Avatar
b10c
b10c0000079a83cf26815dc7538818d8d56a2983e374e30a4143e50060978457
Bitcoin developer and observer

Happy Birthday, LinkingLion!

A year ago I reported about LinkingLion, an entity that's presumably linking transactions to IP addresses and has been opening hundreds of connections per minute to my monitoring nodes.

An update: https://b10c.me/blog/013-one-year-update-on-linkinglion/

Update on LinkingLion: Reduced activity and a statement by LionLink Networks

https://b10c.me/blog/013-one-year-update-on-linkinglion/

tl;dr: ViaBTC didn't check the header merkle root in their P2P client. Sending a block message with an old header and a modified coinbase transaction caused them to SPV mine on the old header for 30s at a time. I responsibly disclosed this to ViaBTC, and they awarded 2000 USDT.

In January, while investigating a misbehaving client on the Bitcoin P2P network, I found a vulnerability in ViaBTC's SPV mining code that allowed a remote attacker to waste their 60 EH/s hashrate by sending a single, crafted Bitcoin P2P message.

https://b10c.me/blog/012-viabtc-spv-vulnerability-disclosure/

I took a look at non-standard transactions in the last 117k blocks. Here's an overview:

https://b10c.me/observations/09-non-standard-transactions/?n

My miningpool-observer project recently reported six OFAC-sanctioned transactions as missing from blocks.

Four of these transactions were likely filtered by F2Pool. This is the first filtering based on OFAC sanctions I've seen.

More in: https://b10c.me/observations/08-missing-sanctioned-transactions?n

MaraPool mined an invalid block at 809478 on mainnet. I observed the block on 9 out of 9 nodes.

ERROR: ConnectTip: ConnectBlock 000000000000000000006840568a01091022093a176d12a1e8e5e261e4f11853 failed, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent

https://void.cat/d/3XxZTGnzrUdNhxHkCJ5ENg.webp

Replying to Avatar b10c

![]()

do normal, animated PNGs work too? ![]()

hello high-PoW world