From: Eric Voskuil <eric@voskuil.org>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: [BIP Draft] P2P UTXO Set Sharing
Date: Sat, 16 May 2026 19:09:39 -0700 (PDT) [thread overview]
Message-ID: <26c7fd2e-d35d-4ed4-9638-18c95efc75dfn@googlegroups.com> (raw)
In-Reply-To: <RiAeHX6Gt48YabQbYIIOFyMF63Pziq12Czi1gSAHlXZ3dBWHIs6l5P-egzOYpyShLUQKVcIeb1pW358WsHR5pALr6T5xAHoN6Igg9Hg0NS0=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1956 bytes --]
From: Fabian
> The header chain is fully validated before the snapshot is loaded,
Validating the headers is inconsequential if you are not verifying tx
inclusion. That's what SPV is, and people should not be misled into
believing that this is SPV.
> and the historical blocks are validated in the background.
The issue is the time before that completing. After validating it's moot.
> The work is the same, only the node becomes usable earlier.
Until the work is complete the node is not usable in the sense of a node -
it hasn't validated.
> AssumeUTXO is anchored to a hash that is hardcoded in Bitcoin Core
> and reviewed in the open. Anyone running a fully validating node can
> independently reproduce it from their own UTXO set.
In this proposal there is no statement that everyone must trust Bitcoin
Core. The proposal specifically states:
"The Merkle root is the sole trust input required to verify the
integrity of the received UTXO set."
and
"[The Merkle root is]... either from a trusted source or by selecting a
root with agreement among multiple peers."
The "agreement among peers" is why Bitcoin exists, so we can dismiss that
as an infinite regression.
Above you make the explicit claim that Bitcoin Core is the oracle for this
"sole trust input". If that is the case you should add it to the proposal
so that people are fully aware.
If so the proposal establishes a central authority for validity. If not
then we are back to the original problem that Bitcoin supposedly solved -
where does this agreement come from.
Best,
Eric
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/26c7fd2e-d35d-4ed4-9638-18c95efc75dfn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2401 bytes --]
next prev parent reply other threads:[~2026-05-17 2:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 15:36 [bitcoindev] [BIP Draft] P2P UTXO Set Sharing 'Fabian' via Bitcoin Development Mailing List
2026-05-05 16:01 ` [bitcoindev] " Eric Voskuil
2026-05-06 1:06 ` Antoine Riard
2026-05-07 21:50 ` 'Fabian' via Bitcoin Development Mailing List
2026-05-07 21:34 ` 'Fabian' via Bitcoin Development Mailing List
2026-05-12 15:56 ` eric
2026-05-15 23:08 ` Anthony Towns
2026-05-16 0:58 ` eric
2026-05-16 17:58 ` Saint Wenhao
2026-05-16 21:48 ` 'Fabian' via Bitcoin Development Mailing List
2026-05-17 2:09 ` Eric Voskuil [this message]
2026-05-17 8:50 ` sadiq Ismail
2026-05-17 21:29 ` Eric Voskuil
2026-05-18 1:36 ` Eric Voskuil
2026-05-19 8:36 ` 'Fabian' via Bitcoin Development Mailing List
2026-05-19 23:20 ` Eric Voskuil
2026-05-16 22:39 ` Eric Voskuil
2026-05-19 9:32 ` josie
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=26c7fd2e-d35d-4ed4-9638-18c95efc75dfn@googlegroups.com \
--to=eric@voskuil.org \
--cc=bitcoindev@googlegroups.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