A continuation of a series of ongoing threads on detail and well explained technical approach into token confidentiality and it's various usage.
On thread 3, we talked about or further broke down PlatON thread on Compliance × Privacy Tension Map and how it affects token confidentiality. Thread 4 is a continuation of these series and today's writeup is on Account-based Confidential Balances.
Token confidentiality as we have mentioned on several post, it's not simply hiding or masking certain transactions but rather a means for institutions to come in while ensuring there is a degree for privacy and also accountability when the need arise. Thread 4 talks about address been visible to the public while amounts and balances are encrypted or represented as commitments.
How is this carried out?
From the onset we talk about the interface, simply put a means were contracts are enabled to invoke confidential balances and transfers in a manner similar to Erc20, then product shape and engineering boundary.
The end goal is to ensure address stays visible to any and everyone who cares to look, but transfers and transactions stay masked or hidden represented as commitment.
ERC-20 transfers on public chains disclose amounts and balances by default. That creates clear problems for institutional and commercial scenarios.
Account-based model:
Addresses are visible.
Amounts and balances are encrypted or represented as commitments.
Main track for Phase 1 — suitable for everyday payments and institutional settlement.
To read the entirity of Deep read 04, then check out PlatON official X page here Tweet.