From: Eric Lombrozo <elombrozo@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Zero-length scripts
Date: Wed, 12 Dec 2012 14:09:38 -0800 [thread overview]
Message-ID: <A08D9088-82EE-4F67-B260-8AF5CB1D15A6@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
I've noticed a few transactions that have zero-length input and/or output scripts. There's a couple examples in block 0000000000000159a27442ee8b7f9ffad0cd799b003eafe007de9fbb47bd6ce7:
Txs: cdb553214a51ef8d4393b96a185ebbbc2c84b7014e9497fea8aec1ff990dae35, af32bb06f12f2ae5fdb7face7cd272be67c923e86b7a66a76ded02d954c2f94d
Is there ever a legitimate reason to create a transaction with a zero-length script? Should the protocol even allow it?
-Eric Lombrozo
[-- Attachment #2: Type: text/html, Size: 1336 bytes --]
next reply other threads:[~2012-12-12 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 22:09 Eric Lombrozo [this message]
2012-12-13 9:00 ` gronager
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A08D9088-82EE-4F67-B260-8AF5CB1D15A6@gmail.com \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox