[Discussion] ZK compliance layer for EU users — alternative to permissioned pools

MiCA is enforced. Aave needs a compliance path for EU users that doesn’t fragment liquidity into separate permissioned pools like Arc did. I’ve built a working ZK compliance attestation protocol (Piyora). Users do KYC once with any provider, then generate a zero-knowledge proof in-browser (3-5s) that says “I’m compliant” — valid KYC, allowed jurisdiction, not sanctioned, not expired — without revealing identity. Verified on-chain, 25K gas per tx on L2. What this means practically for Aave: No separate pool needed. Compliance check sits as a modifier on EU-facing functions in the main pool. No KYC data custody. Aave never touches PII. Liability stays with the KYC provider. 25K gas overhead per tx ($0.002 on Base). One-time attestation submission: 280K gas ($0.02). Users re-prove every 7-30 days (checks latest sanctions list automatically). The circuit is built in Noir (~30K constraints, UltraPlonk, no trusted setup). Solidity verifier auto-generated. I have a working prototype — contracts tested (13 passing), proof generates and verifies locally. I’m not proposing a governance vote here — just checking: Is EU compliance being actively discussed? I see nothing in recent proposals. Would a ZK approach be considered, or is the preference for traditional KYC gating? What specific checks would governance want? (KYC level, jurisdiction whitelist, sanctions, accredited investor status?) Happy to share a demo or technical details if there’s interest. piyora.org Piyora — ZK Compliance for DeFi 3 posts - 2 participants Read full topic