From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XHcqj-0004vI-TE for bitcoin-development@lists.sourceforge.net; Wed, 13 Aug 2014 18:00:37 +0000 X-ACL-Warn: Received: from mail-qg0-f44.google.com ([209.85.192.44]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XHcqe-0006Mp-1X for bitcoin-development@lists.sourceforge.net; Wed, 13 Aug 2014 18:00:37 +0000 Received: by mail-qg0-f44.google.com with SMTP id e89so89592qgf.31 for ; Wed, 13 Aug 2014 11:00:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:subject:message-id:date:to :mime-version; bh=pcmH9auuOIiSNc2yX6YconaxrjGMbDzw21hObuSKs/Y=; b=cpAejT7+eRV0FmWDh3iASHqIw//MUQlk+NsyuuDj5hPhfx7xUf0lG4B9e9spq9pXXY cOJP4MtY8lYTXU0gVem5Q/k+JC6lUsGL3D4QClEpSW91zSV30MjDHwZYt8A7fn1ZAx/0 L8clK3Q4M/3/km2n8FiZXCrf/x63mZ0WS+45CxwO7FzsKKz89698O5bJRzhwCswf8/Fg sNCwwu6c3/D+laSE5v5nuj/ScK8aQKc7u4sgb8bfEyTZ8EfHZ0K4b8/4QWifweQub9wW nvB3aIY/58fsCE+F6B8VsQMkw/9vT57+NFkSkYGZtbg5dNyZVZhO9piX9WjneMvMppF1 34Dg== X-Gm-Message-State: ALoCoQlptxDKw6vQk00OeO6eVgn/UcTPkaWq+rGnZ6gWmZQYEcBlocQCVDPVZlE1pu1RZYPSlF62 X-Received: by 10.224.151.69 with SMTP id b5mr9528787qaw.37.1407952826343; Wed, 13 Aug 2014 11:00:26 -0700 (PDT) Received: from [192.168.2.25] (135-23-143-85.cpe.pppoe.ca. [135.23.143.85]) by mx.google.com with ESMTPSA id n46sm2771446qgd.49.2014.08.13.11.00.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Aug 2014 11:00:24 -0700 (PDT) From: Richard Moore Content-Type: multipart/alternative; boundary="Apple-Mail=_29D598FB-02C4-438A-9F92-3B2E0ADBFF59" Message-Id: Date: Wed, 13 Aug 2014 14:00:22 -0400 To: Bitcoin Dev Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-Spam-Score: 2.0 (++) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 SPF_PASS SPF: sender matches SPF record 1.1 TRACKER_ID BODY: Incorporates a tracking ID number 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XHcqe-0006Mp-1X Subject: [Bitcoin-development] Another weird transaction question... X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 18:00:38 -0000 --Apple-Mail=_29D598FB-02C4-438A-9F92-3B2E0ADBFF59 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 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 .=B7=B4=AF`=B7.=B8=B8.=B7=B4=AF`=B7.=B8=B8.=B7=B4=AF`=B7.=B8=B8.=B7=B4=AF`= =B7.=B8=B8.=B7=B4=AF`=B7.=B8><(((=BA> Richard Moore ~ Founder Genetic Mistakes Software inc. phone: (778) 882-6125 email: ricmoo@geneticmistakes.com www: http://GeneticMistakes.com --Apple-Mail=_29D598FB-02C4-438A-9F92-3B2E0ADBFF59 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
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.in= fo/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


.=B7=B4=AF`=B7.=B8=B8.=B7=B4=AF`=B7.=B8=B8.=B7=B4=AF`=B7.=B8=B8.=B7=B4= =AF`=B7.=B8=B8.=B7=B4=AF`=B7.=B8><(((=BA>

Richard Moore = ~ Founder
Genetic Mistakes Software inc.
phone: (778) = 882-6125
email: ricmoo@geneticmistakes.com<= br>www: http://GeneticMistakes.com=

= --Apple-Mail=_29D598FB-02C4-438A-9F92-3B2E0ADBFF59--