Git commit allegedly from Satoshi embedded inside a Bitcoin transaction
blockchain.info
blockchain.info
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
--
1.7.9.4The line breaks are in the page source, but they've been stripped because of HTML white-space collapsing.
the output of the second transaction is: OP_DUP OP_HASH160 d9fc6bc120342fc43b2296876562e1d4c6536fda OP_EQUALVERIFY OP_CHECKSIG
They are accepted and valid in blocks though. So any miner can include them in their blocks. What Eligius, and some other pools do, is they allow accepting the transaction directly. So you connect your node to it directly and send the transaction as normal. It won't be relayed to other peers as they reject it. But those running a modified client will and can include it in a block.
Doing transactions on behalf of other users' accounts is not possible, as accounts are secured using public key cryptography (via elliptic curves) [2]. Only the creator of an account has the private key that allows her to sign valid transactions.
Nothing hinders the entity controlling the block chain to include invalid transactions that aren't properly signed, however all the other bitcoin clients in the network still verify the blockchain when downloaded, so those invalid transactions won't have a visible effect on users of the Bitcoin network.
[1] http://mineforeman.com/2012/12/10/want-to-destroy-bitcoin-i-...
[2] http://blog.ezyang.com/2011/06/the-cryptography-of-bitcoin/
Instead, as PG and others have hypothesized, the sovereign behind btc will have achieved a new worldwide currency system, that naturally, they will participate in, perhaps from a somewhat advantageous position (premined blocks etc).
The last 3 sentences of your post are a non-sequitur imho.
Bitcoin, on the other hand, has been adopted in tandem with other currencies worldwide and has made international news. It may never succeed in some of its proponents' dreams of replacing fiat currency, but it's certainly visible enough to act as a global alternative currency during recessions.
http://pgp.circl.lu/pks/lookup?op=vindex&search=0x5EC948A1&f...
I assume none of the key verified his identity before signing it ;-)
Hope this helps.
This transaction is embedding a message inside of a non-standard output script, which shouldn't be possible.
It is restricted by the standard Bitcoin client implementation. Neither the transaction scripting language[0] nor the transaction[1] restricts it, so you would need to do it yourself or write a custom client to embed a message.
http://garzikrants.blogspot.com/2013/04/on-bitcoin-data-spam...
Bitcoin is a really amazing piece of software and algorithm engineering. It is highly unlikely, although not impossible, that it was designed by a single individual. The scale, relatively bullet-proof crypto design (most systems are rigorously peer reviewed and still break), and the massive potential impact on global finance all point to a nation-state as the designer.
PG actually launched a thread with the same conclusion, and it seems eminently plausible to me.
As an example, JK Rowling released a book under a pseudonym. Very few people knew it was written by her, but one of those (a solicitor/lawyer) let slip to a friend, who then tweeted a tip to a journalist. It took a matter of weeks from publication for her to be outed. We are 4 years into bitcoin and there has not been anyything like this to suggest a large group worked on it.
If anything the lomger it goes the more likely it is that Satoshi Nakamoto was acting alone. Aditionally if there was a group of people then many of those would have had access to the numerous coins that were suposedly generated by SN during 2009. Surely some, one, any of those would have tried to access a portion of the coins to liquidate them.
Givent hat neither of these have happened it is more likely that a single individual was responsible and he/she is very strict with regard to their secuirty. i.e. they knwo that using any of those coins increases the chance that they will be tracked down. Whereas if it was a team then any one member may feel they could get away with it. Operational Security gets easier the fewer people that know about it.
the day before that leak you could have used exactly the same argument against the existence of a comprehensive NSA surveillance program ... someone would have leaked it already, right?
To actually see the message click the link "Show scripts & coinbase"
This is a non-standard transaction. This type of transaction burns bitcoins(bitcoins don't go anywhere.)
This transaction was first mined by the pool called Eligius. The Eligius pool allows non standard transactions if the transation is relayed to it directly.
The message is also not signed(PGP) correctly by Satoshi(Bitcoin creator).
1) Whoever did this has access to enough hashing power to mine their own non-standard transactions into blocks.
2) $0.43 is unusually high for a transaction fee. Perhaps this is high enough to incentivize miners to include the tx in a block.