Can Ethereum be private? Pushed by the developers for the airpled Mempool, Default Privacy
When the US government allows the Crypto Mixing Service Tornado Cash Crypto Mixing Service Cash, it will notice a debate within the crypto community that continues three years later.
Tornado enables users to transfer crypto anonymously. The government has argued that the service has facilitated the money laundering, which motivates some of the Ethereum validators and block builders who have taken steps to prevent contact with tornado-related transactions, which has become slower and cheaper service.
Proponents argue that compliance with penalties is worth censorship – which bothers a basic Cypherpunk principle. President Donald Trump supported Cypherpunks and Raised penalties In Tornado Cash in March of this year, but for some Ethereum developers, the situation has highlighted a flaw within the network that still exists today: why should users depend on third-party apps that transact privately to the network?
“The graphs of the transaction publicly allow anyone to monitor the flow of funds between In a blog post On Wednesday. “While the transparency of the Ethereum network promotes being distrustful, it also opens the door to potential monitoring, targeting, and exploitation.”
Perhaps reinforced by recent tornado cash developments, Ethereum developers and researchers have begun discussing ideas for making Ethereum’s private network at its core.
“Privacy should not be an optional feature that users should enable-it should be the default state of the network,” said Cavesaccio, whose post outlines its vision for a privacy-focused roadmap. “Ethereum architecture must be designed to ensure that users are private by default, not by exclusion.”
Cavesaccio’s post recognized some potential interventions-some new ones, some old-fashioned, according to him, would make Ethereum more private for end-users. An idea is to have Ethereum’s public mempool – where transactions were sent before they were permanently recorded. Another involves making Ethereum transactions confidential through zero-knowledge cryptography, new transaction formats, and other methods.
“Today, Ethereum operates in a slight, opt-in privacy model, where users should take deliberate steps to hide their financial activities-often at the expense of usability, access, and even effectiveness,” Caversaccio wrote. “This paradigm should move. Privacy-sending technologies should be deeply integrated with protocol levels, allowing transactions, intelligent contracts, and network interactions to become naturally confidential.”
In response to Cavesaccio’s post, Ethereum co-founder Vitalik Blerin left a Comment on the main network developer forum with himself Most shorter privacy-oriented Ethereum Roadmap.
Buterin suggested that privacy for on-chain payments, not introducing on-chain activity within applications, making network anonymous network, and privatizing on-chain read.
To achieve all of this, the bakerin listed various steps such as integrating some third-party privacy features into the main network.
One of the larger interventions that Blerin suggested involves moving the network to a “one address per application” model -a removal from the system today, where a single application can use twelve purses for a variety of features. “This is a basic step, and requires significant sacrifices of comfort, but IMO is a bullet we must bite, because it is the most practical way to eliminate public links between all your activity in different applications,” wrote Baterin.
According to Baterin, if all of his suggestions are implemented, private transactions can default to Ethereum.
Privacy discussion will come a few weeks before Ethereum Next basic upgradePectra, with no main focus on privacy. Ethereum developers are also currently planning to follow the network upgrade to FUSAKA. The changes included in the hard fork have not been placed on the stone.
Read more: Vitalik Blerin failed to embrace blockchain’s “casinos”
