public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related services
Date: Fri, 8 Aug 2014 14:13:45 +0200	[thread overview]
Message-ID: <CANEZrP3ij79gNxHCYbvhJ15=UQZmWPTuUng9aC-nFN6Z28riPw@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0MOn5XxAFzqDPgvM=jrr8PRx=Lkatpw30xZqiOQDaK52Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 794 bytes --]

>
> 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.

[-- Attachment #2: Type: text/html, Size: 1192 bytes --]

      reply	other threads:[~2014-08-08 12:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  3:38 [Bitcoin-development] NODE_EXT_SERVICES and advertising related services Jeff Garzik
2014-08-08  9:45 ` Mike Hearn
2014-08-08  9:56   ` Wladimir
2014-08-08 10:01     ` Mike Hearn
2014-08-08 10:15       ` Wladimir
2014-08-08 10:26         ` Wladimir
2014-08-08 10:41           ` Christian Decker
2014-08-08 11:22             ` Jeff Garzik
2014-08-08 11:33       ` Jeff Garzik
2014-08-08 11:38         ` Mike Hearn
2014-08-08 11:59           ` Wladimir
2014-08-08 12:06             ` Jeff Garzik
2014-08-08 12:11             ` Jeff Garzik
2014-08-08 12:15               ` Wladimir
2014-08-08 12:11             ` Mike Hearn
2014-08-08 12:15               ` Jeff Garzik
2014-08-08 12:16               ` Wladimir
2014-08-08 12:34               ` Wladimir
2014-08-08 13:55                 ` Mike Hearn
2014-08-08 12:04           ` Jeff Garzik
2014-08-08 12:13             ` Mike Hearn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANEZrP3ij79gNxHCYbvhJ15=UQZmWPTuUng9aC-nFN6Z28riPw@mail.gmail.com' \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@bitpay.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox