From: Mike Hearn <mike@plan99•net>
To: Andy Parkins <andyparkins@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Suggestion for enhancements to getblock
Date: Thu, 7 Jul 2011 18:44:48 +0200 [thread overview]
Message-ID: <CANEZrP1eEmjqLAhAWHXTWurUVP7P1pxuf6e0w_0UF2DGZo3ZQw@mail.gmail.com> (raw)
In-Reply-To: <201107071719.45416.andyparkins@gmail.com>
> What I want to be able to do though is calculate a balance for an aribtrary
> address. Not every address; just the particular ones that the client is
> interested in. It's complete overkill to require the whole block chain just
> to calculate the balance of a few addresses.
But what is that for? You said it's for a lightweight client to do
that when it receives a transaction, to verify that all the
dependencies are in blocks recursively. But why?
> Not entirely. If I ask for "the block that contains transaction with hash
> 12345678abcd..." then when I get that full block, I can verify the merkle tree
> myself.
Well, it's more efficient to just verify the merkle branch. But yes.
> I'm not entirely sure I see how a filter helps. If I've been offline for ten
> minutes then I need all the transactions pending in the last ten minutes. No
> amount of filtering makes that list any smaller.
Why do you need all of them? You just care about the ones sending
coins to you, surely?
> That would be fine. My reason for suggesting using getblocks was that it
> didn't introduce a new command.
IMHO it's fine to introduce new commands. They'll just be ignored by
old clients in any event.
next prev parent reply other threads:[~2011-07-07 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 9:49 Andy Parkins
2011-07-07 15:42 ` Mike Hearn
2011-07-07 16:19 ` Andy Parkins
2011-07-07 16:44 ` Mike Hearn [this message]
2011-07-07 19:02 ` Andy Parkins
2011-07-07 17:45 ` Gregory Maxwell
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=CANEZrP1eEmjqLAhAWHXTWurUVP7P1pxuf6e0w_0UF2DGZo3ZQw@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=andyparkins@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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