Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XFj3Q-0004Dg-1K for bitcoin-development@lists.sourceforge.net; Fri, 08 Aug 2014 12:13:52 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.218.47 as permitted sender) client-ip=209.85.218.47; envelope-from=mh.in.england@gmail.com; helo=mail-oi0-f47.google.com; Received: from mail-oi0-f47.google.com ([209.85.218.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XFj3P-0007XU-4k for bitcoin-development@lists.sourceforge.net; Fri, 08 Aug 2014 12:13:51 +0000 Received: by mail-oi0-f47.google.com with SMTP id x69so3577061oia.6 for ; Fri, 08 Aug 2014 05:13:45 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.209.101 with SMTP id ml5mr30328702obc.2.1407500025649; Fri, 08 Aug 2014 05:13:45 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.35.234 with HTTP; Fri, 8 Aug 2014 05:13:45 -0700 (PDT) In-Reply-To: References: Date: Fri, 8 Aug 2014 14:13:45 +0200 X-Google-Sender-Auth: R7cditG2TUToBkUdT1NreNZSi6s Message-ID: From: Mike Hearn To: Jeff Garzik Content-Type: multipart/alternative; boundary=e89a8ff1ca200ce05105001d231c 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: 1XFj3P-0007XU-4k Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related services X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2014 12:13:52 -0000 --e89a8ff1ca200ce05105001d231c Content-Type: text/plain; charset=UTF-8 > > Yes, that is the one change I am still pondering: adding categories > (classes), rather than one single bit. > Sure, that makes more sense I think. As a motivating use case, Bitcoin Wallet for Android currently has a hard-coded block explorer (biteasy.com) which it uses to find UTXOs for a given key. This is used for its "Sweep paper wallet" feature. It must work this way because P2P nodes don't calculate such indexes. If there was a way to do block index autodiscovery, that'd help us remove this hard-coded block explorer and increase decentralisation. But because it's a GUI app we don't want users to look at a spinner for more than a few seconds, so a slow discovery process would make it unworkable. With API-based categories of service bits we could implement such a scheme. --e89a8ff1ca200ce05105001d231c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes, that is the one change I am still pondering= : =C2=A0adding categories
(classes), rather than one single bit.

= Sure, that makes more sense I think.

As a motivating use case, Bitcoin Wallet for Android c= urrently has a hard-coded block explorer (bi= teasy.com) which it uses to find UTXOs for a given key. This is used fo= r its "Sweep paper wallet" feature. It must work this way because= P2P nodes don't calculate such indexes.

If there wa= s a way to do block index autodiscovery, that'd help us remove this har= d-coded block explorer and increase decentralisation. But because it's = a GUI app we don't want users to look at a spinner for more than a few = seconds, so a slow discovery process would make it unworkable. With API-bas= ed categories of service bits we could implement such a scheme.
--e89a8ff1ca200ce05105001d231c--