From: Peter Todd <pete@petertodd.org>
To: Richard Moore <me@ricmoo.com>,
Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Another weird transaction question...
Date: Wed, 13 Aug 2014 11:10:32 -0700 [thread overview]
Message-ID: <d2f135de-16cc-41df-8ec5-de3089cf3741@email.android.com> (raw)
In-Reply-To: <A6E1C677-89CD-425D-BE36-A2A4C6837165@ricmoo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 13 August 2014 11:00:22 GMT-07:00, Richard Moore <me@ricmoo.com> wrote:
>Hey all,
>
>Sorry to keep bugging you all, as I slowly verify the blockchain one
>transaction after another with my own implementation, but I have found
>another transaction that is obviously correct (as it is verified by the
>legit client) that has me seeking clarification.
>
>This multisig output script:
>
>https://blockchain.info/tx-index/12809044/0 (txid:
>274f8be3b7b9b1a220285f5f71f61e2691dd04df9d69bb02a8b3b85f91fb1857)
>
>contains a public key:
>
>00f2b7816db49d55d24df7bdffdbc1e203b424e8cd39f5651ab938e5e4a193569e
>
>Are invalid public keys permitted and silently ignored? Or does the
>0x00 prefix have some interesting meaning?
Have you looked at the Bitcoin Core script test cases yet? You might be surprised at what is allowed. Equally, read the source code! In particular follow the block acceptance logic line by line from start to finish.
In any case, the Bitcoin protocol doesn't care whether or not a public key is valid.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQFQBAEBCAA6BQJT66oXMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhcgKCACT18WjN11SCuX5qyeq
D5zOtGBsAtPMWr8CJuds4gLIkRtxDxPy9cuIMzwLylaC0yvFSIrG6rAIcqqRpkEH
hcJj2IXyTRVr/mxg3qDzphYuwWQAgUzBgbhPsHtl8SvnbzJgEdXCsErGs3eW6JTR
I5OXeMVT8ZKQVJUKCNGdzlH4673Gh6fIzwW1cPLATt486ByCk5YRXC14IGasxnlg
6IWm4r/I6gOAB7FiPCHm60Q2DJOsX+VEFe3U28Zxlx06i0Ij9JYoKbTDu8e12bSB
YFUBwGCbwWr/Xcygg0nWyrEMVk5dcxk/30asF/dEczHRZo9DNUdKt4IAESd+GGC2
P9g4
=e0do
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-08-13 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 18:00 [Bitcoin-development] Another weird transaction question Richard Moore
2014-08-13 18:10 ` Peter Todd [this message]
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=d2f135de-16cc-41df-8ec5-de3089cf3741@email.android.com \
--to=pete@petertodd.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=me@ricmoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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