eerc-introduction
Use when the agent needs to understand what eERC (Encrypted ERC) is, its key features, and high-level architecture before building a confidential token on Avalanche. The entry point for all eERC work.
SKILL.mdskills/eerc-introduction/SKILL.md
GitHubeERC (Encrypted ERC) — Introduction
Overview
The Encrypted ERC-20 (eERC) standard, developed by AvaCloud, enables confidential token transfers on Avalanche (and any EVM chain). Balances and transfer amounts are encrypted on-chain, while validity is proven with zk-SNARKs. No protocol changes, relayers, or off-chain actors are required — it is fully on-chain.
Key Features
- Confidential transactions — balances and amounts are hidden on-chain.
- Client-side operations — encryption, decryption, and proof generation run on the user's device. The contract only verifies proofs; it never sees plaintext.
- Fully on-chain — no relayers or trusted off-chain intermediaries.
- Built-in, rotatable auditors — selective decryption for compliance, without redeploying.
- Dual-mode — create a brand-new private token (Standalone) or wrap an existing ERC-20 (Converter). See [[eerc-deployment-modes]].
- Large integers — supports amounts up to 2^251.
- Chain-agnostic — deployable on any EVM chain (C-Chain mainnet, Fuji, custom L1s).
- (New) Encrypted metadata — attach arbitrary encrypted metadata to transactions.
Architecture (high level)
flowchart LR
User["User (browser)"] -->|encrypt + prove| SDK["eERC SDK (@avalabs/ac-eerc-sdk)"]
SDK -->|tx + zk proof| EERC["EncryptedERC contract"]
EERC --> Reg["Registrar (public keys)"]
EERC --> Bal["EncryptedUserBalances"]
EERC --> Aud["AuditorManager"]
EERC --> Ver["ZK Verifiers (Groth16)"]
All sensitive math happens client-side in the SDK; the chain stores ciphertext and verifies proofs. Details: [[eerc-architecture-contracts]], [[eerc-cryptography]].
The eERC lifecycle
register → generateDecryptionKey → (privateMint / deposit) → privateTransfer → (privateBurn / withdraw). Compliance via the auditor key ([[eerc-auditor-compliance]]).
Common Pitfalls
- Skipping registration. Every user must
register()and have a decryption key before any operation — see [[eerc-sdk-registration]]. - Confusing eERC with general FHE. eERC uses zk-SNARKs + partially homomorphic ElGamal for token amounts specifically, not arbitrary encrypted computation.
AI Agent Prompt
"Act as an eERC specialist. Explain how eERC keeps balances and amounts confidential on a public Avalanche chain while remaining EVM-compatible and compliance-ready, then outline the build steps."
References
See references/README.md (EncryptedERC repo README + academy "What is eERC").