Hello,
I see that people have been filing issues on the Bitcoin Improvement
Requests repository, https://github.com/bitcoin/bips.
This is not how it is supposed to work -- BIP authors are not required
to monitor the github issues, and it is not a good place to discuss in
the first place. If you h
On Thu, Jun 5, 2014 at 7:43 PM, Richard Moore wrote:
> I was considering names like getcheckpoints() to use the terminology that
> already seemed to be in place, but they were too long :)
>
> I have been using getheaders() in my thick client to quickly grab all the
> headers before downloading the
I was considering names like getcheckpoints() to use the terminology that
already seemed to be in place, but they were too long :)
I have been using getheaders() in my thick client to quickly grab all the
headers before downloading the full blocks since I can grab more at a time.
Even with getb
The correct approach here is header hash-tree commitments which enable
compact (logarithmic) SPV proofs that elide nearly all intervening
headers since the last checkpoint. You could then query the hash tree
for references to any of the headers you actually need.
See this message for details:
htt
4 matches
Mail list logo
