Beyond the Blacklist, The Compliant Way To Do Private Transactions
summary
Claims that only 0.01% encrypted of last year’s crypto payments (a $27 trillion market) motivates a new L1, Alo, that combines zero-knowledge proofs with view keys and a programmable policy engine (Predicate-style) to enable threshold-shared disclosure, ZPass identity attestations, and bridge flows guarded by time locks and escrows. Concrete builds include private smart contracts, a bridge for ETH/USDC with analytic windows, ARC 100 compliance proposals, and live examples of private stablecoin payments and private DeFi.
AI-written summary · about
chapters (16)
- 0:00Introduction & The Need for Compliant Privacy
- 1:14Parallels to HTTPS & E-Commerce
- 2:14Two Main Challenges in Encrypted Transactions
- 3:10Overview of Alo as a Private L1
- 4:43The Intersection of Permissionless, Programmable & Private
- 6:05Compliance Primitives: View Keys & Policy Engines
- 7:40Real-World ID: ZPass & Age/Governance Proofs
- 9:08Enabling Timelocks, Escrows & Fraud Detection
- 10:04Policy Makers & Best Practices (ARC 100)
- 11:15Industry Validation & Perspectives
- 12:30Key Use Cases: Private Stablecoin Payments
- 13:26Identity & Credential-Based Transactions
- 14:22Gaming & Information-Asymmetric Gameplay
- 15:30Private DeFi & Dark Pools
- 17:10How to Learn More & Future Outlook
- 18:40Conclusion & Thank You
related talks
28mThe Year Is 2030: What Does On-Chain Privacy and Compliance Look Like?
30mBringing Privacy to Public Blockchain
23mAchieving privacy, compliance, and decentralization
18mThe Privacy Spectrum - From Shadows to Standards
21mPrivacy and Compliance - A pragmatic approach
26mHow zero-knowledge proofs can be used to balance privacy and compliance
46mCan we have privacy and compliance at the same time?
48mSoK: Programmable Privacy