Ethereum privacy framework Kohaku integrates Helios light client and TEE technology

ETH2.07%

Gate News, April 1, Vitalik Buterin and Ethereum Foundation researcher Nicolas Consigny disclosed the latest progress of the privacy framework Kohaku at the EthCC[9] conference. This update has shifted from the early focus on integrating upper-layer privacy protocols to combining the network layer, hardware layer, and light clients.

Kohaku directly integrates the Helios light client into a wallet SDK. Users no longer need to rely on centralized RPC providers such as Infura or Alchemy to achieve native self-verification, cutting off centralized service providers from tracking users’ IP addresses and transaction behavior. On the privacy-reading layer, Kohaku introduces trusted execution environments (TEE) and oblivious random access memory (ORAM) technology, preventing external nodes from learning—through traffic analysis—which account information the user is querying.

In addition, Kohaku also introduces an automated privacy routing mechanism that, by default, creates a separate isolated address space for each DApp the user connects to, fundamentally eliminating address linkage across applications. Nicolas revealed that a dedicated “Kohaku Cohort” has already been established via EPF, aiming to deeply embed the Kohaku framework into Ethereum’s mainstream clients.

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments