Hi guys and welcome to another writeup on PlatON lately, a continuation from thread 5 of 10. As mentioned earlier, subsequent post will be focused on the various technical approach involve in achieving token confidentiality and today's writeup is on Inco & Aleo.
One of the key approach in token confidentiality basically revolve around EVM compatibility, the goal is not to create an entire new system but rather work on existing system towards achieving desired goal and Inco does basically this.
Inco extends EVM with a modular confidential computing layer, primarily built around Zama fhEVM.
Developers can integrate confidential computing into existing smart contracts to support:
🔹 Encrypted state
🔹 Private inputs
🔹 Access control
without changing the underlying application model.
As mentioned on thread 5 of 6, the approaches involve in token confidentiality are usually separated into 2 various forms and one basically using EVM compatibility while the other might be somewhat related but also create a distinct approach and this fall under Aleo.
Aleo takes a very different path.
Instead of extending EVM, it builds a native private application architecture around Zero-Knowledge Proofs.
Users generate proofs locally.
The blockchain verifies proofs and updates state.
Private data is never exposed on-chain by default.
The technical term are further broken down with each having the why and how which you can read it entirety directly from PlatON X page here https://x.com/PlatON_Network/status/2074697917240336481
As usual, don't forget to follow PlatON various social platforms to get new and trending info as it comes.
