Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <gronager@mac.com>) id 1Tj4fC-0005mH-CQ for bitcoin-development@lists.sourceforge.net; Thu, 13 Dec 2012 09:01:06 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of mac.com designates 17.172.81.2 as permitted sender) client-ip=17.172.81.2; envelope-from=gronager@mac.com; helo=st11p00mm-asmtp003.mac.com; Received: from st11p00mm-asmtpout003.mac.com ([17.172.81.2] helo=st11p00mm-asmtp003.mac.com) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Tj4fA-0005oI-22 for bitcoin-development@lists.sourceforge.net; Thu, 13 Dec 2012 09:01:06 +0000 MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Received: from [109.105.106.229] (unknown [109.105.106.229]) by st11p00mm-asmtp003.mac.com (Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPSA id <0MEY002GIP1KPG00@st11p00mm-asmtp003.mac.com> for bitcoin-development@lists.sourceforge.net; Thu, 13 Dec 2012 09:00:58 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327,1.0.431,0.0.0000 definitions=2012-12-13_04:2012-12-13, 2012-12-13, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1212130016 From: gronager@mac.com In-reply-to: <A08D9088-82EE-4F67-B260-8AF5CB1D15A6@gmail.com> Date: Thu, 13 Dec 2012 10:00:55 +0100 Content-transfer-encoding: quoted-printable Message-id: <833554E8-0732-46D2-88BE-D8BA98325C4C@mac.com> References: <A08D9088-82EE-4F67-B260-8AF5CB1D15A6@gmail.com> To: Eric Lombrozo <elombrozo@gmail.com> X-Mailer: Apple Mail (2.1499) X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gronager[at]mac.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Tj4fA-0005oI-22 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Zero-length scripts X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Thu, 13 Dec 2012 09:01:06 -0000 Normally I would consider it an error of the parsing script of = blockchain (seen that before), however, this seems genuine enough. the second transaction is the most amusing - it has an output script = which is: OP_HASH256 = 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f = OP_EQUAL The hash is the most famous bitcoin hash... - so if you can come up with = something that, when hashed with sha256 yields the genesisblock hash you = can claim one BTC ;) It is actually very easy to do (!), however, it is a game only for = miners, as non_standard transactions are not relayed between standard = clients. So now a miner can have a go creating a transaction redeeming = this 1BTC. Perhaps, Eligius creating that block, might be playing a little = christmas game :) Cheers, Michael On 12/12/2012, at 23:09, Eric Lombrozo <elombrozo@gmail.com> wrote: > I've noticed a few transactions that have zero-length input and/or = output scripts. There's a couple examples in block = 0000000000000159a27442ee8b7f9ffad0cd799b003eafe007de9fbb47bd6ce7: >=20 > Txs: cdb553214a51ef8d4393b96a185ebbbc2c84b7014e9497fea8aec1ff990dae35, = af32bb06f12f2ae5fdb7face7cd272be67c923e86b7a66a76ded02d954c2f94d >=20 >=20 > Is there ever a legitimate reason to create a transaction with a = zero-length script? Should the protocol even allow it? >=20 > -Eric Lombrozo >=20 > = --------------------------------------------------------------------------= ---- > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add = services > Discover what IT Professionals Know. Rescue delivers > = http://p.sf.net/sfu/logmein_12329d2d______________________________________= _________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development Michael Gr=F8nager Jens Juels Gade 33 2100 Copenhagen E DENMARK Mobile: +45 31 45 14 01 E-mail: gronager@mac.com