From: Aaron Voisine <voisine@gmail•com>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Wallet nLockTime best practices
Date: Fri, 6 Jun 2014 13:17:49 -0700 [thread overview]
Message-ID: <CACq0ZD4WSRK=sUq9yCUQX3jpH39m5dzxGAxxeXDFHXTrc0BmUw@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0PQkNN6F=dEH0F8Gw59jYfU2f5ZmY=2tooJME9_t2kHHA@mail.gmail.com>
I'll implement it in breadwallet (oss SPV wallet, hopefully about to
be in the app store) if other wallet authors are planning to.
Aaron
https://github.com/voisine/breadwallet
There's no trick to being a humorist when you have the whole
government working for you -- Will Rodgers
On Fri, Jun 6, 2014 at 12:00 PM, Jeff Garzik <jgarzik@bitpay•com> wrote:
> We are considering pulling in https://github.com/bitcoin/bitcoin/pull/2340
> "Discourage fee sniping with nLockTime"
>
> Comments from other wallet implementors in particular are welcomed.
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2014-06-06 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 19:00 Jeff Garzik
2014-06-06 20:17 ` Aaron Voisine [this message]
2014-06-25 15:43 Jeff Garzik
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='CACq0ZD4WSRK=sUq9yCUQX3jpH39m5dzxGAxxeXDFHXTrc0BmUw@mail.gmail.com' \
--to=voisine@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(echo .)com \
/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