From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 135D73C8 for ; Thu, 30 Jul 2015 23:01:41 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7FD90E0 for ; Thu, 30 Jul 2015 23:01:40 +0000 (UTC) Received: by wicgb10 with SMTP id gb10so10652880wic.1 for ; Thu, 30 Jul 2015 16:01:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7wYxRPPIw6eFGmBWTYDq51IY0w5vh49zCOqpJEzSidE=; b=pe/4+2EZFS8x8JbWfV2mWdwLWttMkrYaNNOHAkX0B08fi1nsJDGtmw9KAeGPRNW3Dd +cDm+9bpjyqkILK/UmVjc3Sy+uKljT0DGcLZfNmauO1CX+FDOCiDWd1GyuxlfKmgTUxS U25nxv0SuVFxnJo1rwNseDDJk+vOOVrESlr2m2qrMmzYFCSm0kvUcbBAMfMG+OP8/rk6 M5SY8/6pJZdhGV/mZ0OrsIpY10MVelW2cUvbnBkk44+HX6VqKVItlWl1YuDDTnPyDD42 q+YXgnMNSm2AmMWscVUe4Pq+1XdZeJ5jLMsMLGw8yAFXi/PQPdV1RQLhbq3nq1znEAPg y0BA== X-Received: by 10.180.39.163 with SMTP id q3mr267888wik.82.1438297299135; Thu, 30 Jul 2015 16:01:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.32.132 with HTTP; Thu, 30 Jul 2015 16:00:59 -0700 (PDT) In-Reply-To: <6DA19C0F-EFBD-4C38-B2FD-1DD0A40F11D4@coincadence.com> References: <6DA19C0F-EFBD-4C38-B2FD-1DD0A40F11D4@coincadence.com> From: Micha Bailey Date: Fri, 31 Jul 2015 02:00:59 +0300 Message-ID: To: Ian Treibick Content-Type: multipart/alternative; boundary=001a11c3544a98b264051c1faffc X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] LockUnspent not working, bug? X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jul 2015 23:01:41 -0000 --001a11c3544a98b264051c1faffc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable RTFM: `help lockunspent`. The boolean parameter is whether or not the UTXO should be available. On Thu, Jul 30, 2015 at 11:43 PM, Ian Treibick via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > My first post to the list, not sure this is the right place, let me know > if it is better to open an issue on GitHub. > > This is occurring on OS X with Satoshi 0.11.0, the TXID and vout belong t= o > the wallet: > > command: lockunspent true "[ { \"txid\": > \"fd697746c67f68a206bb7377fd40f35d146cc5821883e4c4b6cbf82b48e62a13\", > \"vout\": 1 } ]" > output: true > command: listlockunspent > Output:=EF=BF=BC > [ > ] > > Additionally after locking the TX with lockunspent I am able to spend it > from the wallet. > > Cheers, > > Ian > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > > --001a11c3544a98b264051c1faffc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
RTFM: `help lockunspent`. The boolean parameter is whether= or not the UTXO should be available.

--001a11c3544a98b264051c1faffc--