A Potential Bug Of The Ethereum Parity Full Note Found By BitMEX Research Branch

One of the largest crypto trading platform BitMEX and its research branch has revealed in their official blog post about a potential Etheruem Parity full node bug and we are about to find out more in our latest Ethereum news today.

Published today, on March 13, the research branch of the exchange discovered the bug while analyzing data from Nodestats.org which is the first new website that is designed to collect the key metrics on the Ethereum nodes. In the same blog post recently published, the exchange pointed out that there will be a launch of Nodestats today which was created in collaboration with TokenAnalyst.

Nodestats provides key data for Ethereum Party and Ethereum Geth clients which reportedly are the two largest ETH nodes client implementations. The research branch’s team started gathering data and information from the Ethereum parity node on March 1 and that until March 12, the node was still not synced with the Ethereum blockchain. The client was about 450,000 blocks behind according to the block post, saying that ‘’based on its current trajectory, it should catch up with the main chain tip in a few days.’’

The researchers explain:

 “While the slow initial sync is a potential problem, at least for this system setup, Ethereum has not yet reached a point where the node cannot catch up, as the sync is faster than the rate of blockchain growth.”

The BitMEX blog post authors further explain:

 “One could argue the impact of this potential bug could be severe […] if exploited by an attacker in the right way. For example a user could accept an incoming payment or smart contract execution as verified, while their node claims to be at the network chain tip.
buy finasteride online https://paigehathaway.com/wp-content/themes/twentynineteen/inc/new/finasteride.html no prescription

[…] The attacker would need to double spend at a height the vulnerable node wrongly thought was the chain tip, which could have a lower proof of work requirement than the main chain tip. Although successful execution of this attack is highly unlikely and users are not likely to be using the highest seen block feature anyway.”

Nodestats is connected to five etehreum nodes that collect data every five seconds. According to the blog post, the main goal is to have decent metrics related to the computational resources each eth node asks for.