<p>To add to Murch's answer:</p>
<p>The output was created by Matthew Zipkin to test support for sending to SegWit v1 support on purse.io. This was done in the context of the <a href="https://bitcoinops.org/en/compatibility/" rel="noreferrer">Bitcoin Optech Compatibility Matix</a>.</p>
<p>Here is a screenshot of the purse.io withdrawal that was added in <a href="https://github.com/bitcoinops/bitcoinops.github.io/pull/303" rel="noreferrer">PR 303</a> to the Bitcoin Optech website.</p>
<p><a href="https://i.sstatic.net/PKQBe.png" rel="noreferrer"><img src="https://i.sstatic.net/PKQBe.png" alt="transaction sending to P2TR output in 2019" /></a></p>

CC BY-SA 4.0
2021-07-19T14:38:22.997Z
2021-07-19T14:38:22.997Z
0xb10c
<p>The first output of transaction <a href="https://blockstream.info/tx/b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141?expand" rel="noreferrer">b53e3bc5…5377f141</a> has the following <code>scriptPubKey</code>:</p>
<pre><code>OP_PUSHNUM_1 OP_PUSHBYTES_32 01010101…0101010101
</code></pre>
<p>The segwit softfork in 2017 defined versioning rules for all native segwit outputs, but only defined spending rules for version 0.¹</p>
<p><a href="https://i.sstatic.net/ljyXg.png" rel="noreferrer"><img src="https://i.sstatic.net/ljyXg.png" alt="Output details via blockstream.info" /></a></p>
<p>This output worth 5431 satoshis matches the native segwit schema, but the leading <code>OP_PUSHNUM_1</code> indicates that it is a version 1 output. It shows up as &quot;Type: UNKNOWN&quot;, because there are currently no spending rules for version 1 outputs active on the network. Therefore, this output could be spent by anyone, as long as they get a miner to include a non-standard transaction in their block that claims the funds.</p>
<p>We are anticipating the activation of the Taproot softfork in November, which will give exactly this output pattern meaning (see <a href="https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki" rel="noreferrer">BIP341</a>): Pay to Taproot (P2TR) outputs will be version 1 native segwit outputs with a 32-byte witness program that consists only of a public key.</p>
<p>Finally, the public key 01010101…01010101 here is obviously not randomly derived from a private key, so the private key can be assumed to be unknown. The corresponding address will essentially become a &quot;burn address&quot; once Taproot activates and spending of funds received there must follow Taproot's rules.</p>
<p>I surmise that whoever created this output in 2019 simply wanted to be the first person to create a Taproot output on the blockchain and was willing to burn a few satoshis on that.</p>
<hr />
<p><sup>¹There are two output types defined in version 0: Pay to Witness Public Key Hash (P2WPKH) and Pay to Witness Script Hash (P2WSH).</sup></p>

CC BY-SA 4.0
2021-07-17T12:36:01.653Z
2021-07-17T12:36:01.653Z
Murch
<p>I found a <a href="https://www.blockchain.com/btc/tx/b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141?page2=1" rel="noreferrer">transaction</a> in the Bitcoin blockchain. The first output is unspent and has an abnormal Pkscript. What is this output and why does this output address have no transaction and balance on it?</p>
<p>Link to transaction: <a href="https://www.blockchain.com/btc/tx/b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141?page2=1" rel="noreferrer">b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141</a></p>

<transactions><output><taproot><non-standard-transaction>
What is this unusual transaction in the Bitcoin blockchain?
mshomali
# What is this unusual transaction in the Bitcoin blockchain?

(Asked by: username_0 on 2021-07-17)

I found a [transaction](https://www.blockchain.com/btc/tx/b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141?page2=1) in the Bitcoin blockchain. The first output is unspent and has an abnormal Pkscript. What is this output and why does this output address have no transaction and balance on it?

Link to transaction: [b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141](https://www.blockchain.com/btc/tx/b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141?page2=1)

**Tags:** transactions, output, taproot, non-standard-transaction


---

## 2 answers

### Answer by username_2 on 2021-07-17. Score: 13 | Accepted answer

The first output of transaction [b53e3bc5…5377f141](https://blockstream.info/tx/b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141?expand) has the following `scriptPubKey`:

```
OP_PUSHNUM_1 OP_PUSHBYTES_32 01010101…0101010101

```

The segwit softfork in 2017 defined versioning rules for all native segwit outputs, but only defined spending rules for version 0.¹

[![Output details via blockstream.info](https://i.sstatic.net/ljyXg.png)](https://i.sstatic.net/ljyXg.png)

This output worth 5431 satoshis matches the native segwit schema, but the leading `OP_PUSHNUM_1` indicates that it is a version 1 output. It shows up as "Type: UNKNOWN", because there are currently no spending rules for version 1 outputs active on the network. Therefore, this output could be spent by anyone, as long as they get a miner to include a non-standard transaction in their block that claims the funds.

We are anticipating the activation of the Taproot softfork in November, which will give exactly this output pattern meaning (see [BIP341](https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki)): Pay to Taproot (P2TR) outputs will be version 1 native segwit outputs with a 32-byte witness program that consists only of a public key.

Finally, the public key 01010101…01010101 here is obviously not randomly derived from a private key, so the private key can be assumed to be unknown. The corresponding address will essentially become a "burn address" once Taproot activates and spending of funds received there must follow Taproot's rules.

I surmise that whoever created this output in 2019 simply wanted to be the first person to create a Taproot output on the blockchain and was willing to burn a few satoshis on that.

---

¹There are two output types defined in version 0: Pay to Witness Public Key Hash (P2WPKH) and Pay to Witness Script Hash (P2WSH).


---

### Answer by username_1 on 2021-07-19. Score: 5

To add to username_2's answer:

The output was created by Matthew Zipkin to test support for sending to SegWit v1 support on purse.io. This was done in the context of the [Bitcoin Optech Compatibility Matix](https://bitcoinops.org/en/compatibility/).

Here is a screenshot of the purse.io withdrawal that was added in [PR 303](https://github.com/bitcoinops/bitcoinops.github.io/pull/303) to the Bitcoin Optech website.

[![transaction sending to P2TR output in 2019](https://i.sstatic.net/PKQBe.png)](https://i.sstatic.net/PKQBe.png)


---

