heavenkey (heavenkey)

Heavenkey is a trustless digital inheritance protocol built on Ethereum. This 5-minute video shows the full flow end-to-end: inactivity detection, encrypted heirs, commit–reveal succession, and an ethical fallback if no heir claims. The goal is to prevent on-chain assets from remaining locked forever, without custodians and without leaking private data. Built with Ethereum, Chainlink, XMTP, MetaMask.

• 0 replies
• 0 recasts
• 1 reaction

Heavenkey has officially applied to the Ethereum Security QF Round on Giveth. We’re building non-custodial security infrastructure for digital asset continuity on Ethereum: privacy-preserving heirs, sequential claim flows, and ethical fallback to reduce permanent asset loss. Official Giveth project page: https://giveth.io/project/heavenkey-digital-will-automation-ethical-fallback #Ethereum #EthereumSecurity #Giveth #PublicGoods #WalletSafety #Heavenkey

• 0 replies
• 0 recasts
• 1 reaction

Heavenkey – encrypted heirs for digital inheritance on Ethereum 🔐 Heirs are never exposed on-chain. – Client-side encryption (AES-GCM) – Encrypted blobs on IPFS – On-chain commitment only – At succession, only the active heir receives the decryption key; all others stay encrypted until (and unless) their turn arrives. Digital inheritance needs privacy by design. GitHub (protocol + docs): https://github.com/heavenkey-protocol/heavenkey-sepolia-deployment/blob/main/docs/Heavenkey_Evolution_Roadmap.md #Heavenkey #Ethereum #PrivacyByDesign #Web3Security @ipfs @gitcoin

• 0 replies
• 0 recasts
• 1 reaction

@ethereum Looking for feedback from devs who’ve built complex Ethereum systems. We’re using a Diamond architecture (EIP-2535) for an automated digital-inheritance protocol with inactivity proofs, encrypted heirs (AES-GCM on IPFS), and a fallback to public goods. What’s the most critical security consideration you’d expect in such a design?

• 0 replies
• 0 recasts
• 0 reactions