From: "Brautigam Róbert" <robert.brautigam@netmind•hu>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] ECC Signature Issue
Date: Sun, 22 Jan 2012 14:18:35 +0100 [thread overview]
Message-ID: <4F1C0CAB.4000905@netmind.hu> (raw)
Hi all,
I'm working on a from scratch Java implementation. So far I got a
modularized, unit tested implementation of the core modules (api, keys,
blocks, chain, scripts, network protocol).
My dummy client however gets stuck on Block 140493, specifically at
transaction hash:
70f7c15c6f62139cc41afa858894650344eda9975b46656d893ee59df8914a3d
It seems the (signature) verification fails for this specific
transaction (for the 1 input in it), which is rather odd since
verification was successful for all the preceding blocks and inputs.
I double checked that the official (C++) client is indeed successful
here. Oddly enough the bitcoinj implementation also seems to fail to
verify this transaction, which seems to point in the direction of
BouncyCastle (which we both use).
My question is, did anybody hit this issue before? If not, can someone
doublecheck maybe that I'm not missing something trivial?
The data that should be signed (the signature hash):
b45c680f32f9364f5255cc15ef7cad879dbde9062d7fb8db0fe56e245823a78f
The signature (with '01' at the end for SIGHASH_ALL, remove this before
you pass it to verification):
304402206b5c3b1c86748dcf328b9f3a65e10085afcf5d1af5b40970d8ce3a9355e06b5b0220cdbdc23e6d3618e47056fccc60c5f73d1a542186705197e5791e97f0e6582a3201
The public key:
04f25ec495fa21ad14d69f45bf277129488cfb1a339aba1fed3c5099bb6d8e9716491a14050fbc0b2fed2963dc1e56264b3adf52a81b953222a2180d48b54d1e18
As said, this seems to work with openssl, but seems to fail with
bouncycastle for some reason (version 140).
Thanks,
Robert.
next reply other threads:[~2012-01-22 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 13:18 Brautigam Róbert [this message]
2012-01-23 17:50 ` Mike Hearn
[not found] <4F1DBD07.3050904@netmind.hu>
2012-01-24 17:33 ` Brautigam Róbert
2012-01-27 18:19 ` Brautigam Róbert
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=4F1C0CAB.4000905@netmind.hu \
--to=robert.brautigam@netmind$(echo .)hu \
--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