Previously on PlatON lately thread 6 of 10, we talked about Inco & Aleo and how subsequent writeup would be focused on deepdive into the various technical approach leading to token confidentiality, and for those just finding this writeup or joining the series of thread, you can browse through my page or read the entirity of thread 6 of 10 here @otemzi/platon-lately-thread-6-of-10.
Today's writeup is a continuation of PlatON confidential token report(the technicalities), and today's writeup will be on Aztec & TACEO Merces.
Why Aztec?
Aztec hides transaction details through privacy Rollups and ZK proofs.
Users execute private transfers and contract logic on L2; the main chain primarily verifies aggregated proofs and state updates.
Aztec focuses on L2's system to create a stronger backend system instead of direct replication of EVM-compatible chains. It is mostly used for mid - long term infrastructure as it helps to amortize proof costs, and it also creates strong privacy for complex private DeFi. TACEO Merces on the other hand,
it adopts an MPC shared-state approach.
creates multiple parties jointly maintain and compute private balances, and ensure the correctness of state updates through proofs or verification mechanisms.
Users interact with an ERC-20-like asset interface; the underlying MPC network processes private computation.
The major key takeaway would likely be its multiple parties system especially in high end organization where multiple individuals needs consensus to validate various payment batch and what have you. While maintenance and upkeep might be on the high end, trust and safer backend would likely push elite teams and companies to go for TACEO Merces.
For complete breakdown or deepdive into Aztec & TACEO Merces, read the entire thread via PlatON official X page here https://x.com/PlatON_Network/status/2075415367418261599.
As usual, don't forget to follow PlatON on it's various social platforms to get new and trending info as they come by.
