I like the backwards syncing idea. First you provide proof of your best block
height via coinbase, then sync backwards. It solves lots of related problems.
You know how much you can expect from the given peer.
On different note, one of the problems that I haven't seen mentioned here yet
is the
On Sat, Oct 12, 2019 at 6:56 PM Joachim Strömbergson <
joachim...@protonmail.com> wrote:
> I like the backwards syncing idea. First you provide proof of your best
> block height via coinbase, then sync backwards. It solves lots of related
> problems. You know how much you can expect from the given
Hi Jonas,
Let's review case when we create filters for part of mempool or whole mempool.
After new block is mined we have to verify what transactions is confirmed from
mempool. Mempool filter in design with set of transactions make impossible use
it do block filter reconstruction because we ha
On Thu, Oct 10, 2019 at 5:20 PM Braydon Fuller via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> It would be interesting to have a succinct chainwork proof
> for all cases. Chainwork being a sum of the total proof-of-work in a
> chain. Such proofs currently only require a few head
