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 <mh.in.england@gmail.com>) id 1XgAdT-0004b1-4B
	for bitcoin-development@lists.sourceforge.net;
	Mon, 20 Oct 2014 10:56:23 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.172 as permitted sender)
	client-ip=209.85.214.172; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f172.google.com; 
Received: from mail-ob0-f172.google.com ([209.85.214.172])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XgAdR-0007VC-Et
	for bitcoin-development@lists.sourceforge.net;
	Mon, 20 Oct 2014 10:56:23 +0000
Received: by mail-ob0-f172.google.com with SMTP id vb8so3623023obc.31
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 20 Oct 2014 03:56:16 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.98.142 with SMTP id ei14mr87978oeb.77.1413802575819; Mon,
	20 Oct 2014 03:56:15 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.108.196 with HTTP; Mon, 20 Oct 2014 03:56:15 -0700 (PDT)
In-Reply-To: <5442B4BC.9040601@walltime.info>
References: <CABbpET8x__gvSLhVp54GcC5FFVs1buE_-7D4xiqpX0ncB2GPJQ@mail.gmail.com>
	<CA+s+GJBsgKrZgtOTHFqpbGPp8YfbYdRE885emiqMApGfUGX0WA@mail.gmail.com>
	<5442B4BC.9040601@walltime.info>
Date: Mon, 20 Oct 2014 12:56:15 +0200
X-Google-Sender-Auth: njgAsS-A7KAUCOr1rXfUZ0CuVnA
Message-ID: <CANEZrP043U1FNcTPDg1OLPz-Hej48G+UGb4rh9bSp8qcGE=eVg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Felipe Micaroni Lalli <micaroni@walltime.info>
Content-Type: multipart/alternative; boundary=089e0115f8165078bc0505d8902a
X-Spam-Score: -0.5 (/)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1XgAdR-0007VC-Et
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: Mon, 20 Oct 2014 10:56:23 -0000

--089e0115f8165078bc0505d8902a
Content-Type: text/plain; charset=UTF-8

>
> This feature makes possible Bitcoin Core to read a balance of any
> public address via RPC call or, after importing the balance, it became
> available only via QT interface?


Neither. A watching wallet still has to be synced with the chain in the
same way as any other wallet, i.e. after adding an address, if it was
already used, you must rescan.

--089e0115f8165078bc0505d8902a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">This feature makes possible Bitcoin Core to read=
 a balance of any<br>
public address via RPC call or, after importing the balance, it became<br>
available only via QT interface?</blockquote><div><br></div><div>Neither. A=
 watching wallet still has to be synced with the chain in the same way as a=
ny other wallet, i.e. after adding an address, if it was already used, you =
must rescan.=C2=A0</div></div></div></div>

--089e0115f8165078bc0505d8902a--