Marathon Digital Holdings (MARA), a prominent Bitcoin mining company, has reportedly mined an invalid Bitcoin block at height 809478.

According to various developers, miners, and researchers, the invalid Bitcoin block resulted from a wrong transaction ordering.

Anonymous Developer Exposes Transaction Ordering Issue

The issue was first brought to light by an anonymous Bitcoin developer known as 0xB10C, who took to social media platform X to report the incident. According to the developer, the problem originated from a transaction ordering issue within Marathon’s mining pool, known as MaraPool.

“It seems like MARAPool had a transaction ordering issue,” 0xB10C stated in their initial tweet. They then pinpointed the specific transaction that caused the problem. The invalid block contained a transaction identified as the sixth one in the invalid block. This one attempted to spend an output from another transaction, which was the 1,454th transaction in the block.

Notably, the latter transaction was positioned lower down in the block, invalidating the entire block due to improper transaction ordering.

Furthermore, the developer suggested that Marathon Digital might have been running custom code. They stated, “They might be running custom code. Bitcoin Core normally double-checks block validity after creating a block template,” hinting at the possibility of a customized approach that deviated from established practices.

Lopp and BitMEX Confirm Invalid Bitcoin Block Incident

Jameson Lopp, the co-founder of CasaHODL, also weighed in on the matter, responding by confirming this claim.

BitMEX Research, a well-known cryptocurrency research firm, provided additional insights into the situation, stating that the block’s invalidation resulted from incorrectly arranged transactions.

According to BitMEX Research, MARA made an error in arranging their Bitcoin transactions, which resulted in an invalid Bitcoin block at height 809478. This involved including transaction (A) in the block that attempted to use an output from a preceding transaction (B).

They further highlighted that the issue arose because transaction B was wrongly placed in the block after transaction A, resulting in the entire block being invalid. Later on, Marathon confirmed the reports on X.

SPECIAL OFFER (Sponsored)

Binance Free $100 (Exclusive): Use this link to register and receive $100 free and 10% off fees on Binance Futures first month (terms).

PrimeXBT Special Offer: Use this link to register & enter CRYPTOPOTATO50 code to receive up to $7,000 on your deposits.

Leave a Reply

Your email address will not be published. Required fields are marked *