<p>All of these addresses were created as part of the <a href="https://github.com/mikeinspace/stamps/blob/main/OLGA.md" rel="nofollow noreferrer">OLGA</a> standard that is used to put arbitrary data into the UTXO set in the form of &quot;fake&quot; P2WSH outputs that are forever unspendable.</p>
<p>The five addresses you posted each belong to a different transaction, whose arbitrary data payloads are:</p>
<ul>
<li>a 1×1 orange (#FF9900) PNG image (<a href="https://mempool.space/tx/e8b00ef950db37b33e3618516afc82710bdef17c3861bb5fb92174ee8556ec57" rel="nofollow noreferrer">1</a>)</li>
<li>a GIF animation (<a href="https://mempool.space/tx/bce265fa2e9ac8cc4e0f4bfcf40ddc9952ca59ed032d1e58cb890c83c097c729" rel="nofollow noreferrer">2</a> and <a href="https://mempool.space/tx/87348d5d8ad543d9d739d4f34f7121b36e860ebe87a461d9389fd1661fba8380" rel="nofollow noreferrer">3</a>)</li>
<li>a SRC-721 token mint (<a href="https://mempool.space/tx/b7a017e88a39de994133671773d8b4fc73ba64de8c323b8eec0e7ddf4246379f" rel="nofollow noreferrer">4</a> and <a href="https://mempool.space/tx/afa63770c1790f89119e3b84bef86bc755822b6f3760b013094491eb074a515e" rel="nofollow noreferrer">5</a>)</li>
</ul>
<p>The reason some of the addresses have a long string of q's before the checksum is because the last output in an OLGA transaction must be 0-padded, and &quot;q&quot; corresponds to 0 in the Bech32 alphabet.</p>

CC BY-SA 4.0
2024-08-09T17:16:17.923Z
Thanks for the answer, it is very useful. I have a last question, using the counterparty decoder (https://jpja.github.io/Electrum-Counterparty/decode_tx) I indeed found the payload of all but the SRC-721 token. How do you know this transaction corresponds to a SRC 721 token. Thanks?
user155892
CC BY-SA 4.0
2024-08-09T17:59:11.163Z
If you run the raw data through an ASCII/UTF8 encoder you'll get a serialized JSON that includes "src-721".
Vojtěch Strnad
CC BY-SA 4.0
2024-09-18T14:31:03.923Z
Vojtěch I am about to complete a paper on bitcoin burn addresses and I would like to add you to the acknowledgements. I would have hard time without you to identify the OLGA standard. Do you accept to be acknowledged and if yes, do you have an affiliation you want me to cite?
user155892
CC BY-SA 4.0
2024-09-18T14:40:38.480Z
Thanks, you can simply link to this post in your citation with my name as the author. I'd be happy to receive a link to your paper once it's available.
Vojtěch Strnad
CC BY-SA 4.0
2024-08-09T15:13:11.363Z
2024-08-09T15:26:04.743Z
2024-08-09T15:26:04.743Z
Vojtěch Strnad
<p>I noticed some bech32 Bitcoin addresses that have a specific structure with a large number of &quot;q&quot;. Here is a few examples:
bc1qmdtv5qqqqqp4qnz5ghlejq9evyuxgqqqqq9yj3zp2sydwcmqqqqq2j6wen
bc1qqyqzr7gyq5qqqqsq9smqqqqqyyqq6qqqqg6ffrepsrrvmgjspk7srnq0kp
bc1qd4sn6vpwxs6ngdf4qqsljpq9q5qqvqpvqyqqzqqcqqwqqqqrmy5q505e7m</p>
<p>Here are other bech32 addresses with a different structure (so most likely a different usage)
bc1q9scnqtpn9sejcdza05qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq5wx2ys
bc1q9scjcvpvxykrqtpn9s6jcvf39sc46lgqqqqqqqqqqqqqqqqqqqqqlcyp97</p>
<p>It looks like they are burn addresses used by a specific (or several) protocols on top of Bitcoin. Any idea which protocol is using such addresses. Link to a documentation on the structure of the addresses would be great.</p>
<p>Thanks.</p>

<bech32-address>
Why some bech32 bitcoin addresses contain a structure with a large number of "q"?
user155892
# Why some bech32 bitcoin addresses contain a structure with a large number of "q"?

(Asked by: username_0 on 2024-08-09)

I noticed some bech32 Bitcoin addresses that have a specific structure with a large number of "q". Here is a few examples:
bc1qmdtv5qqqqqp4qnz5ghlejq9evyuxgqqqqq9yj3zp2sydwcmqqqqq2j6wen
bc1qqyqzr7gyq5qqqqsq9smqqqqqyyqq6qqqqg6ffrepsrrvmgjspk7srnq0kp
bc1qd4sn6vpwxs6ngdf4qqsljpq9q5qqvqpvqyqqzqqcqqwqqqqrmy5q505e7m

Here are other bech32 addresses with a different structure (so most likely a different usage)
bc1q9scnqtpn9sejcdza05qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq5wx2ys
bc1q9scjcvpvxykrqtpn9s6jcvf39sc46lgqqqqqqqqqqqqqqqqqqqqqlcyp97

It looks like they are burn addresses used by a specific (or several) protocols on top of Bitcoin. Any idea which protocol is using such addresses. Link to a documentation on the structure of the addresses would be great.

Thanks.

**Tags:** bech32-address


---

## 1 answers

### Answer by username_1 on 2024-08-09. Score: 2 | Accepted answer

All of these addresses were created as part of the [OLGA](https://github.com/mikeinspace/stamps/blob/main/OLGA.md) standard that is used to put arbitrary data into the UTXO set in the form of "fake" P2WSH outputs that are forever unspendable.

The five addresses you posted each belong to a different transaction, whose arbitrary data payloads are:

* a 1×1 orange (#FF9900) PNG image ([1](https://mempool.space/tx/e8b00ef950db37b33e3618516afc82710bdef17c3861bb5fb92174ee8556ec57))
* a GIF animation ([2](https://mempool.space/tx/bce265fa2e9ac8cc4e0f4bfcf40ddc9952ca59ed032d1e58cb890c83c097c729) and [3](https://mempool.space/tx/87348d5d8ad543d9d739d4f34f7121b36e860ebe87a461d9389fd1661fba8380))
* a SRC-721 token mint ([4](https://mempool.space/tx/b7a017e88a39de994133671773d8b4fc73ba64de8c323b8eec0e7ddf4246379f) and [5](https://mempool.space/tx/afa63770c1790f89119e3b84bef86bc755822b6f3760b013094491eb074a515e))

The reason some of the addresses have a long string of q's before the checksum is because the last output in an OLGA transaction must be 0-padded, and "q" corresponds to 0 in the Bech32 alphabet.

> **Comments:**
> **username_0**: Thanks for the answer, it is very useful. I have a last question, using the counterparty decoder (https://jpja.github.io/Electrum-Counterparty/decode_tx) I indeed found the payload of all but the SRC-721 token. How do you know this transaction corresponds to a SRC 721 token. Thanks?  
> **username_1**: If you run the raw data through an ASCII/UTF8 encoder you'll get a serialized JSON that includes "src-721".  
> **username_0**: username_1 I am about to complete a paper on bitcoin burn addresses and I would like to add you to the acknowledgements. I would have hard time without you to identify the OLGA standard. Do you accept to be acknowledged and if yes, do you have an affiliation you want me to cite?  
> **username_1**: Thanks, you can simply link to this post in your citation with my name as the author. I'd be happy to receive a link to your paper once it's available.  

---

