From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Release priorities for v0.4?
Date: Mon, 13 Jun 2011 19:59:08 -0400 [thread overview]
Message-ID: <BANLkTikOEWZQur8EqumWH0jU=07-4vAFhg@mail.gmail.com> (raw)
With increased reports of stolen wallets, I humbly submit that wallet
crypto should be a top priority for the next version.
https://github.com/bitcoin/bitcoin/pull/232
Anyway... start pulling :)
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
next reply other threads:[~2011-06-13 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 23:59 Jeff Garzik [this message]
2011-06-15 14:27 ` [Bitcoin-development] Release priorities for v0.4? Mark Visser
2011-06-15 16:50 ` Jeff Garzik
2011-06-15 17:32 ` Theodore Witkamp
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='BANLkTikOEWZQur8EqumWH0jU=07-4vAFhg@mail.gmail.com' \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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