{"id":18150,"date":"2026-03-10T14:48:06","date_gmt":"2026-03-10T14:48:06","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/10\/dodging-a-bullet-ethereum-state-problems\/"},"modified":"2026-03-10T14:48:06","modified_gmt":"2026-03-10T14:48:06","slug":"dodging-a-bullet-ethereum-state-problems","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/10\/dodging-a-bullet-ethereum-state-problems\/","title":{"rendered":"Dodging a bullet: Ethereum State Problems"},"content":{"rendered":"


\n<\/p>\n

\n

With this blog post, the intention is to officially disclose a severe threat against the Ethereum platform, which was a clear and present danger up until the Berlin hardfork.<\/p>\n

<\/g><\/svg><\/a>State<\/h2>\n

Let’s begin with some background on Ethereum and State.<\/p>\n

The Ethereum state consists of a patricia-merkle trie, a prefix-tree. This post won’t go into it in too much detail, suffice to say that as the state grows, the branches in this tree become more dense. Each added account is another leaf. Between the root of the tree, and the leaf itself, there are a number of “intermediate” nodes.<\/p>\n

In order to look up a given account, or “leaf” in this huge tree, somewhere on the order of 6-9 hashes need to be resolved, from the root, via intermediate nodes, to finally resolve the last hash which leads to the data that we were looking for.<\/p>\n

In plain terms: whenever a trie lookup is performed to find an account, 8-9 resolve operations are performed. Each resolve operation is one database lookup, and each database lookup may be any number of actual disk operations. The number of disk operations are difficult to estimate, but since the trie keys are cryptographic hashes (collision resistant), the keys are “random”, hitting the exact worst case for any database.<\/p>\n

As Ethereum has grown, it has been necessary to increase the gas prices for operations which access the trie. This was performed in Tangerine Whistle<\/span> at block 2,463,000<\/span> in October 2016, which included EIP 150<\/a>. EIP 150 aggressively raised certain gascosts and introduced a whole slew of changes to protect against DoS attacks, in the wake of the so called “Shanghai attacks”.<\/p>\n

Another such raise was performed in the Istanbul<\/span> upgrade, at block 9,069,000<\/span> in December 2019. In this upgrade, EIP 1884<\/a> was activated.<\/p>\n

EIP-1884 introduced the following change:<\/p>\n