MIME-Version: 1.0
In-Reply-To: <CABsx9T1v9Rfm_d7DcfbkkHEC96CwTNNp4_E1G97UBXqVHjVyOw@mail.gmail.com>
References: <CABsx9T1v9Rfm_d7DcfbkkHEC96CwTNNp4_E1G97UBXqVHjVyOw@mail.gmail.com>
Date: Wed, 3 Oct 2012 15:53:41 -0400
Message-ID: <CA+8xBpeRsOa_7rLfziyd7Gd79o9d5QPyc1-cWwZ36f8HNDjKdw@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.7.1 release
Precedence: list

On Wed, Oct 3, 2012 at 1:49 PM, Gavin Andresen <gavinandresen@gmail.com> wrote:
> "Add -reindex, to perform in-place reindexing of blockchain data
> files" : https://github.com/bitcoin/bitcoin/pull/1870

Agree, though needs testing

> "P2P: Do not request blocks from peers with fewer blocks than us" :
> https://github.com/bitcoin/bitcoin/pull/1834

Agree

> "Add new RPC "lockunspent", to prevent spending of selected outputs" :
> https://github.com/bitcoin/bitcoin/pull/1861

Agree, though sipa raised a valid issue.  lockunspent, like the
existing listunspent, is wallet based.

As raw transactions might spend outputs _not_ in the wallet,
lockunspent would miss those.

I think this is OK, because listunspent is already wallet-based, but
it should be noted.

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com