<p><a href="http://blockexplorer.com/tx/930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72" rel="nofollow">930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72</a>
as reported by forum user makomk <a href="https://bitcointalk.org/index.php?topic=33618.msg420597#msg420597" rel="nofollow">here</a>.</p>

CC BY-SA 3.0
2012-04-06T22:46:45.160Z
2012-04-06T22:46:45.160Z
Stephen Gornick
<p><strong>Find it yourself with my preprocessed ASCII strings data</strong></p>
<p>At <a href="https://github.com/cirosantilli/bitcoin-strings-with-txids" rel="nofollow noreferrer">https://github.com/cirosantilli/bitcoin-strings-with-txids</a> I have uploaded a dump of all ASCII strings of length 20 or greater, including scripts to generate that data from a local copy of the blockchain by using <a href="https://github.com/alecalve/python-bitcoin-blockchain-parser" rel="nofollow noreferrer">https://github.com/alecalve/python-bitcoin-blockchain-parser</a></p>
<p>The main difference between my dump and <a href="https://bitcoinstrings.com/blk00003.txt" rel="nofollow noreferrer">https://bitcoinstrings.com/blk00003.txt</a> is that since I parse the blockchain, I am dumping a bit more metadata, notably the transaction IDs.</p>
<p>So if you do:</p>
<pre><code>git clone https://github.com/cirosantilli/bitcoin-strings-with-txids
cd bitcoin-strings-with-txids
git grep 'BEGIN TRIBUTE'
</code></pre>
<p>one of the very few hits will be:</p>
<pre><code>data/out/0138.txt:2:---BEGIN TRIBUTE--- #./BitLen ...
</code></pre>
<p>and then when you open the corresponding file <a href="https://github.com/cirosantilli/bitcoin-strings-with-txids/blob/master/data/out/0138.txt#L2" rel="nofollow noreferrer">data/out/0138.txt#L2</a> you see:</p>
<pre><code>tx 930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72
---BEGIN TRIBUTE--- #./BitLen ...
</code></pre>
<p>Unfortunately my dump does not do automatic newline splitting at the end of every ASCII payload, so this particular ASCII art does not show up correctly.</p>
<p>Before <code>OP_RETURN</code>, payloads were always put into a 20 bytes long address, and this particular ASCII art was intended to have automatic newlines.</p>
<p>However, this prevents ASCII art with lines longer than 20 bytes, with explicit <code>\n</code> added, and so I decided to not automatically add newlines as it allows seeing many more interesting ASCII arts correctly on average.  I did an overview of the most interesting ASCII arts I've found on <a href="https://cirosantilli.com/cool-data-embedded-in-the-bitcoin-blockchain/ascii-art" rel="nofollow noreferrer">this blog post</a>.</p>
<p><strong>Manually obtaining and interpreting data from an online blockchain tracker API</strong></p>
<p>Here's are links that still works as of 2021 and have full disassembled data:</p>
<ul>
<li><a href="https://blockchain.info/tx/930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72?format=json" rel="nofollow noreferrer">https://blockchain.info/tx/930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72?format=json</a></li>
<li><a href="https://blockchain.info/block-height/138725?format=json" rel="nofollow noreferrer">https://blockchain.info/block-height/138725?format=json</a></li>
</ul>
<p>based on <a href="https://bitcoin.stackexchange.com/a/3384/21282">this other answer</a>.</p>
<p>The key contents are the outputs of the transaction:</p>
<pre><code>   &quot;out&quot;:[
      {
         &quot;spent&quot;:false,
         &quot;tx_index&quot;:0,
         &quot;type&quot;:0,
         &quot;addr&quot;:&quot;1CqKQ2EqUscMkeYRFMmgepNGtfKynXzKW7&quot;,
         &quot;value&quot;:1000000,
         &quot;n&quot;:0,
         &quot;script&quot;:&quot;76a91481ccb4ee682bc1da3bda70176b7ccc616a6ba9da88ac&quot;
      },
      {
         &quot;spent&quot;:false,
         &quot;tx_index&quot;:0,
         &quot;type&quot;:0,
         &quot;addr&quot;:&quot;157sXa7duStAvq3dPLWe7J449sgh47eHzw&quot;,
         &quot;value&quot;:1000000,
         &quot;n&quot;:1,
         &quot;script&quot;:&quot;76a9142d2d2d424547494e20545249425554452d2d2d2088ac&quot;
      },
...
      {
         &quot;spent&quot;:false,
         &quot;tx_index&quot;:0,
         &quot;type&quot;:0,
         &quot;addr&quot;:&quot;157sXYpjvAyEJ6TdVFaVzmoETAQnHB6FGU&quot;,
         &quot;value&quot;:1000000,
         &quot;n&quot;:77,
         &quot;script&quot;:&quot;76a9142d2d2d2d454e4420545249425554452d2d2d2d2088ac&quot;
      }
</code></pre>
<p>where:</p>
<pre><code>echo 76a9142d2d2d424547494e20545249425554452d2d2d2088ac | xxd -r -p
echo 76a9142d2d2d2d454e4420545249425554452d2d2d2d2088ac | xxd -r -p
</code></pre>
<p>give:</p>
<pre><code>v---BEGIN TRIBUTE---
v----END TRIBUTE----
</code></pre>
<p>which clarifies how the message is encoded in the <code>script</code> entries of each output. They are not therefore actually contiguous in the stream.</p>
<p>This is why if you download the blockchain and do:</p>
<pre><code>strings -n20 .bitcoin/blocks/blk00003.dat
</code></pre>
<p>it works really well to see the data, as the newlines come from <code>strings</code> itself. The <code>strings</code> output can also be seen at: <a href="https://bitcoinstrings.com/blk00003.txt" rel="nofollow noreferrer">https://bitcoinstrings.com/blk00003.txt</a></p>
<p><strong>Announcement speech by Dan Kaminsky at BlackHat 2011</strong></p>
<p>Doesn't give the tx, but people who come here might want to see it: <a href="https://www.youtube.com/watch?v=hLIYq3ePaX4&amp;t=502s" rel="nofollow noreferrer">https://www.youtube.com/watch?v=hLIYq3ePaX4&amp;t=502s</a></p>

CC BY-SA 4.0
2021-01-09T17:02:45.857Z
2022-02-03T10:44:26.117Z
2022-02-03T10:44:26.117Z
Ciro Santilli OurBigBook.com
<p>Block <a href="https://www.blockchain.com/btc/block/138725" rel="nofollow noreferrer">138725</a></p>
<p>Transaction <a href="https://www.blockchain.com/btc/tx/930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72" rel="nofollow noreferrer">930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72</a></p>

CC BY-SA 4.0
2012-04-07T08:31:08.117Z
2021-01-09T17:12:20.037Z
2021-01-09T17:12:20.037Z
Chris Moore
<p>It has been mentioned a couple times here and there that <a href="http://en.wikipedia.org/wiki/Len_Sassaman" rel="noreferrer">Len Sassaman</a> was memorialised somewhere in the Block Chain. I was able to find a dump of of the <a href="http://pastebin.com/raw.php?i=BUB3dygQ" rel="noreferrer">tribute to him</a>, but I can't seem to find where in the Chain did this tribute come from.</p>

<p>What are the Blocks/Transactions that contain the tribute to Len Sassaman?</p>

CC BY-SA 4.0
2022-06-24T19:24:49.877Z
@matonis doesn't that show he was skeptical it could remain anonymous, not of the entire concept?
Gaia
CC BY-SA 3.0
2012-04-06T17:52:23.390Z
Not sure about the block chain. Len was brilliant but he was still a bitcoin skeptic. I had this conversation with him about one week before his death. http://themonetaryfuture.blogspot.com.es/2011/07/len-sassaman-on-bitcoin.html
matonis
CC BY-SA 3.0
2012-04-06T22:50:17.260Z
Related notes from Dan Kaminsky, the one who created the tribute: https://bitcointalk.org/index.php?topic=34458.0  and another thread discussing it: https://bitcointalk.org/index.php?topic=33618.0
Stephen Gornick
<transactions><script><encoding><message>
In which Block was Len Sassaman memorialised?
ThePiachu
# In which Block was Len Sassaman memorialised?

(Asked by: username_0 on 2012-04-06)

It has been mentioned a couple times here and there that [Len Sassaman](http://en.wikipedia.org/wiki/Len_Sassaman) was memorialised somewhere in the Block Chain. I was able to find a dump of of the [tribute to him](http://pastebin.com/raw.php?i=BUB3dygQ), but I can't seem to find where in the Chain did this tribute come from.

What are the Blocks/Transactions that contain the tribute to Len Sassaman?

**Tags:** transactions, script, encoding, message

> **Comments:**
> **username_2**: Not sure about the block chain. Len was brilliant but he was still a bitcoin skeptic. I had this conversation with him about one week before his death. http://themonetaryfuture.blogspot.com.es/2011/07/len-sassaman-on-bitcoin.html  
> **username_3**: Related notes from Dan Kaminsky, the one who created the tribute: https://bitcointalk.org/index.php?topic=34458.0  and another thread discussing it: https://bitcointalk.org/index.php?topic=33618.0  
> **username_1**: @username_2 doesn't that show he was skeptical it could remain anonymous, not of the entire concept?  

---

## 3 answers

### Answer by username_5 on 2012-04-07. Score: 5 | Accepted answer

Block [138725](https://www.blockchain.com/btc/block/138725)

Transaction [930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72](https://www.blockchain.com/btc/tx/930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72)


---

### Answer by username_3 on 2012-04-06. Score: 2

[930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72](http://blockexplorer.com/tx/930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72)
as reported by forum user makomk [here](https://bitcointalk.org/index.php?topic=33618.msg420597#msg420597).


---

### Answer by username_4 on 2021-01-09. Score: 2

**Find it yourself with my preprocessed ASCII strings data**

At <https://github.com/cirosantilli/bitcoin-strings-with-txids> I have uploaded a dump of all ASCII strings of length 20 or greater, including scripts to generate that data from a local copy of the blockchain by using <https://github.com/alecalve/python-bitcoin-blockchain-parser>

The main difference between my dump and <https://bitcoinstrings.com/blk00003.txt> is that since I parse the blockchain, I am dumping a bit more metadata, notably the transaction IDs.

So if you do:

```
git clone https://github.com/cirosantilli/bitcoin-strings-with-txids
cd bitcoin-strings-with-txids
git grep 'BEGIN TRIBUTE'

```

one of the very few hits will be:

```
data/out/0138.txt:2:---BEGIN TRIBUTE--- #./BitLen ...

```

and then when you open the corresponding file [data/out/0138.txt#L2](https://github.com/cirosantilli/bitcoin-strings-with-txids/blob/master/data/out/0138.txt#L2) you see:

```
tx 930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72
---BEGIN TRIBUTE--- #./BitLen ...

```

Unfortunately my dump does not do automatic newline splitting at the end of every ASCII payload, so this particular ASCII art does not show up correctly.

Before `OP_RETURN`, payloads were always put into a 20 bytes long address, and this particular ASCII art was intended to have automatic newlines.

However, this prevents ASCII art with lines longer than 20 bytes, with explicit `\n` added, and so I decided to not automatically add newlines as it allows seeing many more interesting ASCII arts correctly on average. I did an overview of the most interesting ASCII arts I've found on [this blog post](https://cirosantilli.com/cool-data-embedded-in-the-bitcoin-blockchain/ascii-art).

**Manually obtaining and interpreting data from an online blockchain tracker API**

Here's are links that still works as of 2021 and have full disassembled data:

* <https://blockchain.info/tx/930a2114cdaa86e1fac46d15c74e81c09eee1d4150ff9d48e76cb0697d8e1d72?format=json>
* <https://blockchain.info/block-height/138725?format=json>

based on [this other answer](https://bitcoin.stackexchange.com/a/3384/21282).

The key contents are the outputs of the transaction:

```
   "out":[
      {
         "spent":false,
         "tx_index":0,
         "type":0,
         "addr":"1CqKQ2EqUscMkeYRFMmgepNGtfKynXzKW7",
         "value":1000000,
         "n":0,
         "script":"76a91481ccb4ee682bc1da3bda70176b7ccc616a6ba9da88ac"
      },
      {
         "spent":false,
         "tx_index":0,
         "type":0,
         "addr":"157sXa7duStAvq3dPLWe7J449sgh47eHzw",
         "value":1000000,
         "n":1,
         "script":"76a9142d2d2d424547494e20545249425554452d2d2d2088ac"
      },
...
      {
         "spent":false,
         "tx_index":0,
         "type":0,
         "addr":"157sXYpjvAyEJ6TdVFaVzmoETAQnHB6FGU",
         "value":1000000,
         "n":77,
         "script":"76a9142d2d2d2d454e4420545249425554452d2d2d2d2088ac"
      }

```

where:

```
echo 76a9142d2d2d424547494e20545249425554452d2d2d2088ac | xxd -r -p
echo 76a9142d2d2d2d454e4420545249425554452d2d2d2d2088ac | xxd -r -p

```

give:

```
v---BEGIN TRIBUTE---
v----END TRIBUTE----

```

which clarifies how the message is encoded in the `script` entries of each output. They are not therefore actually contiguous in the stream.

This is why if you download the blockchain and do:

```
strings -n20 .bitcoin/blocks/blk00003.dat

```

it works really well to see the data, as the newlines come from `strings` itself. The `strings` output can also be seen at: <https://bitcoinstrings.com/blk00003.txt>

**Announcement speech by Dan Kaminsky at BlackHat 2011**

Doesn't give the tx, but people who come here might want to see it: <https://www.youtube.com/watch?v=hLIYq3ePaX4&t=502s>


---

