<p>Disclaimer: I proposed a partial solution myself to this problem (BIP 143, see below).</p>

<blockquote>
  <p>Did the miner collude with the creator of the transaction?</p>
</blockquote>

<p>Yes, because they are the same person.</p>

<p>It's a transaction that consumes a ton of dust outputs, and converts them to fees, which the miner claimed.</p>

<p>I doubt that the intention was to cause problems; it may just have been an attempt to clean up a lot of dust at once.</p>

<p>However, it did make it more obvious that the theoretical problem of quadratic hashing time for verification of blocks was real. The cause is that every signature requires computing a different hash, and that that hash is computed using the entirety of the transaction as input. Thus, if the number of signature checks in a transaction grows, both the number of hashes to compute as the amount of data each of them needs to hash increases.</p>

<p>Several solutions have been proposed:</p>

<ol>
<li>Limiting the maximum size of transactions.</li>
<li>Limiting the total amount of data hashed by a transaction.</li>
<li>Changing the way hashes are computed.</li>
</ol>

<p>1 (and to a lesser extent 2) would harm potentially useful large transactions in the future, depending on what the limits are. In particular, scaling solutions that rely on collapsing multiple payments into a single transaction may get hurt.</p>

<p>Deploying 3 for existing transaction outputs would require a hard fork, and a change to every piece of wallet software. Additionally, it would invalidate any pre-signed but unbroadcast transaction.</p>

<p>However, 3 can be deployed for a new type of transaction output. <a href="https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki">BIP 143</a> describes a new signature hashing mechanism that is at worst linear in the size of blocks, but only applies to transaction inputs that spend segregated witness outputs (see <a href="https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki">BIP 141</a>).</p>

CC BY-SA 3.0
2016-02-06T13:28:43.267Z
2016-02-06T13:39:33.670Z
2016-02-06T13:39:33.670Z
Pieter Wuille
<p>Excellent answer by Pieter Wuille. Pieter just forgot to answer the question of the post title, "Who mined the infamous block 364423?"
Unfortunately, the question <del>is </del> was "wrong": the first two links in the OP's text point at block 364422, not 364423. (edit: meanwhile the OP removed the discrepancy)<br>
Either way, both
Bitcoin blocks 364422 and 364423 had been mined by F2Pool (also called "DiscusFish"). The outputs went to the Bitcoin address 1KFHE7w8BhaENAswwryaoccDb6qcT6DbYY which belongs to F2Pool, see <a href="https://github.com/blockchain/Blockchain-Known-Pools/blob/master/pools.json">https://github.com/blockchain/Blockchain-Known-Pools/blob/master/pools.json</a><br>
Both blocks were merged-mined with Namecoin blocks 238371 and 238372 respectively. The coinbase string of Bitcoin block 364422 as well as the auxPoW data in Namecoin block 238371 contain "新視野號距冥王星6951602公里" (Chinese for: "New Horizons' distance to Pluto: 6951602 km"). The coinbase string of Bitcoin block 364423 as well as the auxPoW data in Namecoin block 238372 contain "New Horizons is 6948752 km to Pluto" (this time in English). One of the pool operators at F2Pool wrote a script that inserted the current distance of NASA's New Horizons probe from Pluto into the coinbase string. After the arrival of the NASA probe he removed that script, and the F2Pool coinbase string contains the usual F2Pool info as before. Amongst other data this includes "七彩神仙鱼", "Discus Fish" in Chinese language.</p>

<blockquote>
  <p>Yes, because they are the same person.</p>
</blockquote>

<p>I guess Pieter is refering to Wang Chun. There is a little message in the tx output script: "七彩神仙鱼  Bitcoin to Pluto!"</p>

CC BY-SA 3.0
2016-02-06T14:29:04.033Z
I fixed the block number to match Gavins slides. Thanks for pointing that out.
boot4life
CC BY-SA 3.0
2016-02-06T14:41:48.807Z
Upvoted. This answers the original question better :)
Pieter Wuille
CC BY-SA 3.0
2016-02-06T14:20:04.567Z
2016-02-06T14:49:35.903Z
2016-02-06T14:49:35.903Z
cassini
<p><a href="https://blockchain.info/block/000000000000000000283e9409575c2426cd72fcb722065431c52b5083e5bb58">Block 364422</a> contains a <a href="https://blockchain.info/tx/5d8875ed1707cfee2221741b3144e575aec4e0d6412eeffe1e0fa07335f61311">transaction</a> that takes a long time to verify. This transaction design demonstrates a way a denial of service attack could be executed. <a href="https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009494.html">This prompted Gavin Andresen to propose additional limits to the protocol.</a></p>

<p>Gavin talks about this issue in <a href="https://www.youtube.com/watch?v=j5OjMdqkiiI&amp;t=662">this video</a>.</p>

<p>Is it known who mined this particular block? What was their intention? Did they collude with the person who generated the transaction?</p>

<transactions><security><block>
Who mined the infamous block 364422?
boot4life
# Who mined the infamous block 364422?

(Asked by: username_0 on 2016-02-06)

[Block 364422](https://blockchain.info/block/000000000000000000283e9409575c2426cd72fcb722065431c52b5083e5bb58) contains a [transaction](https://blockchain.info/tx/5d8875ed1707cfee2221741b3144e575aec4e0d6412eeffe1e0fa07335f61311) that takes a long time to verify. This transaction design demonstrates a way a denial of service attack could be executed. [This prompted Gavin Andresen to propose additional limits to the protocol.](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009494.html)

Gavin talks about this issue in [this video](https://www.youtube.com/watch?v=j5OjMdqkiiI&t=662).

Is it known who mined this particular block? What was their intention? Did they collude with the person who generated the transaction?

**Tags:** transactions, security, block


---

## 2 answers

### Answer by username_2 on 2016-02-06. Score: 9 | Accepted answer

Excellent answer by username_1 username_1. username_1 just forgot to answer the question of the post title, "Who mined the infamous block 364423?"
Unfortunately, the question ~~is~~  was "wrong": the first two links in the OP's text point at block 364422, not 364423. (edit: meanwhile the OP removed the discrepancy)  
Either way, both
Bitcoin blocks 364422 and 364423 had been mined by F2Pool (also called "DiscusFish"). The outputs went to the Bitcoin address 1KFHE7w8BhaENAswwryaoccDb6qcT6DbYY which belongs to F2Pool, see <https://github.com/blockchain/Blockchain-Known-Pools/blob/master/pools.json>  
Both blocks were merged-mined with Namecoin blocks 238371 and 238372 respectively. The coinbase string of Bitcoin block 364422 as well as the auxPoW data in Namecoin block 238371 contain "新視野號距冥王星6951602公里" (Chinese for: "New Horizons' distance to Pluto: 6951602 km"). The coinbase string of Bitcoin block 364423 as well as the auxPoW data in Namecoin block 238372 contain "New Horizons is 6948752 km to Pluto" (this time in English). One of the pool operators at F2Pool wrote a script that inserted the current distance of NASA's New Horizons probe from Pluto into the coinbase string. After the arrival of the NASA probe he removed that script, and the F2Pool coinbase string contains the usual F2Pool info as before. Amongst other data this includes "七彩神仙鱼", "Discus Fish" in Chinese language.

> Yes, because they are the same person.

I guess username_1 is refering to Wang Chun. There is a little message in the tx output script: "七彩神仙鱼 Bitcoin to Pluto!"

> **Comments:**
> **username_0**: I fixed the block number to match Gavins slides. Thanks for pointing that out.  
> **username_1**: Upvoted. This answers the original question better :)  

---

### Answer by username_1 on 2016-02-06. Score: 10

Disclaimer: I proposed a partial solution myself to this problem (BIP 143, see below).

> Did the miner collude with the creator of the transaction?

Yes, because they are the same person.

It's a transaction that consumes a ton of dust outputs, and converts them to fees, which the miner claimed.

I doubt that the intention was to cause problems; it may just have been an attempt to clean up a lot of dust at once.

However, it did make it more obvious that the theoretical problem of quadratic hashing time for verification of blocks was real. The cause is that every signature requires computing a different hash, and that that hash is computed using the entirety of the transaction as input. Thus, if the number of signature checks in a transaction grows, both the number of hashes to compute as the amount of data each of them needs to hash increases.

Several solutions have been proposed:

1. Limiting the maximum size of transactions.
2. Limiting the total amount of data hashed by a transaction.
3. Changing the way hashes are computed.

1 (and to a lesser extent 2) would harm potentially useful large transactions in the future, depending on what the limits are. In particular, scaling solutions that rely on collapsing multiple payments into a single transaction may get hurt.

Deploying 3 for existing transaction outputs would require a hard fork, and a change to every piece of wallet software. Additionally, it would invalidate any pre-signed but unbroadcast transaction.

However, 3 can be deployed for a new type of transaction output. [BIP 143](https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki) describes a new signature hashing mechanism that is at worst linear in the size of blocks, but only applies to transaction inputs that spend segregated witness outputs (see [BIP 141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki)).


---

