Mamareza pfp
Mamareza

@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.
0 reply
0 recast
2 reactions