Gearing up to the end of PlatON confidential token report and I must say, the past couple of weeks have been nothing short of exceptional as each thread comes with newer information into a topic you once thought you had absolute idea about. From what are confidential tokens to the need of confidential token and the practical approach into confidential tokens.
Just like previous threads prior to now, thread 9 of 10 will also be looking into the practical approach for token confidentiality and today's thread is on Solution Deep Dive — PlatON Privacy Solution.
Yes you read that right, today's thread is focused on PlatON Privacy Solution, one you might have been looking forward to, afterall the topic literally says PlatON confidential token report.
The PlatON solution can be summarized as follows: use Notes to represent private assets, use DKSAP to generate one-time receiving addresses to reduce recipient address linkage, use range proofs to prove amount validity, and support authorized tracing or regulatory disclosure through tracing ciphertexts/tracing keys.
The approach is broken down into 3 various stages, from token/asset represention to authorized tracing or regulatory disclosure when a need arise.
Three building blocks
🔹 Note — represents private assets
🔹 DKSAP — generates one-time receiving addresses to reduce recipient address linkage
🔹 Tracing ciphertexts / tracing keys — support authorized tracing or regulatory disclosure.
This approach doesn't just ensure reduction in address linkage, by generating a single one time recipients address but it also creates an option where assets can be verified for various official reasons, say auditing and others.
The thread further goes on explaining the various key takeaway for why PlatON Privacy Solution to recommendation.
As usual, to read the entirity of thread 9, then click the link below PlatON. Don't forget to follow and turn on notifications on PlatON various social platforms to get new and trending info as they come by.