From: Wladimir <laanwj@gmail.com>
To: Flavien Charlon <flavien.charlon@coinprism.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] About watch-only addresses
Date: Sat, 18 Oct 2014 12:13:28 +0200 [thread overview]
Message-ID: <CA+s+GJBsgKrZgtOTHFqpbGPp8YfbYdRE885emiqMApGfUGX0WA@mail.gmail.com> (raw)
In-Reply-To: <CABbpET8x__gvSLhVp54GcC5FFVs1buE_-7D4xiqpX0ncB2GPJQ@mail.gmail.com>
On Fri, Oct 17, 2014 at 10:36 PM, Flavien Charlon
<flavien.charlon@coinprism.com> wrote:
> Hi,
>
> What is the status of watch-only addresses in Bitcoin Core? Is it merged in
> master and usable? Is there documentation on how to add a watch-only address
> through RPC.
It has been merged. There is the "importaddress" RPC call, which works
the same as "importprivkey" except that you a pass it an address.
> Also, I believe that is going towards the 0.10 release, is there a rough ETA
> for a release candidate?
Yes - aim is in a few months, probably by the end of the year.
AFAIK there are no nightly builds at this moment. Warren Togami was
building them for a while (at http://nightly.bitcoin.it/) but he
stopped some time around June.
It's not recommended to use master without at least a little bit of
development/debugging experience of yourself (to trace down problems
when they appear), so it's best to build it yourself if you're going
to test day-to-day development versions.
Wladimir
next prev parent reply other threads:[~2014-10-18 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 20:36 [Bitcoin-development] About watch-only addresses Flavien Charlon
2014-10-18 9:44 ` Flavien Charlon
2014-10-18 10:13 ` Wladimir [this message]
2014-10-18 18:43 ` Felipe Micaroni Lalli
2014-10-20 10:56 ` Mike Hearn
2014-10-20 22:37 ` Warren Togami Jr.
2014-10-20 23:06 ` mbde
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=CA+s+GJBsgKrZgtOTHFqpbGPp8YfbYdRE885emiqMApGfUGX0WA@mail.gmail.com \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=flavien.charlon@coinprism.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