From: Jeff Garzik <jgarzik@bitpay•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Wallet nLockTime best practices
Date: Wed, 25 Jun 2014 11:43:05 -0400 [thread overview]
Message-ID: <CAJHLa0Md-fnYFHqVhPGizdofm-8Ly6aZxN+u3EVkyNJ4B5BWeg@mail.gmail.com> (raw)
I'm inclined to merge https://github.com/bitcoin/bitcoin/pull/2340
which sets nLockTime on wallet-created transactions by default. I
think this is good practice for wallets, long term.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next reply other threads:[~2014-06-25 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 15:43 Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-06 19:00 Jeff Garzik
2014-06-06 20:17 ` Aaron Voisine
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=CAJHLa0Md-fnYFHqVhPGizdofm-8Ly6aZxN+u3EVkyNJ4B5BWeg@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--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