1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1XfR0x-0006Bb-Dg
for bitcoin-development@lists.sourceforge.net;
Sat, 18 Oct 2014 10:13:35 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.178 as permitted sender)
client-ip=209.85.213.178; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f178.google.com;
Received: from mail-ig0-f178.google.com ([209.85.213.178])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XfR0w-0005Uj-9u
for bitcoin-development@lists.sourceforge.net;
Sat, 18 Oct 2014 10:13:35 +0000
Received: by mail-ig0-f178.google.com with SMTP id h3so2202817igd.5
for <bitcoin-development@lists.sourceforge.net>;
Sat, 18 Oct 2014 03:13:29 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.128.4 with SMTP id k4mr15426734ics.8.1413627208930; Sat,
18 Oct 2014 03:13:28 -0700 (PDT)
Received: by 10.64.141.112 with HTTP; Sat, 18 Oct 2014 03:13:28 -0700 (PDT)
In-Reply-To: <CABbpET8x__gvSLhVp54GcC5FFVs1buE_-7D4xiqpX0ncB2GPJQ@mail.gmail.com>
References: <CABbpET8x__gvSLhVp54GcC5FFVs1buE_-7D4xiqpX0ncB2GPJQ@mail.gmail.com>
Date: Sat, 18 Oct 2014 12:13:28 +0200
Message-ID: <CA+s+GJBsgKrZgtOTHFqpbGPp8YfbYdRE885emiqMApGfUGX0WA@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Flavien Charlon <flavien.charlon@coinprism.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1XfR0w-0005Uj-9u
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] About watch-only addresses
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 18 Oct 2014 10:13:35 -0000
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
|
