diff --git a/PRD-IPTF-PUBLIC-Q1-2026.md b/PRD-IPTF-PUBLIC-Q1-2026.md index d34620a..b47f6c5 100644 --- a/PRD-IPTF-PUBLIC-Q1-2026.md +++ b/PRD-IPTF-PUBLIC-Q1-2026.md @@ -108,21 +108,21 @@ Each deliverable scored on: ### Sprint 0: Infrastructure [Week 1, Days 1-2] -**PR-001: CI Quality Gates** +**PR-001: CI Quality Gates** ✅ DONE ([PR #40](https://github.com/ethereum/iptf-map/pull/40)) ``` Files: .github/workflows/ci.yml, scripts/validate-patterns.js DoD: Runs on every PR, blocks merge if checks fail Size: ~200 lines ``` -**PR-002: Pattern Validation Script** +**PR-002: Pattern Validation Script** ✅ DONE ([PR #40](https://github.com/ethereum/iptf-map/pull/40)) ``` Files: scripts/check-frontmatter.py, scripts/check-sections.py DoD: Validates all required fields and sections Size: ~150 lines ``` -**PR-002b: Remediate Existing Pattern Warnings** +**PR-002b: Remediate Existing Pattern Warnings** ✅ DONE ([PR #42](https://github.com/ethereum/iptf-map/pull/42)) ``` Files: 34 pattern files with CI warnings (see GitHub Issue #41) DoD: All patterns have required frontmatter fields, missing sections added, maturity values standardized diff --git a/patterns/pattern-co-snark.md b/patterns/pattern-co-snark.md index 120a5ad..b7adbd9 100644 --- a/patterns/pattern-co-snark.md +++ b/patterns/pattern-co-snark.md @@ -2,6 +2,10 @@ title: "Pattern: co-SNARKs (Collaborative Proving)" status: draft maturity: PoC +layer: hybrid +privacy_goal: Enable multi-party ZK proving over distributed private inputs without disclosure +assumptions: co-SNARK protocol infrastructure, MPC network coordination, honest majority among proving parties +last_reviewed: 2026-01-14 works-best-when: - Multiple parties each hold sensitive data or models, and need to jointly prove compliance, settlement, or state updates without revealing inputs. avoid-when: diff --git a/patterns/pattern-commit-and-prove.md b/patterns/pattern-commit-and-prove.md index e95ec78..8e2bbc1 100644 --- a/patterns/pattern-commit-and-prove.md +++ b/patterns/pattern-commit-and-prove.md @@ -2,6 +2,10 @@ title: "Pattern: Commit-and-Prove Fallback" status: draft maturity: pilot +layer: hybrid +privacy_goal: Achieve conditional atomicity via shared commitments across chains +assumptions: On-chain commitment contracts, coordination runbook, both parties accept coordination overhead +last_reviewed: 2026-01-14 works-best-when: - Both parties accept extra coordination overhead. - Circuit complexity or infra constraints block other patterns. diff --git a/patterns/pattern-crypto-registry-bridge-ewpg-eas.md b/patterns/pattern-crypto-registry-bridge-ewpg-eas.md index 2186a14..b45116e 100644 --- a/patterns/pattern-crypto-registry-bridge-ewpg-eas.md +++ b/patterns/pattern-crypto-registry-bridge-ewpg-eas.md @@ -2,6 +2,10 @@ title: "Pattern: Crypto-register bridge (eWpG) with EAS mirroring" status: ready maturity: pilot +layer: hybrid +privacy_goal: Mirror licensed crypto-register facts on-chain as attestations without exposing PII +assumptions: Licensed crypto-register (eWpG), EAS infrastructure, registrar API access +last_reviewed: 2026-01-14 works-best-when: - Germany/eWpG applies and a licensed crypto-register is required. avoid-when: diff --git a/patterns/pattern-dvp-erc7573.md b/patterns/pattern-dvp-erc7573.md index 5f67fa5..92d71cf 100644 --- a/patterns/pattern-dvp-erc7573.md +++ b/patterns/pattern-dvp-erc7573.md @@ -2,6 +2,10 @@ title: "Pattern: Atomic DvP via ERC-7573 (cross-network)" status: ready maturity: pilot +layer: hybrid +privacy_goal: Enable atomic cross-network DvP with optional privacy extensions +assumptions: ERC-7573 contracts on both networks, stateless decryption oracle, trade negotiation system +last_reviewed: 2026-01-14 works-best-when: - Asset and cash legs live on different networks (L1/L2). avoid-when: diff --git a/patterns/pattern-eil.md b/patterns/pattern-eil.md index e415312..f95861c 100644 --- a/patterns/pattern-eil.md +++ b/patterns/pattern-eil.md @@ -1,7 +1,11 @@ --- title: "Pattern: EIL (Ethereum Interoperability Layer)" status: draft -maturity: ready +maturity: pilot +layer: hybrid +privacy_goal: No privacy improvements; provides censorship-resistant cross-L2 execution +assumptions: ERC-4337 accounts, XLP infrastructure with L1 staking, L1 canonical bridge for disputes +last_reviewed: 2026-01-14 rollout-plan: ready to be integrated in wallets works-best-when: - User needs to execute calls on multiple L2s with one signature diff --git a/patterns/pattern-erc3643-rwa.md b/patterns/pattern-erc3643-rwa.md index 1f7b3a8..7221f3c 100644 --- a/patterns/pattern-erc3643-rwa.md +++ b/patterns/pattern-erc3643-rwa.md @@ -1,7 +1,11 @@ --- title: "Pattern: ERC-3643 Tokenized RWAs" status: ready -maturity: prod +maturity: production +layer: L1 +privacy_goal: Enforce compliant token transfers with identity verification at contract level +assumptions: ONCHAINID infrastructure, trusted claim issuers, ERC-734/735 key management +last_reviewed: 2026-01-14 works-best-when: - Regulatory compliance is mandatory - Need permissioned transfers with identity verification diff --git a/patterns/pattern-focil-eip7805.md b/patterns/pattern-focil-eip7805.md index 6a643d6..883c99d 100644 --- a/patterns/pattern-focil-eip7805.md +++ b/patterns/pattern-focil-eip7805.md @@ -1,7 +1,11 @@ --- title: "Pattern: FOCIL - Fork-Choice Enforced Inclusion Lists" status: draft -maturity: not yet recommended +maturity: experimental +layer: L1 +privacy_goal: No privacy; provides censorship resistance via forced transaction inclusion +assumptions: EIP-7805 adoption, 1-of-16 honest IL committee member, consensus layer changes +last_reviewed: 2026-01-14 rollout-plan: glamsterdam or later forks works-best-when: - Censorship resistance is critical @@ -16,6 +20,12 @@ dependencies: [EIP-7805] FOCIL (Fork-Choice Enforced Inclusion Lists) is an EIP that enables a committee of 16 validators to force-include transactions in blocks, preventing censorship by sophisticated block builders. FOCIL itself does not provide privacy, transactions remain fully visible in the public mempool and on-chain. It only guarantees that transactions cannot be censored once submitted to the mempool. +## Ingredients + +- **Standards**: EIP-7805 (FOCIL specification) +- **Infra**: Ethereum consensus layer with fork-choice enforcement, P2P gossip network for IL propagation +- **Off-chain**: IL committee selection mechanism, equivocation detection + ## Protocol (concise) 1. Committee Selection (Slot N), a committee of 16 validators is selected for slot N to build ILs for slot N+1 diff --git a/patterns/pattern-icma-bdt-data-model.md b/patterns/pattern-icma-bdt-data-model.md index 55fee58..54cac28 100644 --- a/patterns/pattern-icma-bdt-data-model.md +++ b/patterns/pattern-icma-bdt-data-model.md @@ -1,7 +1,11 @@ --- title: "Pattern: ICMA Bond Data Taxonomy (canonical terms/events)" status: ready -maturity: prod +maturity: production +layer: offchain +privacy_goal: Standardize bond data for clean attestations without exposing raw data +assumptions: ICMA BDT schema adoption, schema validator tooling, registrar integration +last_reviewed: 2026-01-14 works-best-when: - You want machine-readable bond terms/events across tools. avoid-when: diff --git a/patterns/pattern-l1-zk-commitment-pool.md b/patterns/pattern-l1-zk-commitment-pool.md index 3e8552b..2c89639 100644 --- a/patterns/pattern-l1-zk-commitment-pool.md +++ b/patterns/pattern-l1-zk-commitment-pool.md @@ -2,6 +2,10 @@ title: "Pattern: L1 ZK commitment pool (low volume)" status: ready maturity: pilot +layer: L1 +privacy_goal: Hide amounts and positions on L1 via shielded pool with commitments and nullifiers +assumptions: ZK proof system, prover infrastructure, ERC-3643/ERC-7573 integration +last_reviewed: 2026-01-14 works-best-when: - Low trade frequency; L2 not available or desirable. avoid-when: diff --git a/patterns/pattern-l2-encrypted-offchain-audit.md b/patterns/pattern-l2-encrypted-offchain-audit.md index 1876a9c..327dc59 100644 --- a/patterns/pattern-l2-encrypted-offchain-audit.md +++ b/patterns/pattern-l2-encrypted-offchain-audit.md @@ -2,6 +2,10 @@ title: "Pattern: Low-cost L2 + Off-chain Encrypted Audit Log" status: ready maturity: pilot +layer: hybrid +privacy_goal: Hide amounts and positions with only commitments on-chain; encrypted audit log off-chain +assumptions: L2 infrastructure, threshold KMS for scoped keys, EAS for access logging +last_reviewed: 2026-01-14 works-best-when: - Need hidden amounts/positions with minimal on-chain footprint. - Prefer cheap daily settlement over full on-chain private compute. diff --git a/patterns/pattern-lean-ethereum.md b/patterns/pattern-lean-ethereum.md index 9f857c3..ae2fd04 100644 --- a/patterns/pattern-lean-ethereum.md +++ b/patterns/pattern-lean-ethereum.md @@ -1,7 +1,11 @@ --- title: Lean Ethereum status: draft -maturity: research +maturity: experimental +layer: L1 +privacy_goal: No direct privacy; consensus redesign enabling light client verification +assumptions: Post-quantum signatures, minimal zkVMs, 4-5 year research timeline, ~15 client teams +last_reviewed: 2026-01-14 works-best-when: - Long-term Ethereum consensus redesign needed - Solo validation accessibility matters diff --git a/patterns/pattern-mpc-custody.md b/patterns/pattern-mpc-custody.md index d713381..bb25db5 100644 --- a/patterns/pattern-mpc-custody.md +++ b/patterns/pattern-mpc-custody.md @@ -1,7 +1,11 @@ --- title: "Pattern: MPC Custody and Transaction Control" status: draft -maturity: prod +maturity: production +layer: offchain +privacy_goal: Protect private keys via threshold distribution; no on-chain privacy of transactions +assumptions: Threshold ECDSA/EdDSA infrastructure, MPC nodes in TEE/HSM, policy engine +last_reviewed: 2026-01-14 works-best-when: - Institutions require regulated-grade custody for digital assets - Key material must never exist in one place, but transactions must be orchestrated quickly diff --git a/patterns/pattern-noir-private-contracts.md b/patterns/pattern-noir-private-contracts.md index c025033..b003e40 100644 --- a/patterns/pattern-noir-private-contracts.md +++ b/patterns/pattern-noir-private-contracts.md @@ -2,6 +2,10 @@ title: "Pattern: Aztec Noir Private Contracts" status: ready maturity: pilot +layer: L2 +privacy_goal: Enable composable private and public state in single contracts via ZK proofs +assumptions: Aztec rollup infrastructure, client-side proving capability (8GB RAM), Barretenberg prover +last_reviewed: 2026-01-14 works-best-when: - Applications need composable private and public state in a single contract - Developers want privacy without abandoning familiar programming paradigms diff --git a/patterns/pattern-oif.md b/patterns/pattern-oif.md index aea4197..b000e38 100644 --- a/patterns/pattern-oif.md +++ b/patterns/pattern-oif.md @@ -1,7 +1,11 @@ --- title: "Pattern: Open Intent Framework (OIF)" status: draft -maturity: ready +maturity: pilot +layer: hybrid +privacy_goal: No transaction privacy; intents visible to solvers during discovery +assumptions: Active solver network, cross-chain messaging layer, price oracles +last_reviewed: 2026-01-14 rollout-plan: ready to build solvers works-best-when: - Cross-chain settlement needed diff --git a/patterns/pattern-permissioned-ledger-interoperability.md b/patterns/pattern-permissioned-ledger-interoperability.md index 02b21aa..b48ca07 100644 --- a/patterns/pattern-permissioned-ledger-interoperability.md +++ b/patterns/pattern-permissioned-ledger-interoperability.md @@ -2,6 +2,10 @@ title: "Pattern: Permissioned Ledger Interoperability" status: draft maturity: pilot +layer: offchain +privacy_goal: Cross-ledger atomicity with counterparty-only visibility of transaction state +assumptions: Canton/DAML or similar sync protocol, harmonized governance, selective disclosure for regulators +last_reviewed: 2026-01-14 works-best-when: - Multiple financial institutions each operate their own permissioned ledger but require atomic cross-ledger settlement - Regulatory constraints prevent moving all participants onto a single shared chain diff --git a/patterns/pattern-pretrade-privacy-encryption.md b/patterns/pattern-pretrade-privacy-encryption.md index 1e3cd80..bafa50d 100644 --- a/patterns/pattern-pretrade-privacy-encryption.md +++ b/patterns/pattern-pretrade-privacy-encryption.md @@ -2,6 +2,10 @@ title: "Pattern: Pre-trade privacy (Shutter/SUAVE/private RFQ)" status: ready maturity: pilot +layer: hybrid +privacy_goal: Prevent front-running and information leakage via encrypted order submission +assumptions: Encrypted mempool (Shutter) or private builders (SUAVE), allow-listed counterparties +last_reviewed: 2026-01-14 works-best-when: - RFQ/secondary trading must not leak intent, size, or price pre-inclusion. avoid-when: diff --git a/patterns/pattern-privacy-l2s.md b/patterns/pattern-privacy-l2s.md index e9b4c85..b04fd9d 100644 --- a/patterns/pattern-privacy-l2s.md +++ b/patterns/pattern-privacy-l2s.md @@ -2,6 +2,10 @@ title: "Pattern: Private L2s" status: draft maturity: PoC +layer: L2 +privacy_goal: Execute financial logic with private state enabling confidential value and unlinkable identity +assumptions: Privacy-native rollup (ZK or FHE), L1 bridge contracts, viewing key infrastructure +last_reviewed: 2026-01-14 works-best-when: - Strong privacy is required beyond value-hiding: identity unlinkability, programmable access. - Institutions want to embed compliance hooks (view keys, audit proofs). @@ -25,6 +29,16 @@ Use a **privacy-native rollup** (ZK or FHE-based) to execute financial logic wit - FHE rollups: Zama/fhEVM, Inco - **Off-chain**: Key management, regulator view proofs +## Protocol (concise) + +1. Bridge assets from L1 to privacy L2 via deposit contract. +2. Assets converted to private notes/commitments on the L2. +3. Execute transactions privately within L2 (amounts, senders, receivers shielded). +4. Generate ZK proofs (or FHE computations) for state transitions. +5. Optionally couple with ERC-7573 for atomic DvP/PvP settlement. +6. Provide viewing keys or disclosure proofs to regulators as needed. +7. Exit to L1 via withdrawal with proof of valid state. + ## Guarantees - **Private transactions**: Transaction details (amounts, senders, receivers) are shielded within the L2. diff --git a/patterns/pattern-private-iso20022.md b/patterns/pattern-private-iso20022.md index 99aaf25..b928ee2 100644 --- a/patterns/pattern-private-iso20022.md +++ b/patterns/pattern-private-iso20022.md @@ -1,7 +1,11 @@ --- title: "Pattern: Private ISO 20022 Messaging & Settlement" status: draft -maturity: research +maturity: experimental +layer: hybrid +privacy_goal: Private ERC-20 settlements linked to ISO 20022 instructions with regulator-only visibility +assumptions: ISO 20022 schema, shielded pool or confidential token infrastructure, threshold KMS +last_reviewed: 2026-01-14 works-best-when: - Institutions already exchange ISO 20022 messages (pacs.008/009/002, camt.\*). - On-chain settlement (ERC-20, tokenized deposits) must link to SWIFT/ISO workflows. diff --git a/patterns/pattern-private-mtp-auth.md b/patterns/pattern-private-mtp-auth.md index c1a1f75..c23a486 100644 --- a/patterns/pattern-private-mtp-auth.md +++ b/patterns/pattern-private-mtp-auth.md @@ -2,6 +2,10 @@ title: "Pattern: Private Client Authentication for Institutional EOAs" status: draft maturity: pilot +layer: hybrid +privacy_goal: Authenticate client EOAs via Merkle proofs without revealing identity or linking addresses +assumptions: ZK circuits for Merkle membership, on-chain Merkle root registry, Semaphore or similar +last_reviewed: 2026-01-14 works-best-when: - Institutions must comply with KYC/AML but want to protect client privacy onchain. - Clients need to prove control of EOAs without revealing identity. diff --git a/patterns/pattern-private-pvp-stablecoins-erc7573.md b/patterns/pattern-private-pvp-stablecoins-erc7573.md index 376a8e7..07cafb5 100644 --- a/patterns/pattern-private-pvp-stablecoins-erc7573.md +++ b/patterns/pattern-private-pvp-stablecoins-erc7573.md @@ -2,6 +2,10 @@ title: "Pattern: Private PvP (cash↔cash) Settlement via ERC‑7573" status: draft maturity: PoC +layer: hybrid +privacy_goal: Atomic PvP between stablecoins with amount privacy and stakeholder-only visibility +assumptions: ERC-7573 escrows, FX/price oracles, shielded transfer infrastructure on both legs +last_reviewed: 2026-01-14 works-best-when: - Two permissioned/regulated stablecoins (same L2 or cross‑L2) must settle **atomically** with **amount privacy**. - FX or cross‑issuer settlement requires on‑chain finality sensing and pricing. diff --git a/patterns/pattern-private-stablecoin-shielded-payments.md b/patterns/pattern-private-stablecoin-shielded-payments.md index 3321993..5b6b9c3 100644 --- a/patterns/pattern-private-stablecoin-shielded-payments.md +++ b/patterns/pattern-private-stablecoin-shielded-payments.md @@ -2,6 +2,10 @@ title: "Pattern: Private Stablecoin Shielded Payments" status: ready maturity: pilot +layer: L2 +privacy_goal: Stakeholder-only stablecoin transfers with view-key/proof-based disclosure for regulators +assumptions: Privacy L2 (Aztec/Zama/Fhenix), wallet/KMS integration, optional L1 anchoring +last_reviewed: 2026-01-14 works-best-when: - Cash leg must be private (amounts + counterparties) with selective disclosure. - You need Ethereum‑native tooling (L2/app‑chain) and interop with PvP or DvP. diff --git a/patterns/pattern-private-vaults.md b/patterns/pattern-private-vaults.md index 07595c4..2bbfa11 100644 --- a/patterns/pattern-private-vaults.md +++ b/patterns/pattern-private-vaults.md @@ -2,6 +2,10 @@ title: "Pattern: Private Intent-Based Vaults" status: draft maturity: PoC +layer: hybrid +privacy_goal: Hide strategy parameters and order flow while keeping deposited assets auditable +assumptions: FHE-enabled chain or privacy L2, intent relayers/solvers, compliance oracles +last_reviewed: 2026-01-14 works-best-when: - Institutions or funds need private strategy execution while assets remain transparently custodied. - Strategies are automated or intent-driven and should not leak parameters to competitors. diff --git a/patterns/pattern-regulatory-disclosure-keys-proofs.md b/patterns/pattern-regulatory-disclosure-keys-proofs.md index 88e693c..feef20e 100644 --- a/patterns/pattern-regulatory-disclosure-keys-proofs.md +++ b/patterns/pattern-regulatory-disclosure-keys-proofs.md @@ -2,6 +2,10 @@ title: "Pattern: Selective disclosure (viewing keys + ZK proofs)" status: ready maturity: pilot +layer: hybrid +privacy_goal: Provide on-demand scoped visibility into confidential trades via threshold keys or ZK proofs +assumptions: Threshold KMS, EAS for access logging, ZK predicate circuits +last_reviewed: 2026-01-14 works-best-when: - Regulator needs targeted visibility without blanket transparency. avoid-when: diff --git a/patterns/pattern-shielding.md b/patterns/pattern-shielding.md index a7bc7e4..9497225 100644 --- a/patterns/pattern-shielding.md +++ b/patterns/pattern-shielding.md @@ -2,6 +2,10 @@ title: "Pattern: Shielded ERC-20 Transfers" status: draft maturity: PoC +layer: hybrid +privacy_goal: Confidential ERC-20 transfers hiding balances and metadata with selective disclosure +assumptions: Shielded pool contracts or privacy L2, wallet support for shielded keys +last_reviewed: 2026-01-14 works-best-when: - You need confidential transfer amounts/counterparties. - Selective disclosure/auditing is required. @@ -24,6 +28,16 @@ Enable **confidential ERC-20 transfers** by shielding balances and transfer meta - **Privacy L2/app-chains** (e.g., Aztec, Zama fhEVM, Fhenix) with native shielding. - **Wallet/KMS**: Management of shielded keys and optional viewing keys. +## Protocol (concise) + +1. Deposit ERC-20 tokens into shielded pool contract. +2. Receive private notes/commitments representing the deposit. +3. Execute shielded transfers by spending notes and creating new ones. +4. Generate ZK proof for each transfer (balance validity, no double-spend). +5. Optionally use stealth addresses (ERC-5564) for recipient unlinkability. +6. Provide viewing keys to auditors for selective disclosure. +7. Withdraw by proving ownership of notes and burning them. + ## Guarantees - Hides amounts + counterparties from non-participants. diff --git a/patterns/pattern-stealth-addresses.md b/patterns/pattern-stealth-addresses.md index 536dd0a..cb162bb 100644 --- a/patterns/pattern-stealth-addresses.md +++ b/patterns/pattern-stealth-addresses.md @@ -2,6 +2,10 @@ title: "Pattern: Stealth Addresses" status: draft maturity: PoC +layer: L1 +privacy_goal: Hide address linkages via one-time destination addresses; amounts remain visible +assumptions: EIP-5564 support, wallet view/spend key management, optional registry for public view keys +last_reviewed: 2026-01-14 works-best-when: - Sender and receiver want to hide address linkages on a public chain. - Amount privacy is less critical than unlinkability of counterparties. diff --git a/patterns/pattern-tee-key-manager.md b/patterns/pattern-tee-key-manager.md index 67ae399..b3ea5c2 100644 --- a/patterns/pattern-tee-key-manager.md +++ b/patterns/pattern-tee-key-manager.md @@ -2,6 +2,10 @@ title: "Pattern: TEE key manager" status: draft maturity: pilot +layer: offchain +privacy_goal: Isolate private keys in TEE with policy-bound signing; no on-chain transaction privacy +assumptions: Attested TEE hardware (SGX/SEV), attestation verification service, KMS for bootstrapping +last_reviewed: 2026-01-14 works-best-when: - Institutions need hot or warm keys with stronger isolation than software-only wallets. - TEE operator and hardware vendor are known and contractually bound. diff --git a/patterns/pattern-tee-zk-settlement.md b/patterns/pattern-tee-zk-settlement.md index f61577e..d667261 100644 --- a/patterns/pattern-tee-zk-settlement.md +++ b/patterns/pattern-tee-zk-settlement.md @@ -2,6 +2,10 @@ title: "Pattern: Hybrid TEE + ZK Settlement" status: draft maturity: pilot +layer: hybrid +privacy_goal: Private cross-chain settlement in TEEs with ZK proofs attesting correct execution +assumptions: Attested TEE infrastructure, ZK prover backend, attestation registry +last_reviewed: 2026-01-14 works-best-when: - Participants accept some trust in TEEs but want zk-based attestations for audit. - Privacy requirements exceed what public smart contracts can do alone. diff --git a/patterns/pattern-verifiable-attestation.md b/patterns/pattern-verifiable-attestation.md index d01f279..f4e0e34 100644 --- a/patterns/pattern-verifiable-attestation.md +++ b/patterns/pattern-verifiable-attestation.md @@ -1,7 +1,11 @@ --- title: "Pattern: Attestation verifiable on-chain" status: ready -maturity: prod +maturity: production +layer: hybrid +privacy_goal: Verify claims about identities/credentials on-chain with minimal data disclosure +assumptions: Trusted issuers (banks, KYC providers), EAS/ONCHAINID infrastructure, wallet support +last_reviewed: 2026-01-14 works-best-when: - Some logic has to be embedded onchain and relies on off-chain attested data - A user wants to prove a statement about his identity (membership, KYC,...) diff --git a/patterns/pattern-zk-derivative-delta.md b/patterns/pattern-zk-derivative-delta.md index 9972b33..7d68b42 100644 --- a/patterns/pattern-zk-derivative-delta.md +++ b/patterns/pattern-zk-derivative-delta.md @@ -2,6 +2,10 @@ title: "Pattern: ZK Proof of Private State Transition" status: draft maturity: PoC +layer: hybrid +privacy_goal: Apply daily margin updates without revealing delta or balances on-chain +assumptions: ERC-6123 SDC, zkSNARK prover/verifier, public oracle with signed price data +last_reviewed: 2026-01-14 works-best-when: - Oracle price or price change is public and signed. - Counterparties share the same private state (notional, direction, balances). @@ -14,6 +18,12 @@ dependencies: - (optional) CoSnark prover/verifier --- +## Ingredients + +- **Standards**: ERC-6123 (SDC framework) +- **Infra**: zkSNARK prover/verifier, SDC contract on L1/L2 +- **Off-chain**: Oracle providing signed price data, optional shielded-pool ledger, CoSnark infrastructure for MPC variants + ## Intent Apply **daily margin updates (delta)** for a plain swap **without revealing delta or balances on-chain**. @@ -56,5 +66,11 @@ If the payoff uses **additional private inputs that the other party must not lea - 1y IRS, public rate fixings. - Parties share notional & direction; oracle signs daily rate. -- Prover submits ZK proof “delta computed correctly; C_prev → C_next valid.” +- Prover submits ZK proof "delta computed correctly; C_prev → C_next valid." - Chain updates state; no amounts leak. + +## See also + +- [pattern-zk-shielded-balances.md](pattern-zk-shielded-balances.md) +- [pattern-regulatory-disclosure-keys-proofs.md](pattern-regulatory-disclosure-keys-proofs.md) +- [pattern-co-snark.md](pattern-co-snark.md) diff --git a/patterns/pattern-zk-htlc.md b/patterns/pattern-zk-htlc.md index e89566c..2efc2cb 100644 --- a/patterns/pattern-zk-htlc.md +++ b/patterns/pattern-zk-htlc.md @@ -2,6 +2,10 @@ title: "Pattern: Shielded-Pool Atomic Swap (ZK-HTLC)" status: draft maturity: PoC +layer: hybrid +privacy_goal: Cross-chain DvP with both legs in shielded pools; atomicity via ZK proofs +assumptions: Shielded pool infrastructure on both chains, relayer/bridge, proof bundling service +last_reviewed: 2026-01-14 works-best-when: - Both assets already live in shielded pools (zk-rollups, privacy L2s). - Cross-chain atomicity is required without revealing linkages. diff --git a/patterns/pattern-zk-kyc-ml-id-erc734-735.md b/patterns/pattern-zk-kyc-ml-id-erc734-735.md index 34e7927..8858a15 100644 --- a/patterns/pattern-zk-kyc-ml-id-erc734-735.md +++ b/patterns/pattern-zk-kyc-ml-id-erc734-735.md @@ -2,6 +2,10 @@ title: "Pattern: zk-KYC/ML + ONCHAINID (ERC-734-735)" status: draft maturity: PoC +layer: hybrid +privacy_goal: Public verifiable identity onboarding via ZK proofs of KYC/AML compliance +assumptions: ERC-734/735 identity framework, zk-KYC/ML prover (EZKL), zk-TLS or compliant EOA proofs +last_reviewed: 2026-01-14 works-best-when: - need public verifiability of identities onboarding (perhaps for instant settlement) avoid-when: diff --git a/patterns/pattern-zk-shielded-balances.md b/patterns/pattern-zk-shielded-balances.md index 756154f..c68914e 100644 --- a/patterns/pattern-zk-shielded-balances.md +++ b/patterns/pattern-zk-shielded-balances.md @@ -2,6 +2,10 @@ title: "Pattern: ZK Shielded Balances for Derivatives" status: draft maturity: PoC +layer: L2 +privacy_goal: Confidential balances and daily deltas in shielded pool with regulator view keys +assumptions: ERC-6123 SDC, shielded-pool L2, ZK prover infrastructure, key governance for regulators +last_reviewed: 2026-01-14 works-best-when: - Daily settlements (margin calls, deltas) must be hidden. - Regulators require replayable audits via view keys. diff --git a/patterns/pattern-zk-spv.md b/patterns/pattern-zk-spv.md index 7ecc5a2..44c1fa1 100644 --- a/patterns/pattern-zk-spv.md +++ b/patterns/pattern-zk-spv.md @@ -1,7 +1,11 @@ --- title: "Pattern: zk-SPV (Succinct Cross-Chain Verification)" status: draft -maturity: research +maturity: experimental +layer: hybrid +privacy_goal: Trustless cross-chain verification via ZK proofs of transaction finality +assumptions: zkSNARK/zkSTARK prover, target chain consensus in-circuit, verifier contract on verifying chain +last_reviewed: 2026-01-14 works-best-when: - Assets/contracts must verify events on another EVM chain. - Institutions require strong DvP atomicity across ledgers. diff --git a/patterns/pattern-zk-tls.md b/patterns/pattern-zk-tls.md index 89212cb..34964ce 100644 --- a/patterns/pattern-zk-tls.md +++ b/patterns/pattern-zk-tls.md @@ -2,6 +2,10 @@ title: "Pattern: zk-TLS" status: draft maturity: PoC +layer: offchain +privacy_goal: Export verifiable identity/data from web2 systems via ZK proofs on TLS transcripts +assumptions: TLSNotary or similar, trusted Notary for TLS session, ZK prover for transcript +last_reviewed: 2026-01-14 works-best-when: - data needs to be captured using a website avoid-when: