@0xmamareza.eth
GM CT π
Howdy Zama Believers ? π
Back with the part 12 of breaking down
@zama
π¨ Confidential ERC-20 | Same Token Standard, Less Exposure π¨
you mint an erc-20, but balances and transfers stay encrypted by default.
holders see their own amounts; everyone else sees rules + proofs, not your numbers.
how it's working π‘
β’ the contract uses fhEVM encrypted types for balances/allowances.
β’ transfers submit encrypted inputs; coprocessors run the fhe math; the chain verifies outcomes.
β’ lightweight zk checks enforce ranges/format (no negative amounts, no overflow) without revealing values.
β’ programmable privacy decides who can decrypt what: user-only, group-only (e.g., auditor + custodian via threshold keys), or post-event.
compliance knobs when needed π‘
β’ allowlists/sanctions, jurisdiction filters, velocity limits.
β’ selective disclosure: reveal just enough for an audit or dispute, nothing more.
β’ full supply math is public and verifiable, even if balances arenβt.
fees + ops π‘
β’ you pay normal gas + protocol fee (usd-denominated, auto-converted to $ZAMA).
β’ kms nodes hold split keys; coprocessors do the heavy lifting.
Zama is maaaking it !
private by default, auditable when required. same erc-20 interface, better privacy hygiene.
TL;DR:
ship a token that protects users without breaking composability.