public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Elden Tyrell <tyrell.elden@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] does "stubbing" off Merkle trees reduce initial download bandwidth?
Date: Mon, 2 Jan 2012 14:23:16 -0800	[thread overview]
Message-ID: <jdtaol$3ku$1@dough.gmane.org> (raw)
In-Reply-To: CALxbBHU7f1m+p45RHLhN-VGBoXJEi62x5mZUiAe_d5D-5Ga7yA@mail.gmail.com

On 2012-01-02 05:31:19 -0800, Christian Decker said:
> Later full blocks would be required to detect usable inputs for future 
> outgoing transactions.

Er, yes, this is what I meant; I guess I should have been more specific.

So, a paranoid client cannot confirm reciept of coins until it has an 
unstubbed copy of the entire chain.  It can do other things (like send 
coins) using a stubbed chain, but it needs the whole unstubbed chain in 
order to be sure that incoming coins haven't already been spent.

Thanks for confirming this.





  reply	other threads:[~2012-01-02 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02  5:04 [Bitcoin-development] does "stubbing" off Merkle trees reduce initial download bandwidth? Elden Tyrell
2012-01-02 13:31 ` Christian Decker
2012-01-02 22:23   ` Elden Tyrell [this message]
2012-01-02 22:41     ` Gregory Maxwell
2012-01-03  1:39       ` Elden Tyrell
2012-01-05 23:30         ` Mike Hearn

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='jdtaol$3ku$1@dough.gmane.org' \
    --to=tyrell.elden@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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