From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WzpMG-0007Yl-0J for bitcoin-development@lists.sourceforge.net; Wed, 25 Jun 2014 15:43:36 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.45 as permitted sender) client-ip=74.125.82.45; envelope-from=jgarzik@bitpay.com; helo=mail-wg0-f45.google.com; Received: from mail-wg0-f45.google.com ([74.125.82.45]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WzpME-0000bJ-6s for bitcoin-development@lists.sourceforge.net; Wed, 25 Jun 2014 15:43:35 +0000 Received: by mail-wg0-f45.google.com with SMTP id l18so2240237wgh.4 for ; Wed, 25 Jun 2014 08:43:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=LcbD5QG3Oru6R6Vqqv+uLClyghSsYThiJRWqmN/2ANQ=; b=ETR1utQ8jWamWqnOemJUb3PfuUWKyko9HbuST8zL+pUVYv1Q/ulj7qZaXOBFsWO4kn r8awacX3eaWtlWDb0TmU6bd/aMcpqNNhPTI+w/G0mbiJi6xolE5ZAKgvvGp9esU3n+2H P5zZtGaI51k3PUTZjGP6dYKyyKo307G814cgRmEUx+KVqA0myRbNGIk+fRBTCTI660Uw Ee6OJ3XL1zQ1jwloVp8Wv4QeR1P0mpDbl/qz8sfom+hhzZICh9HWVJcg1ttfm8d5x3R6 xefRmmY2cBtMwZrxzgUhkpI/UxgTSkXM5UyqRei7GnMFm/UGuQmrIne658nkgLisIzbO 2O/A== X-Gm-Message-State: ALoCoQnVvX5m7E1y8Vc9ZSZj/u5CfVnst7lqIR0WKzbK433xIYtHbunvXisIY3jek+W+vHhLfvQ2 X-Received: by 10.180.72.201 with SMTP id f9mr32740880wiv.41.1403711006200; Wed, 25 Jun 2014 08:43:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.195.12.3 with HTTP; Wed, 25 Jun 2014 08:43:05 -0700 (PDT) From: Jeff Garzik Date: Wed, 25 Jun 2014 11:43:05 -0400 Message-ID: To: Bitcoin Dev Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WzpME-0000bJ-6s Subject: [Bitcoin-development] Wallet nLockTime best practices X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2014 15:43:36 -0000 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/