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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wtogami@gmail.com>) id 1XgLaF-0001wr-9n
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Oct 2014 22:37:47 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.44 as permitted sender)
client-ip=209.85.213.44; envelope-from=wtogami@gmail.com;
helo=mail-yh0-f44.google.com;
Received: from mail-yh0-f44.google.com ([209.85.213.44])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XgLaE-0004f9-0z
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Oct 2014 22:37:47 +0000
Received: by mail-yh0-f44.google.com with SMTP id i57so19065yha.17
for <bitcoin-development@lists.sourceforge.net>;
Mon, 20 Oct 2014 15:37:40 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.39.5 with SMTP id c5mr44792154yhb.92.1413844660553; Mon,
20 Oct 2014 15:37:40 -0700 (PDT)
Received: by 10.170.98.195 with HTTP; Mon, 20 Oct 2014 15:37:40 -0700 (PDT)
In-Reply-To: <CA+s+GJBsgKrZgtOTHFqpbGPp8YfbYdRE885emiqMApGfUGX0WA@mail.gmail.com>
References: <CABbpET8x__gvSLhVp54GcC5FFVs1buE_-7D4xiqpX0ncB2GPJQ@mail.gmail.com>
<CA+s+GJBsgKrZgtOTHFqpbGPp8YfbYdRE885emiqMApGfUGX0WA@mail.gmail.com>
Date: Mon, 20 Oct 2014 12:37:40 -1000
Message-ID: <CAEz79PrNk2fSOxrA4yQMiRU3yNF1eQMEQqaraoLs65T7KWK+vw@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a1136b9b2c28d640505e25c45
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(wtogami[at]gmail.com)
-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: 1XgLaE-0004f9-0z
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: Mon, 20 Oct 2014 22:37:47 -0000
--001a1136b9b2c28d640505e25c45
Content-Type: text/plain; charset=UTF-8
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
>
--001a1136b9b2c28d640505e25c45
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><a href=3D"https://bitcointalk.org/index.php?topic=3D32069=
5">https://bitcointalk.org/index.php?topic=3D320695</a><br><div>I made a br=
anch of Bitcoin 0.9.3 plus backports including watch-only and a huge pile o=
f patches cleaning it up from the master branch.=C2=A0 It seems to work fin=
e although it is not heavily tested.=C2=A0 I suppose if you use ONLY for wa=
tch-only it can't be harmful?=C2=A0 Dunno.</div><div><br></div><div>War=
ren</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On=
Sat, Oct 18, 2014 at 12:13 AM, Wladimir <span dir=3D"ltr"><<a href=3D"m=
ailto:laanwj@gmail.com" target=3D"_blank">laanwj@gmail.com</a>></span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On Fri, Oct 17, 20=
14 at 10:36 PM, Flavien Charlon<br>
<<a href=3D"mailto:flavien.charlon@coinprism.com">flavien.charlon@coinpr=
ism.com</a>> wrote:<br>
> Hi,<br>
><br>
> What is the status of watch-only addresses in Bitcoin Core? Is it merg=
ed in<br>
> master and usable? Is there documentation on how to add a watch-only a=
ddress<br>
> through RPC.<br>
<br>
</span>It has been merged. There is the "importaddress" RPC call,=
which works<br>
the same as "importprivkey" except that you a pass it an address.=
<br>
<span class=3D""><br>
> Also, I believe that is going towards the 0.10 release, is there a rou=
gh ETA<br>
> for a release candidate?<br>
<br>
</span>Yes - aim is in a few months, probably by the end of the year.<br>
<br>
AFAIK there are no nightly builds at this moment. Warren Togami was<br>
building them for a while (at <a href=3D"http://nightly.bitcoin.it/" target=
=3D"_blank">http://nightly.bitcoin.it/</a>) but he<br>
stopped some time around June.<br>
<br>
It's not recommended to use master without at least a little bit of<br>
development/debugging experience of yourself (to trace down problems<br>
when they appear), so it's best to build it yourself if you're goin=
g<br>
to test day-to-day development versions.<br>
<br>
Wladimir<br>
<br>
---------------------------------------------------------------------------=
---<br>
Comprehensive Server Monitoring with Site24x7.<br>
Monitor 10 servers for $9/Month.<br>
Get alerted through email, SMS, voice calls or mobile push notifications.<b=
r>
Take corrective actions from your mobile device.<br>
<a href=3D"http://p.sf.net/sfu/Zoho" target=3D"_blank">http://p.sf.net/sfu/=
Zoho</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>
--001a1136b9b2c28d640505e25c45--
|
