Right here is an instance of one of many talked about transactions:
Transaction hash:
93a11caca3555e3022fb85d4802eea79aec52e2b199f4177a9f215b7b15a27cc
From:
- 18hofVCQv8cMDpqDNqSXyrUDffq7MKLxiu | 1.20742839 BTC
To:
- OP_RETURN | 0.00000000 BTC
- 1111111111111111111114oLvT2 | 0.00305000 BTC
- 1111111111111111111114oLvT2 | 0.00305000 BTC
- 18hofVCQv8cMDpqDNqSXyrUDffq7MKLxiu | 1.19954374 BTC
That is possible an try to spam the Bitcoin community with ineffective transactions, filling up the mempool and driving up charges for different customers. It’s unclear who’s behind these transactions, as Bitcoin transactions are pseudonymous and it may be tough to hint them again to particular people or organisations.
The truth that every transaction has two an identical outputs to the burn tackle might be an try to extend the scale of the transaction and due to this fact its impression on the community. In different phrases, quite than sending one transaction with two outputs, the attacker is sending two an identical transactions with one output every.
Anyway, this isn’t a foul factor. The blocks are filling up and full nodes are working as ordinary. An individual with good intentions may view this behaviour as a method of testing the whole Bitcoin community.