web3wagmi
← All standards

EIP-8182 Private ETH and ERC-20 Transfers

ReviewCorecreated 2026-03-03requires ERC-20

A canonical validity layer for private ETH and compatible ERC-20 transfers via a system contract and a split-proof architecture.

Author: Tom Lehman (@RogerPodacter)

ERC-165 interface ids

Computed here as the XOR of the selectors each interface defines.

IAuthVerifier0x88a8315c

Functions this standard introduces (1)

0x88a8315cverifyAuth(bytes,bytes)

Events (3)

Topic0 is the keccak256 hash of the signature, which is what a log filter matches on.

0xf0b44aeb00769322d0d1c556d150bdfcb0b8c0854dda5f7643e50d9a87f4cf93ShieldedPoolTransact(uint256,uint256,uint256,address,uint256,uint256,uint256,uint256,uint256,bytes,bytes,bytes)
0x95278718c224a240fc6219a205839fc52938b9ac4e085ed6d42028a0e856cb5bShieldedPoolDeposit(address,uint256,uint256,uint256,uint256,uint256,bytes)
0x613bfa51a8f21976490ff0942b6e06e776ddc510271cdbafc7577d4161d76860AuthPolicySet(address,uint256,uint256,uint256,uint256,uint256,uint256)

Depends on (1)

Proposals this one names in its requires field.

ERC-20Token Standard

What the specification covers

AbstractMotivationScopeSpecification1. Overview2. Terminology3. Parameters and Constants3.1 Domain Separators3.2 Fixed Constants3.3 Poseidon Hash Construction3.4 Merkle Tree Constructions3.5 Public-Input Field-Element Encoding4. Architecture5. System Contract5.1 Deployment and Upgrade Model5.2 State5.2.1 Auth-Policy Root History5.3 Contract Interface5.4 Execution5.4.1 transact5.4.2 deposit5.5 Pool Proof Verification6. Auth Policy Registry6.1 Structure and Lifecycle7. Note Commitment and Nullifiers7.1 Address and Amount Constraints7.2 ownerNullifierKeyHash7.3 ownerCommitment7.4 Note Body Commitment7.5 Final Note Commitment7.6 Nullifier7.7 Phantom Nullifier7.8 Note Secret Seed7.9 Note Secret8. Pool Circuit Requirements8.1 Pool Circuit Interface and Auth Proof Coupling8.2 Input Ownership and Membership8.3 Sender ownerNullifierKeyHash and Note-Secret-Seed Binding8.4 Value Conservation8.5 Output Well-Formedness and Determinism8.6 Output Note Data and Output Binding8.7 Intent Replay ID8.8 Token Consistency8.9 Transaction Intent Digest8.10 Execution Constraints9. Public Inputs9.1 Public Input Range Validation10. Poseidon Hash Contexts11. Auth Verifier Contract11.1 Interface11.2 Verification Semantics12. Output Note DataRationaleSystem Contract, Fork-Managed Pool Circuit, and No Admin PauseSplit Proof Architecture and Private Auth-Policy RegistrationCredential-Proof SeparationGroth16 BN254 Pool Proof SystemFuture PQ MigrationHidden Owner IDs and Address ScopeProof-Free DepositsConstrained vs Wallet-Chosen Note SecretsTwo-Layer Note CommitmentLeaf-Index UniquenessOut-of-Protocol ComplianceFinalized Output BindingPrivate Fee CompensationUTXO-Based Notes over Account-Based Encrypted BalancesBackwards CompatibilityTest CasesSecurity ConsiderationsMulti-Auth Security BoundaryAuth Verifier TrustDoS via Root HistoryMetadata LeakageChain-Level Linkability of Self-Reshield FlowsState GrowthOutput Note Data Leakage and SabotageAuth-Policy Root History and Deactivation DelayRegistration HygienenoteSecret ReuseDeposits Are PermissionlessUnlocked Output SlotsPool Proof System AssumptionsCopyright

Compare with

Parsed from the canonical specification · discussion