False Send Transactions With Fee of 2.5BTC

Wrong sending Transaction. One bitcoin user, made a mistake when making a delivery transaction bitcoin. Someone with the name Voiceeeeee, conveying the problem in the bitcointalk forum. He admitted that the funds are a savings fund for his college needs.

At that time, Voiceeeeee intend to send a total of 0.24701244 BTC on two output addresses, on March 8 last. In the details of the transaction, the transaction size is 2051 bytes, and the fee value per byte is 121,891,76 satoshi. So of course, it is true that the total fee reached a total of 2.5 BTC.

Voiceeeeee transaction details, transaction fee of 2.5 BTC
So, with a large enough fee, the transaction was indeed able to process with a relatively faster time. But Voiceeeee appears to realize the mistake he made, and immediately post on the forum to ask for help.

When his complaint was made in the Bitcointalk forum shortly after he found out about his mistake, he got a lot of advice from other forum members who helped solve the problem. One with the name xhomerx10, then try to help by making a ticket support to the Bitmain. The search how to conclude that the transaction is related to Bitmain, of course this can be easily searched.

We certainly remember that all transactions in bitcoins are stored in new blocks generated every 10 minutes on average by miners. Thus, the next miner who processes the new block is valid, will get a reward block and all transaction fees in the new block.

In this case, the transaction with ID 4d45a14ee73 ....... is inserted in the block with number #456363. While on the new block, successfully relayed by AntPool, a pool made from Bitmain. Because blockchain is open ledger and can be accessed by public details, then detail block can be traced.

A block containing a Voiceeeeee transaction, generated by Antpool.
The attempt by Xhomerx10 by sending a support ticket to Bitmain, is to share the details and chronological issues due to the transaction's fault. As a result, the Bitmain was immediately coordinate with the pool besutannya, AntPool. According to Bitmain, the transaction error is purely a user's own fault.

Bitmain party, explained about the reward fee obtained from the new block numbered # 456363, has been distributed completely to the mining participants in the pool AntPool. Of course, with a typical pool pattern that uses PPS and PPLNS, then reward results may soon be distributed to all mining participants.

Response from Bitmain

In casuistic misinformation such transactions, if the error is due to user error itself, it is not possible to try to get back the transaction fee. Bitmain party also felt quite regret it until the bias occurred.

Voiceeeeee lucky fate in this event. Although Bitmain realizes that the transaction error is the sender's own fault, but the Bitmain, decided to replace it. The result, on March 14 last, on the Voiceeeee's Address, successfully received back 2.5 BTC.

Voiceeeeee receives 2.5 BTC from Address 1L75eRMgeCwAxEjD1oWXjLgud9jxwxm34u

If searched further, the sender's Address, is, 1L75eRMgeCwAxEjD1oWXjLgud9jxwxm34u. While in that address, the recent transaction has a lot to do with coinbase transactions (creation of new bitcoin units). So it is strongly suspected that the address is the Antpool address of Bitmain, which previously intended to replace the transaction's fault.

This address often receives coinbase transactions (transactions for awarding new rewards block marked with no input).

From the misplaced events of this transaction, we certainly can take a lot of things, so in the future, when doing bitcoin transactions must be full of thoroughness, so as not to repeat the mistakes that occur. Reflecting on what happened to Voiceeeeee, still fared well if it turns out the Bitmain want to replace errors that are not made by it or Antpool. What if the pool does not want to change? Of course we alone must bear the consequences of our own mistakes.

While on the other hand, we can see for ourselves the benefits of so transparent recording of these bitcoin transactions. Thus, what Xhomerx10 and others do, is able to try to help solve the problem. It's all easy to do, because recording transactions inside a blockchain is quite transparent, detailed, and can not be manipulated. Likewise also in this event, the Bitmain and Antpool, can also browse the details of transactions that occur. When did see the details of the transaction with a fee of 2.5 BTC.