PlatON lately, Deep read thread 5

in #platon • 23 hours ago

A continuation of a series of ongoing threads on detail and well explained technical approach into token confidentiality and it's various usage.

Deep read 05? ZK + Note — Stronger Privacy Does Not Mean a Better Default Architecture.

Stronger privacy does not mean a better default architecture, what does this mean or why shouldn't it be default?

Over the past couple of weeks to months, we have been explaining and outlining the various needs and importance for privacy and many might have asked, why not make it default for all transactions if it is built to follow compliance and the rest? From the end point, this might look all good and real theoretically but actualization is a different thing.

Privacy on its own comes with various approaches to achieve the desired result, approaches which are a bit complex and also expensive, making this the default setting for all transactions might end up creating more problems than actually solving them. Say a user need to transfer $10 worth of an asset and then opt for a strong privacy approach, they might end up spending far more time to achieve this and also the end user might find it a bit difficult to recieve the disired assets.

PlatON's approach says that privacy shouldn't start all strong but rather a stage approach, from a simple medium say hidden account and balances, to a later stage where addresses and other transactions can be hidden according to one's required needs.

Deep Read 05

ZK + Note — Stronger Privacy Does Not Mean a Better Default Architecture

If stronger privacy can hide not only amounts, but also recipient linkage and transaction graphs, why shouldn’t it be the default?

DKSAP + Note is a clear example.

🔹 UX — Note scanning, change handling & proof generation add complexity
🔹 Proof cost — proof generation, verification & circuit complexity
🔹 Compliance — strong privacy should be optional, not the default objective

Positioning:
Optional strong privacy mode.

Near term: lightweight account-based amount privacy first, then gradually add strong privacy and tracing.

From PlatON’s Technical Research Report on Confidential Token Transfers.

Deep read 05 like other thread also create a tabular approach where it is further simplified and you can read it's entirety on PlatON X page here Deep read 05

Till next time, do have fun and happy weekend.