public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Micha Bailey <michabailey@gmail.com>
To: Ian Treibick <ian@coincadence.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] LockUnspent not working, bug?
Date: Fri, 31 Jul 2015 02:00:59 +0300	[thread overview]
Message-ID: <CAAmoQf2mZrytwT7ptpSG-vK-yqEXrZGUb6TRrTYPADmk5Q9nGg@mail.gmail.com> (raw)
In-Reply-To: <6DA19C0F-EFBD-4C38-B2FD-1DD0A40F11D4@coincadence.com>

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

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 to
> the wallet:
>
> command: lockunspent true "[ { \"txid\":
> \"fd697746c67f68a206bb7377fd40f35d146cc5821883e4c4b6cbf82b48e62a13\",
> \"vout\": 1 } ]"
> output: true
> command: listlockunspent
> Output:
> [
> ]
>
> 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
>
>

[-- Attachment #2: Type: text/html, Size: 1503 bytes --]

      reply	other threads:[~2015-07-30 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3587.1438280185.1480.bitcoin-dev@lists.linuxfoundation.org>
2015-07-30 20:43 ` [bitcoin-dev] LockUnspent not working, bug? Ian Treibick
2015-07-30 23:00   ` Micha Bailey [this message]

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=CAAmoQf2mZrytwT7ptpSG-vK-yqEXrZGUb6TRrTYPADmk5Q9nGg@mail.gmail.com \
    --to=michabailey@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=ian@coincadence.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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