The Evolution of Data Control in Decentralized Networks
summary
Frequency implements a private social-graph protocol that already stores almost a million private graphs, uses 64-bit identifiers and Merkle child trees to compress state, and enforces tombstoning for deletes. Access uses wallet-held keys with an extended login based on EIP-4361 and Cappy 122 and supports lazy key rotation. Future fixes include threshold cryptography for permissioned reads; homomorphic encryption works but is slow and leaks metadata; quantum-safe signatures balloon key sizes (roughly 65× larger), a practical storage cost.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:41What is Data Control
- 3:15History of Data Control
- 6:28Blockchain
- 7:21Today
- 14:38Data Management
- 16:45Tangent Alert
- 18:45Threshold Cryptography
- 20:53Homorphic Encryption
- 22:38PassKey Encryption
- 28:16Outro
related talks
16mThe Future of Democracy Hinges on Privacy Rights
31mBuilding a Web3 Where Platform Controls our Data
42mYour Data is Showing
10mHow Merkle Trees Enable the Decentralized Web!
01h 15mKeynote: Feeling the Local-First Elephant: A Roadmap, Hidden Gems, and New Puzzles...
51mSign in With Ethereum: the Most Powerful Protocol in #Web3?
24mDecentralise to Protect: Start your shift away from centralised storage today
07mZone of Privacy