Skip to main content

Quantum-Resistant
Encryption

CIFER SDK provides post-quantum cryptographic infrastructure for your applications. Secure your data with ML-KEM-768 key encapsulation and AES-GCM encryption — with Web3 wallets or Web2 email + password.

npm install cifer-sdk

Why CIFER SDK?

🔐

Quantum-Resistant

Built on ML-KEM-768 (NIST post-quantum standard) for encryption that stays secure against future quantum computers.

Learn more →
🌐

Web3 + Web2 Ready

Use blockchain wallets (MetaMask, WalletConnect) or email + password — choose the integration that fits your app.

Learn more →
💼

Wallet Agnostic

Works with any EIP-1193 wallet—MetaMask, WalletConnect, Coinbase, or your own custom signer.

Learn more →
✉️

Web2 Support

Use CIFER with email + password registration—no wallet needed. Session-based auth for server-side and traditional web apps.

Learn more →
📦

Zero Dependencies

No wallet library lock-in. Bring your own wallet stack—ethers, viem, wagmi, or vanilla JS.

Learn more →
📁

File Encryption

Encrypt files of any size with async job processing. Perfect for NFT metadata, documents, and media.

Learn more →
⛓️

On-Chain Commitments

Store encrypted data commitments on-chain with log-based retrieval and integrity verification.

Learn more →

Simple, Powerful API

import { createCiferSdk, Eip1193SignerAdapter, blackbox } from 'cifer-sdk';

// Initialize SDK with automatic chain discovery
const sdk = await createCiferSdk({
  blackboxUrl: 'https://cifer-blackbox.ternoa.dev:3010',
});

// Connect your wallet
const signer = new Eip1193SignerAdapter(window.ethereum);

// Encrypt data with quantum-resistant encryption
const encrypted = await blackbox.payload.encryptPayload({
  chainId: 752025,
  secretId: 123n,
  plaintext: 'My confidential data',
  signer,
  readClient: sdk.readClient,
  blackboxUrl: sdk.blackboxUrl,
});

// Store encrypted.cifer on-chain, encrypted.encryptedMessage off-chain
console.log('Encrypted successfully!');

How It Works

1

Create a Secret

Register a quantum-resistant keypair via on-chain transaction (Web3) or API call (Web2). The private key is secured across the CIFER enclave network.

2

Authenticate

Authorize via wallet signature (Web3) or session token (Web2). Both paths use the same Blackbox encryption pipeline.

3

Encrypt Data

Send plaintext to the Blackbox API. Data is encrypted with your secret's ML-KEM public key. Store the result on-chain, in a database, or anywhere.

4

Decrypt Anytime

Authorized users (owner or delegate) can decrypt by signing a request. The Blackbox verifies authorization and returns plaintext.

Ready to Build?

Start encrypting your data with quantum-resistant security in minutes — with Web3 wallets or Web2 email + password.