Bitcoin Graffiti work in progress
← Timeline text · 2013
From a3a61fef43309b9fb23225df7910b03afc5465b9 Mon Sep 17 00:00:00 2001
From: Satoshi Nakamoto <satoshin@gmx.com>
Date: Mon, 12 Aug 2013 02:28:02 -0200
Subject: [PATCH] Remove (SINGLE|DOUBLE)BYTE
I removed this from Bitcoin in f1e1fb4bdef878c8fc1564fa418d44e7541a7e83
in Sept 7 2010, almost three years ago. Be warned that I have not
actually tested this patch.
backends/bitcoind/deserialize.py |    8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/backends/bitcoind/deserialize.py b/backends/bitcoind/deserialize.py
index 6620583..89b9b1b 100644
--- a/backends/bitcoind/deserialize.py
+++ b/backends/bitcoind/deserialize.py
@@ -280,10 +280,8 @@ opcodes = Enumeration("Opcodes", [
"OP_WITHIN", "OP_RIPEMD160", "OP_SHA1", "OP_SHA256", "OP_HASH160",
"OP_HASH256", "OP_CODESEPARATOR", "OP_CHECKSIG", "OP_CHECKSIGVERIFY", "OP_CHECKMULTISIG",
"OP_CHECKMULTISIGVERIFY",
-    ("OP_SINGLEBYTE_END", 0xF0),
-    ("OP_DOUBLEBYTE_BEGIN", 0xF000),
"OP_PUBKEY", "OP_PUBKEYHASH",
-    ("OP_INVALIDOPCODE", 0xFFFF),
+    ("OP_INVALIDOPCODE", 0xFF),
@@ -293,10 +291,6 @@ def script_GetOp(bytes):
vch = None
opcode = ord(bytes[i])
i += 1
-        if opcode >= opcodes.OP_SINGLEBYTE_END and i < len(bytes):
-            opcode <<= 8
-            opcode |= ord(bytes[i])
-            i += 1
if opcode <= opcodes.OP_PUSHDATA4:
nSize = opcode
Open the raw reconstruction ↗
text unknown ✓ Verified on-chain

Satoshi 'email patch' (git diff)

Written to the chain on 12 Aug 2013, block 251,718.

Block
251,718
Written
12 Aug 2013
Size
1,355 B
Format
CODE
Transactions
1

About this artifact

A git diff distributed as an on-chain message rather than a mailing-list post. Early Bitcoin development happened over email, and this preserves a patch in the one place no list archive can lose it.

How it was stored

Some artifacts are visible or strongly evidenced, but the exact storage recipe is not fully understood yet. The bytes may appear in a recognizable place, or an external index may identify the object, while the original uploader’s ordering, compression, or framing convention remains unclear.

More about unknown
Proof · 1 transaction

Verified against the chain

Every byte shown here was read from these transactions. Open one in a block explorer to check it yourself.