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 1XfQZF-00007f-1d for bitcoin-development@lists.sourceforge.net; Sat, 18 Oct 2014 09:44:57 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of pixodegames.com designates 209.85.160.170 as permitted sender) client-ip=209.85.160.170; envelope-from=flavien.charlon@pixodegames.com; helo=mail-yk0-f170.google.com; Received: from mail-yk0-f170.google.com ([209.85.160.170]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XfQZE-0001bu-10 for bitcoin-development@lists.sourceforge.net; Sat, 18 Oct 2014 09:44:57 +0000 Received: by mail-yk0-f170.google.com with SMTP id 20so977837yks.1 for <bitcoin-development@lists.sourceforge.net>; Sat, 18 Oct 2014 02:44:50 -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:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=SSvzODPAgiPkMopFcyVL7cabvs6cPdyldOgUf/qYeLc=; b=SJjQr86CKYwCFzwgcsnXzx85PZ8JtgNK+l8Ce1CZddq2cJis7fBPFdcxD7ssCEnJT7 FCKC+CGO1OPdvPXorJc5tlt5lGbWAji+b/++FEK0CrKzUVa+N46ruF1uOcliw2kXbQnf 0RNS8gdgfPIaR3llVe5GdBkIJciG+iA15F9NNLqxBhqagLIs1tTw3R7t59Oi32yXyl7k UE0Y+lGirXO5o6rAx/WXaTjnwq6MgAwWVf4uFRCgpnVFpBOgVyuhCykHPehGPxSExERj wMe229ZeUvHctVwn/raCyu5J9v8RZJ3gtgvu//VDFNPwjGpWAxZkRXuQi4tyEX/mSl3Z vWWQ== X-Gm-Message-State: ALoCoQnSISOKWnGGTeyKQt84LOO6dzTdZ3MxF5Y+MlIqZ1u+N55OU3gQqD4mQmia/lS8dEbx0qiM X-Received: by 10.236.15.103 with SMTP id e67mr19920919yhe.22.1413625490489; Sat, 18 Oct 2014 02:44:50 -0700 (PDT) Received: from mail-yk0-f175.google.com (mail-yk0-f175.google.com. [209.85.160.175]) by mx.google.com with ESMTPSA id c59sm4273762yho.2.2014.10.18.02.44.50 for <bitcoin-development@lists.sourceforge.net> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Oct 2014 02:44:50 -0700 (PDT) Received: by mail-yk0-f175.google.com with SMTP id 19so966242ykq.6 for <bitcoin-development@lists.sourceforge.net>; Sat, 18 Oct 2014 02:44:50 -0700 (PDT) X-Received: by 10.236.230.40 with SMTP id i38mr19934115yhq.34.1413625490227; Sat, 18 Oct 2014 02:44:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.58.202 with HTTP; Sat, 18 Oct 2014 02:44:10 -0700 (PDT) X-Originating-IP: [89.100.161.202] In-Reply-To: <CABbpET8x__gvSLhVp54GcC5FFVs1buE_-7D4xiqpX0ncB2GPJQ@mail.gmail.com> References: <CABbpET8x__gvSLhVp54GcC5FFVs1buE_-7D4xiqpX0ncB2GPJQ@mail.gmail.com> From: Flavien Charlon <flavien.charlon@coinprism.com> Date: Sat, 18 Oct 2014 10:44:10 +0100 Message-ID: <CABbpET9NHKyfPTjam3gH8McT+Bz197BiVAtoBTtODU=BtJ70qQ@mail.gmail.com> To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Content-Type: multipart/alternative; boundary=089e0160d0f830dd8e0505af5562 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: 1XfQZE-0001bu-10 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 09:44:57 -0000 --089e0160d0f830dd8e0505af5562 Content-Type: text/plain; charset=UTF-8 Also, I was wondering if there were nightly builds I could try this from? On Fri, Oct 17, 2014 at 9: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. > > Also, I believe that is going towards the 0.10 release, is there a > rough ETA for a release candidate? > > Thanks > Flavien > --089e0160d0f830dd8e0505af5562 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Also, I was wondering if there were nightly builds I could= try this from?</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quo= te">On Fri, Oct 17, 2014 at 9:36 PM, Flavien Charlon <span dir=3D"ltr"><= <a href=3D"mailto:flavien.charlon@coinprism.com" target=3D"_blank">flavien.= charlon@coinprism.com</a>></span> wrote:<br><blockquote class=3D"gmail_q= uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e= x"><div dir=3D"ltr"><div>Hi,</div><div><br></div><div>What is the status of= watch-only addresses in Bitcoin Core? Is it merged in master and usable? I= s there documentation on how to add a watch-only address through RPC.</div>= <div><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><di= v>Thanks</div><span class=3D"HOEnZb"><font color=3D"#888888"><div>Flavien</= div></font></span></div> </blockquote></div><br></div> --089e0160d0f830dd8e0505af5562--