From: Richard Moore <me@ricmoo•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Another weird transaction question...
Date: Wed, 13 Aug 2014 14:00:22 -0400 [thread overview]
Message-ID: <A6E1C677-89CD-425D-BE36-A2A4C6837165@ricmoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
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?
Thanks again,
RicMoo
.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸><(((º>
Richard Moore ~ Founder
Genetic Mistakes Software inc.
phone: (778) 882-6125
email: ricmoo@geneticmistakes•com
www: http://GeneticMistakes.com
[-- Attachment #2: Type: text/html, Size: 1792 bytes --]
next reply other threads:[~2014-08-13 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 18:00 Richard Moore [this message]
2014-08-13 18:10 ` Peter Todd
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=A6E1C677-89CD-425D-BE36-A2A4C6837165@ricmoo.com \
--to=me@ricmoo$(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