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: Sun, 24 May 2026 12:32:46 -0700 (PDT) [thread overview]
Message-ID: <6292786d-6509-486d-945c-b8c7f6225e81n@googlegroups.com> (raw)
In-Reply-To: <KRJNxmvJhInTDgjGdVBPS5kzWXngejQhVHjtuD3jTdPoyAUSGz-dOc3LkuPlA5MAKiVJUGZ5mhAC-6Orx7AUFwe7Mtm2NBbOQv3x-diwfwM=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1770 bytes --]
>Hi Josie,
> ...
> Hosting the files would give a constant attack surface to the process
> of fetching them. At any point the server could be DoS'd, the network
> layer could be attacked (BGP, DNS), admins could be compromised, legal
> avenues explored to take down hosting providers or ISP connections,
> regional reliability issues can disrupt this and so on.
As you point out immediately below, this is actually just a cost...
> Sure, these are problems that most internet companies face and where
> solutions exist but these are usually costly and require constant
> maintenance.
Yes, there is a cost for hosting your own content.
Sure, anyone can create the content, but it's unusable without the trusted
authority. You have confirmed this by repeatedly pointing out that the
authority is trustworthy (they write the code and engage in public review),
while at the same time suggesting that there is no such authority (and
unspecified in the BIP). It's not clear which it is... trusted authority or
untrustworthy.
> The uptime of the bitcoin network has famously been pretty good
The fact that it's cheaper for you is not justification for foisting an
identity/authority/trust-based system onto the Bitcoin network. You're
explaining to us how you will centralize Bitcoin validation, but that you
don't want to pay for it. It's not exactly the most compelling argument.
e
--
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/6292786d-6509-486d-945c-b8c7f6225e81n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2174 bytes --]
next prev parent reply other threads:[~2026-05-24 19:48 UTC|newest]
Thread overview: 27+ 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
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-22 12:32 ` 'Fabian' via Bitcoin Development Mailing List
2026-05-24 20:58 ` Eric Voskuil
2026-05-24 15:53 ` Eric Voskuil
2026-05-24 23:50 ` 'Fabian' via Bitcoin Development Mailing List
2026-05-25 0:45 ` Eric Voskuil
2026-05-16 22:39 ` Eric Voskuil
2026-05-19 9:32 ` josie
2026-05-22 12:52 ` 'Fabian' via Bitcoin Development Mailing List
2026-05-24 19:32 ` Eric Voskuil [this message]
2026-06-05 11:24 ` Anthony Towns
2026-06-08 11:37 ` Josie Baker
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=6292786d-6509-486d-945c-b8c7f6225e81n@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