From: Mike Hearn <mike@plan99•net>
To: "Brautigam Róbert" <robert.brautigam@netmind•hu>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] ECC Signature Issue
Date: Mon, 23 Jan 2012 18:50:51 +0100 [thread overview]
Message-ID: <CANEZrP31-7gGDxze11QHBpt0sG3M5A6yviM++7RM63fRHzUwdA@mail.gmail.com> (raw)
In-Reply-To: <4F1C0CAB.4000905@netmind.hu>
> 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).
BitCoinJ does not verify signatures (it is an SPV implementation), so
I'm not sure what you mean by this. Are you using old code? There used
to be some stuff that checked signatures but it was removed some time
ago.
next prev parent reply other threads:[~2012-01-23 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 13:18 Brautigam Róbert
2012-01-23 17:50 ` Mike Hearn [this message]
[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=CANEZrP31-7gGDxze11QHBpt0sG3M5A6yviM++7RM63fRHzUwdA@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=robert.brautigam@netmind$(echo .)hu \
/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