From: "Warren Togami Jr." <wtogami@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] About watch-only addresses
Date: Mon, 20 Oct 2014 12:37:40 -1000 [thread overview]
Message-ID: <CAEz79PrNk2fSOxrA4yQMiRU3yNF1eQMEQqaraoLs65T7KWK+vw@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJBsgKrZgtOTHFqpbGPp8YfbYdRE885emiqMApGfUGX0WA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]
https://bitcointalk.org/index.php?topic=320695
I made a branch of Bitcoin 0.9.3 plus backports including watch-only and a
huge pile of patches cleaning it up from the master branch. It seems to
work fine although it is not heavily tested. I suppose if you use ONLY for
watch-only it can't be harmful? Dunno.
Warren
On Sat, Oct 18, 2014 at 12:13 AM, Wladimir <laanwj@gmail•com> wrote:
> 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
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2893 bytes --]
next prev parent reply other threads:[~2014-10-20 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 20:36 Flavien Charlon
2014-10-18 9:44 ` Flavien Charlon
2014-10-18 10:13 ` Wladimir
2014-10-18 18:43 ` Felipe Micaroni Lalli
2014-10-20 10:56 ` Mike Hearn
2014-10-20 22:37 ` Warren Togami Jr. [this message]
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=CAEz79PrNk2fSOxrA4yQMiRU3yNF1eQMEQqaraoLs65T7KWK+vw@mail.gmail.com \
--to=wtogami@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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