summaryrefslogtreecommitdiff
path: root/1c/2184a78d8a9c5b11b70cb7ed710fcb56719845
blob: f61535ba45829a36d013336603ccd355efd6f5bb (plain)
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
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mbde@bitwatch.co>) id 1XgMIq-0000VE-R8
	for bitcoin-development@lists.sourceforge.net;
	Mon, 20 Oct 2014 23:23:52 +0000
Received: from dd32718.kasserver.com ([85.13.150.64])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1XgMIo-0000JI-Nk
	for bitcoin-development@lists.sourceforge.net;
	Mon, 20 Oct 2014 23:23:52 +0000
Received: from [192.168.1.100] (ip-95-222-210-186.hsi15.unitymediagroup.de
	[95.222.210.186])
	by dd32718.kasserver.com (Postfix) with ESMTPSA id BCD004900086
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 21 Oct 2014 01:06:26 +0200 (CEST)
Message-ID: <5445957C.9060408@bitwatch.co>
Date: Tue, 21 Oct 2014 01:06:36 +0200
From: "mbde@bitwatch.co" <mbde@bitwatch.co>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
	rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CABbpET8x__gvSLhVp54GcC5FFVs1buE_-7D4xiqpX0ncB2GPJQ@mail.gmail.com>	<CA+s+GJBsgKrZgtOTHFqpbGPp8YfbYdRE885emiqMApGfUGX0WA@mail.gmail.com>
	<CAEz79PrNk2fSOxrA4yQMiRU3yNF1eQMEQqaraoLs65T7KWK+vw@mail.gmail.com>
In-Reply-To: <CAEz79PrNk2fSOxrA4yQMiRU3yNF1eQMEQqaraoLs65T7KWK+vw@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------090500040507040804090108"
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1XgMIo-0000JI-Nk
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 23:23:53 -0000

This is a multi-part message in MIME format.
--------------090500040507040804090108
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

This is just a guess, but I can imagine sipa's address index branch
might be more suitable for an use case where information about any
address is required - jmcorgan continued to maintain a usually somewhat
up-to-date version:

https://github.com/jmcorgan/bitcoin/tree/addrindex

As for balance queries, that's not possible out of the box and I have my
own branch for this with a few other RPC calls that are noted in the README:

https://github.com/dexX7/bitcoin/tree/master-addrindex-extended

When using the original, you need to ensure a transaction is part of the
main chain and wasn't orphaned. If you consider using my branch, please
consider it twice and review the changes first.

-------- Original Message --------
*Subject: *Re: [Bitcoin-development] About watch-only addresses
*From: *Warren Togami Jr. <wtogami@gmail.com>
*To: *Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
*Date: *Mon, 20 Oct 2014 12:37:40 -1000
> 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
> <mailto:laanwj@gmail.com>> wrote:
>
>     On Fri, Oct 17, 2014 at 10:36 PM, Flavien Charlon
>     <flavien.charlon@coinprism.com
>     <mailto: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
>     <mailto:Bitcoin-development@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> 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


--------------090500040507040804090108
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dwindows-1252"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">This is just a guess, but I can imagin=
e
      sipa's address index branch might be more suitable for an use case
      where information about any address is required - jmcorgan
      continued to maintain a usually somewhat up-to-date version:<br>
      <br>
      <a class=3D"moz-txt-link-freetext" href=3D"https://github.com/jmcor=
gan/bitcoin/tree/addrindex">https://github.com/jmcorgan/bitcoin/tree/addr=
index</a><br>
      <br>
      As for balance queries, that's not possible out of the box and I
      have my own branch for this with a few other RPC calls that are
      noted in the README:<br>
      <br>
      <a class=3D"moz-txt-link-freetext" href=3D"https://github.com/dexX7=
/bitcoin/tree/master-addrindex-extended">https://github.com/dexX7/bitcoin=
/tree/master-addrindex-extended</a><br>
      <br>
      When using the original, you need to ensure a transaction is part
      of the main chain and wasn't orphaned. If you consider using my
      branch, please consider it twice and review the changes first.<br>
      <br>
      -------- Original Message --------<br>
      <b>Subject: </b>Re: [Bitcoin-development] About watch-only
      addresses<br>
      <b>From: </b>Warren Togami Jr. <a class=3D"moz-txt-link-rfc2396E" h=
ref=3D"mailto:wtogami@gmail.com">&lt;wtogami@gmail.com&gt;</a><br>
      <b>To: </b>Bitcoin Dev
      <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:bitcoin-developme=
nt@lists.sourceforge.net">&lt;bitcoin-development@lists.sourceforge.net&g=
t;</a><br>
      <b>Date: </b>Mon, 20 Oct 2014 12:37:40 -1000</div>
    <blockquote
cite=3D"mid:CAEz79PrNk2fSOxrA4yQMiRU3yNF1eQMEQqaraoLs65T7KWK+vw@mail.gmai=
l.com"
      type=3D"cite">
      <div dir=3D"ltr"><a moz-do-not-send=3D"true"
          href=3D"https://bitcointalk.org/index.php?topic=3D320695">https=
://bitcointalk.org/index.php?topic=3D320695</a><br>
        <div>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.=A0 It seems to work fine although it is not
          heavily tested.=A0 I suppose if you use ONLY for watch-only it
          can't be harmful?=A0 Dunno.</div>
        <div><br>
        </div>
        <div>Warren</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">&lt;<a moz-do-not-send=3D"true"
              href=3D"mailto:laanwj@gmail.com" target=3D"_blank">laanwj@g=
mail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><span
              class=3D"">On Fri, Oct 17, 2014 at 10:36 PM, Flavien Charlo=
n<br>
              &lt;<a moz-do-not-send=3D"true"
                href=3D"mailto:flavien.charlon@coinprism.com">flavien.cha=
rlon@coinprism.com</a>&gt;
              wrote:<br>
              &gt; Hi,<br>
              &gt;<br>
              &gt; What is the status of watch-only addresses in Bitcoin
              Core? Is it merged in<br>
              &gt; master and usable? Is there documentation on how to
              add a watch-only address<br>
              &gt; 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>
              &gt; Also, I believe that is going towards the 0.10
              release, is there a rough ETA<br>
              &gt; 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 moz-do-not-send=3D"true"
              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 going<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.<br>
            Take corrective actions from your mobile device.<br>
            <a moz-do-not-send=3D"true" 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 moz-do-not-send=3D"true"
              href=3D"mailto:Bitcoin-development@lists.sourceforge.net">B=
itcoin-development@lists.sourceforge.net</a><br>
            <a moz-do-not-send=3D"true"
              href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoi=
n-development"
              target=3D"_blank">https://lists.sourceforge.net/lists/listi=
nfo/bitcoin-development</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">----------------------------------------------------=
--------------------------
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.
<a class=3D"moz-txt-link-freetext" href=3D"http://p.sf.net/sfu/Zoho">http=
://p.sf.net/sfu/Zoho</a></pre>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
Bitcoin-development mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Bitcoin-development@=
lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.sourceforge.net/=
lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/l=
istinfo/bitcoin-development</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------090500040507040804090108--