Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
CIFER SDK (Cryptographic Infrastructure for Encrypted Records) adds quantum-resistant encryption to blockchain applications using ML-KEM-768, a NIST-standardized post-quantum algorithm. It covers payload encryption, large file encryption via async jobs, secret key management with owner/delegate authorization, and on-chain encrypted data commitments.
Uses ML-KEM-768 instead of classical asymmetric algorithms, so encrypted data stays protected even if quantum computers break RSA or ECC in the future.
When to use it
- Encrypting patient health records before writing them to a blockchain
- Protecting private configuration secrets in a server-side Node.js service
- Encrypting large media files with progress tracking before decentralized storage
- Granting a third-party delegate address read-only decryption access to a secret
- Anchoring encrypted message hashes on-chain for tamper-evident audit trails
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Encrypt a message and store the commitment on-chain
- 1Initialize the SDK with createCiferSdk pointing to the blackbox endpoint
- 2Connect the user's wallet via Eip1193SignerAdapter
- 3Call blackbox.payload.encryptPayload with the target secretId and plaintext to get cifer and encryptedMessage
- 4Build the on-chain store transaction with commitments.buildStoreCommitmentTx using the encrypted output
- 5Send the transaction intent through the connected wallet
Encrypted message and cifer bytes stored on-chain; owner or delegate can later retrieve and decrypt via commitments namespace
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.