From: Peter Todd <pete@petertodd•org>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoinj 0.11 released, with p2sh, bip39 and payment protocol support
Date: Tue, 4 Feb 2014 08:17:23 -0500 [thread overview]
Message-ID: <20140204131723.GA10309@savin> (raw)
In-Reply-To: <CANEZrP2NyvRKwSEZORjAOq6G7UqLv=F3FjxmGNTPMT10yWGxzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2625 bytes --]
On Tue, Feb 04, 2014 at 02:13:12PM +0100, Mike Hearn wrote:
> Hah, good point. If nobody completes the homework, I'll post a fixed
> version tomorrow :)
Heh, here's another 25mBTC while we're at it:
https://github.com/opentimestamps/opentimestamps-client/commit/288f3c17626974de7eaef4f1c9b5cd93eecf40f6
Why is that a bad idea?
Bonus question: What was I smoking? (hint: where do I live?)
> On Tue, Feb 4, 2014 at 2:03 PM, Peter Todd <pete@petertodd•org> wrote:
>
> > On Tue, Feb 04, 2014 at 01:01:12PM +0100, Mike Hearn wrote:
> > > Hello,
> > >
> > > I'm pleased to announce the release of bitcoinj 0.11, a library for
> > writing Bitcoin applications that run on the JVM. BitcoinJ is widely used
> > across the Bitcoin community; some users include Bitcoin Wallet for
> > Android, MultiBit, Hive, blockchain.info, the biteasy.com block explorer
> > (written in Lisp!), Circle, Neo/Bee (Cypriot payment network), bitpos.me,
> > Bitcoin Touch, BlueMatt's relay network and DNS crawler, academic advanced
> > contracts research and more.
> > >
> > > The release-0.11 git tag is signed by Andreas Schildbach's GPG key. The
> > commit hash is 410d4547a7dd. This paragraph is signed by the same Bitcoin
> > key as with previous releases (check their release announcements to
> > establish continuity). Additionally, this email is signed using DKIM and
> > for the first time, a key that was ID verified by the Swiss government.
> > >
> > > Key: 16vSNFP5Acsa6RBbjEA7QYCCRDRGXRFH4m
> > > Signature for last paragraph:
> > H3DvWBqFHPxKW/cdYUdZ6OHjbq6ZtC5PHK4ebpeiE+FqTHyRLJ58BItbC0R2vo77h+DthpQigdEZ0V8ivSM7VIg=
> >
> > The above makes for a great homework problem for budding cryptographers:
> > Why did the three forms of signature, DKIM, long-lived bitcoin address,
> > and Official Swiss Government Identity fail to let you actually verify
> > you have the right code? (but make for great security theater)
> >
> > Bonus question: Who has the smallest work-factor for such an attack?
> >
> > Two rewards of 25mBTC for correct responses to each question from a
> > crypto newbie.
> >
> > > Thanks to Mike Belshe, the wallet can now send to P2SH addresses.
> >
> > Thanks
> >
> > > Generated signatures now use canonical S values. This will aid a future
> > hard-forking rule change which bans malleable signatures.
> >
> > Soft-forking rule change.
> >
> > --
> > 'peter'[:-1]@petertodd.org
> > 000000000000000075829f6169c79d7d5aaa20bfa8da6e9edb2393c4f8662ba0
> >
--
'peter'[:-1]@petertodd.org
000000000000000075829f6169c79d7d5aaa20bfa8da6e9edb2393c4f8662ba0
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 685 bytes --]
next prev parent reply other threads:[~2014-02-04 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 12:01 Mike Hearn
2014-02-04 13:03 ` Peter Todd
2014-02-04 13:13 ` Mike Hearn
2014-02-04 13:17 ` Peter Todd [this message]
2014-02-04 14:43 ` Jeff Garzik
2014-02-04 14:46 ` Peter Todd
2014-02-04 15:17 ` Natanael
2014-02-04 16:04 ` Peter Todd
2014-02-05 7:57 ` Jeremy Spilman
2014-02-05 15:09 ` Brooks Boyd
2014-02-07 9:21 ` Peter Todd
2014-02-07 10:48 ` Mike Hearn
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=20140204131723.GA10309@savin \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)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