The Year Is 2030: What Does On-Chain Privacy and Compliance Look Like?
summary
Panel argues concrete roadmap: encryption layers (Inco) plus on‑chain policy engines (Predicate) combine ZK, MPC, FHE and TE so systems use private compute layer plus pre‑transaction checks; bridges enforce risk checks before tokens enter private chains (example: mandatory flow‑of‑fund analytics on LIO bridges). Commitment vs encryption designs trade off rigid per‑user view keys versus shareable decryption via threshold MPC auditors, and programmable compliance stitches on‑chain ZK attestations to off‑chain KYB data; main barrier is social/legal, not crypto.
AI-written summary · about
chapters (13)
- 0:00Introduction and Setup
- 0:14The Hype and Challenges of Privacy in DeFi
- 1:06Imagining the Future of Crypto Compliance
- 1:39Panelist Introductions
- 1:49Remi on Private Compute Layers
- 2:35Nikila on On-Chain Policy Infrastructure
- 3:33Privacy and Compliance Frameworks
- 6:09Types of Privacy in Blockchain
- 9:13Compliance and System Design
- 12:16Technological Solutions for Privacy and Compliance
- 20:15Legal and Societal Challenges
- 24:58Audience Q&A
- 28:10Conclusion and Final Thoughts
related talks
19mBeyond the Blacklist, The Compliant Way To Do Private Transactions
48mSoK: Programmable Privacy
01h 24mPseudonymity, Automation, and Responsibility on Public, Permissionless Blockchains under the GDPR
35mWhy Privacy Matters
31mPrivacy-preserving smart contracts
30mBringing Privacy to Public Blockchain
37mThe Thing with Privacy is
46mCan we have privacy and compliance at the same time?