ZK-Snarks based Wallet Key Management using smart contracts for seed phrase controller, a zk trusted setup on the client side and certificate transparency logs to keep track of revoked keys (experimental)
This project is an approach to seed phrase and private key less key management, which we call radioactive toxic waste, which should be avoided at all cost being treated by humans.
- ENS -
PublicResolver(exists infdp-contracts) - Wasm secure execution context -
KeychainOpsManager - ZK-snarks trusted setup -
KeySequencer - Ethereum Smart Contracts -
KeyController - Certificate Transparency for blockchain wallets
- Keypair operations are executed with security policies using WasmEdge
- First release will use ENS to connect addresses to keys, the spec will allowed for other chains nameservices.
A smart contract (no need to be one per user) that handles seed phrase identification through ZK-snarks proofs, must be able to:
- Associate a seed phrase to Swarm Bee store FDP encrypted seed phrase
- Keep track of key derivation using fingerprinting
- Be able to recover keys by registered WebAuthentication keys, backup codes or Google Drive exported keystores
Where it will create zk-snarks proofs and then update the smart contract with private keys sequences. Seed phrase is downloaded into client (same as FDP) and key is generated inside WasmEdge
- WebAuthentication (recommended approach)
- Backup codes
- Google Drive
Keys are rotated bty design, so public keys must be registered as revoked in a offchain Certificate Transparency database, but with the additional zk-snarks proof as index to search for seed phrase merkle tree of private keys (HD Wallet keys). These logs must not contain any machine or hardware tags or identifier.
- Luis Sanchez (Bee team)
- Rogelio Morrell (FDP team)
MIT Licensed