ETH postponed the Glamsterdam test grid due to a risk of gas leakage
#What are you talking about#The Ethereum#He is a member of the Democratic Party.ETH#The testnet Hoodi#The price of gas
The developers of Ethereum postponed testing hard fork Glamsterdam on the testnet Hoodi after researchers identified an application that might rely on a hypothesis about computing gas, which upgrades would be altered by Ethereum Foundation requiring different teams to test the code before proceeding further.
When did the turning point occur?
In an update on November 6, Marius van der Wijden, a developer from Ethereum Foundation noted that the Glamsterdam test process would not go into fork phase on Hoodi until problems found in testing were fixed.
The problem is not that the Ethereum network doesn't work, but that existing applications may stop working incorrectly because some rely on assumptions about how gas is thought to process business and run.
Why did the gas change affect the app?
The gas in Ethereum is the cost of doing business and ordering on smart contract , but some developers don't just see gas as a fee, because they also take properties or assumptions about gas into their design work and app testing.
When Ethereum Foundation specifies EIP-8037 and EIP-2 as proposals to be closely scrutinized, this means that if an upgrade changes the billing model, code built on its original assumptions may behave differently even though the app's business logic is not addressed at all.
ChainSecurity found a potentially vulnerable project behind Glamsterdam.
Ethereum Foundation reported that ChainSecurity found a project that may have been affected after Glamsterdam because of invariant or conditions the developer assumed would persist.
Breaking an invariant does not mean that every contract involved is immediately attacked, but it can lead to unexpected behavior, unintentional malfunctions or hidden security holes in the original system.
The engineering team is launching the instruments for inspection.
The engineering team is working with ChainSecurity and Dedaub, in addition to internal auditing, also releasing a repository describing eight related invariants along with examples for developers to audit.
Disclosing this repository is opening up the relevant application teams to participate in review, not just internal protocol discussions because vulnerabilities lie between layers of Ethereum and external code connected to it.
Delay testnet reflects a verification process that is still in progress.
Upgrading blockchain was challenging because it required updating the underlying platform without inadvertently damaging already installed applications. Due to an open network, the developers of Ethereum were unable to verify every third-party contract, outbound connection or app-specific processing path in all cases.
The fact that AllCoreDevs decided not to fork on Hoodi until the problem was fixed indicates that the bottleneck is in checking Glamsterdam's compatibility, rather than stopping development altogether.
Hegota is still moving in parallel.
Ethereum Foundation indicates that work on the next Hegota upgrade will continue in parallel. This separation of duties makes it clear that Glamsterdam still needs to solve its compatibility issue, while Hegota is a development path which should not be paused altogether.
What should the system administrator do next?
For the team that maintains an app or a contract on Ethereum , the appropriate response is to check whether their own code, or systems around them relying on gas assumptions have been altered, then test with updated specifications and note any points that may be affected.
Even if the contract itself looks unchanged, it may be affected if there are other in-app elements that assume a contract's gas consumption such as transaction cost estimation, nonce management or off-chain service timeout settings.
Don't just guess the new deployment date.
The November 6th post doesn't specify a new final deployment date, so predicting when the upgrades will be released is speculation beyond what appears to be data.
The next thing to know is the specification, which can be revised if necessary; confirmation that affected cases have been resolved; successful testing on Hoodi; and a clear indication of what apps might need to be modified.
ETF Flow is not the same as protocol testing.
Activity of Ethereum in the broader context continues to be separate from this test case,NewsBTC having tracked capital flows into it,ETF but should not take fund requirements and protocol engineering together as a single cause.
What's been verified from this news is that Ethereum Foundation chose to pause carefully after discovering a compatibility vulnerability. For networks supporting large amounts of financial activity, pre-deployment vulnerabilities are the crux of the matter.
This article was written by News Desk and edited by Samuel Rae.
It's a warning.
This article is just a collection of information, not investment advice. Highly volatile digital asset prices should be studied and made rational decisions

Comments (0)