The co -founder of Ethereum, Vitalik Buterin, outlined an intensive plan to enhance the privacy of the network he created.
In a roadmap of April 11, however the button spoke for the inclusion of knowledge protection instruments in Ether (Eth) -Woleisen and the implementation of norms and characteristics of knowledge protection within the Ethereum ecosystem and the protocol of privacy. He explained that the roadmap in query is a brief -term solution that requires only limited changes to the essential protocol and extra long -term updates.
According to the plan, but based on the plan, Berin recommends the introduction of knowledge protection systems corresponding to railgun or data protection pools through existing wallets. If funds are sent with these wallets, he argues that users must be welcomed from the choice to “send off sensible balance”, which must be anonymized and “ideally switched on” by default. He wrote:
“Users shouldn’t download a separate” data protection letter bag “.”
Main changes really helpful for Defi
Buterin really helpful profound changes in implementing decentralized financing (Defi) and wider -based decentralized applications (DAPP). He argued that these systems must be limited to “one address per application”.
The co -founder of Ethereum admitted that this might require “significant potential convenience”, however it is “essentially the most practical technique to eliminate public connections between all of your activities across different applications”. He also emphasizes that the user experience in Crisschain Interoperability Systems is “very similar” to take funds from one other chain.
Buterin also emphasized that developers to enjoy the benefits of this modification be certain that the user decision functions are issued by default for data protection regulations.
The Ethereum Protocol changes
Further changes are the implementation of fork-choice inclusion lists (FOCIL) and the EIP proposal (Ethereum Improvement Proposal) 7701. The latter is an improvement within the abstraction of Ethereum account, and the previous is an improvement in censor resistance.
Fokil functionality diagram. Source: Ethereum research
EIP-7701 ensures that data protection protocols can work without relays or public broadcasters. This in turn simplifies the event and maintenance of this kind of protocol.
In this context, relay intermediaries or nodes are accountable for the acceptance and forwarding of transactions. On the opposite hand, broadcasters are accountable for publishing transactions to the general public blockchain.
EIP-7701 divides Ethereum transactions into phases and enables third parties to enter and pay the fees in the right phase. This signifies that a relay shouldn’t be crucial to transmit the private transactions of the users anonymously from a separate company.
On the opposite hand, FOCIL prevents the censorship of transactions, including privacy that the current. The relevance might be that anonymized transactions have a significantly higher risk of falling victim to censorship attempts.
Infrastructure changes are required
A brief-term solution to combat the info protection restrictions of RPC systems (Remote Remote Procedure Call), that are used to interact with the blockchain proposed by Buterin, is the implementation of a trustworthy execution environment (tea).
Tea is a protected area inside a processor that ensures that code and data which might be loaded in it are protected. Buterin said: “This enables users to interact with RPC nodes and at the identical time to take care of stronger assurances that their private data shouldn’t be collected.”
As a long-term solution, T-shirts must be replaced by a non-public information call system (PIR). Pir is a cryptographic protocol with which users can access a certain element from a database without indicating which element has been called up.
In this fashion, users can access data via the blockchain content without the provider knowing which data is shared. Buterin emphasized that it’s superior since it offers “cryptographic guarantees”.
The Ethereum co-founder also argued that items must be connected to several RPC servers. You must also use a separate RPC Pro Dapp and possibly a mixnet-a data protection improvement technology that was developed for the coverage of metadata.
Further recommendations are the event of proof aggregation protocols for data protection protocols. This would result in significantly lower fees for using such systems.
