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
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <flavien.charlon@pixodegames.com>) id 1XfFJP-0004tJ-BX
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Oct 2014 21:43:51 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of
pixodegames.com designates 209.85.213.44 as permitted sender)
client-ip=209.85.213.44;
envelope-from=flavien.charlon@pixodegames.com;
helo=mail-yh0-f44.google.com;
Received: from mail-yh0-f44.google.com ([209.85.213.44])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XfFJO-0006cg-Au
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Oct 2014 21:43:51 +0000
Received: by mail-yh0-f44.google.com with SMTP id i57so747198yha.31
for <bitcoin-development@lists.sourceforge.net>;
Fri, 17 Oct 2014 14:43:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to
:content-type;
bh=orhMfl+Ou7n8JmD+lZtMhoM5T/U3CWV4SEx7gREBwBM=;
b=hxII9A8Gp/eR253fMoHHNAZhRfSDf57Wyw0smwf27sCK/Lv09nPhC3r09ZldvXi81o
ngl+dN0NlLYoO1tbkIi+tY3/8NhRfrmbFJYjkbA/+BaWHT0FSerCOzlSAEnRRXPka/TH
l5801ozvht7tvI6/AJKnbL9eTNo0V0mNiEP9trT9/piH4s/E+9++YI0puXT2z41dA1py
nVxUETkzBxcLtalK66ccOIH2dF3Fz2unx5lu3G7Wv94MoauizCbC8rvMlzmVC0pIE4PJ
oMwZC9Jd2vAP+Js7T37pd8QoH9jiBSXcWjs9M/C3whHnpBUCH45Cmd7G/TAPab+Gaj1y
ipVg==
X-Gm-Message-State: ALoCoQk1tn4q6PiWRGL/feJfbCE8KHF9HwmmBON6L6jqIOVdmeZV/BGr8mp8pEjCdCxCsgO7/eDy
X-Received: by 10.236.16.230 with SMTP id h66mr7898410yhh.145.1413578206087;
Fri, 17 Oct 2014 13:36:46 -0700 (PDT)
Received: from mail-yk0-f181.google.com (mail-yk0-f181.google.com.
[209.85.160.181])
by mx.google.com with ESMTPSA id z65sm3453156yha.44.2014.10.17.13.36.45
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Fri, 17 Oct 2014 13:36:45 -0700 (PDT)
Received: by mail-yk0-f181.google.com with SMTP id q200so667553ykb.26
for <bitcoin-development@lists.sourceforge.net>;
Fri, 17 Oct 2014 13:36:45 -0700 (PDT)
X-Received: by 10.236.28.229 with SMTP id g65mr14879112yha.26.1413578205754;
Fri, 17 Oct 2014 13:36:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.170.58.202 with HTTP; Fri, 17 Oct 2014 13:36:04 -0700 (PDT)
X-Originating-IP: [89.100.161.202]
From: Flavien Charlon <flavien.charlon@coinprism.com>
Date: Fri, 17 Oct 2014 21:36:04 +0100
Message-ID: <CABbpET8x__gvSLhVp54GcC5FFVs1buE_-7D4xiqpX0ncB2GPJQ@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c1f9fad10c600505a4529d
X-Spam-Score: -0.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 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1XfFJO-0006cg-Au
Subject: [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: Fri, 17 Oct 2014 21:43:51 -0000
--001a11c1f9fad10c600505a4529d
Content-Type: text/plain; charset=UTF-8
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.
Also, I believe that is going towards the 0.10 release, is there a
rough ETA for a release candidate?
Thanks
Flavien
--001a11c1f9fad10c600505a4529d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>What is the status of wa=
tch-only addresses in Bitcoin Core? Is it merged in master and usable? Is t=
here documentation on how to add a watch-only address through RPC.</div><di=
v><br></div><div>Also, I believe that is going towards the 0.10 release, is=
there a rough=C2=A0ETA for a release candidate?</div><div><br></div><div>T=
hanks</div><div>Flavien</div></div>
--001a11c1f9fad10c600505a4529d--
|
