From: Anthony Towns <aj@erisian.com.au>
To: 'Bitcoin Development Mailing List' <bitcoindev@googlegroups.com>
Cc: eric@voskuil.org, 'Fabian' <fjahr@protonmail.com>
Subject: Re: [bitcoindev] Re: [BIP Draft] P2P UTXO Set Sharing
Date: Sat, 16 May 2026 09:08:25 +1000 [thread overview]
Message-ID: <agenaZ5mfhghneYo@erisian.com.au> (raw)
In-Reply-To: <02c201dce227$e808e050$b81aa0f0$@voskuil.org>
On Tue, May 12, 2026 at 11:56:33AM -0400, eric@voskuil.org wrote:
> > AssumeUTXO is a UX improvement for those interested in running a fully
> > validating node. The option to get started in
> > a very limited amount of time [...]
> It's not at all clear to me how this is a UX improvement. Get started doing what?
Getting started validating blocks and transactions at the current tip;
ie receiving payments.
Obtaining the full Bitcoin blockchain currently requires downloading
about 600GB of data. At 250Mbps with perfectly well-behaved peers,
that's a bit under 7 hours. At the consumer level, bandwidth seems to
be the bottleneck, with modern PCs being able to validate the blockchain
in about that time.
AssumeUTXO significantly reduces the download requirement, with
the utxo snapshot at block 935000 being under 9GB. At 100Mbps with
perfectly well-behaved peers, that's about 15m to download. Adding in
another 8GB-34GB of actual block data to download (assuming that the
utxo snapshot people use will be between 4 and 17 weeks out of date)
brings that up to 30 minutes to an hour.
That is, it's something you can leave running over lunch, rather than
overnight.
(Sharing these figures, because up to a few weeks ago, my assumption was
that a fresh IBD over the network from Australia would take multiple days,
and I commonly see people expecting IBD to take a week or more)
Cheers,
aj
--
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/agenaZ5mfhghneYo%40erisian.com.au.
next prev parent reply other threads:[~2026-05-15 23:12 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 [this message]
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-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=agenaZ5mfhghneYo@erisian.com.au \
--to=aj@erisian.com.au \
--cc=bitcoindev@googlegroups.com \
--cc=eric@voskuil.org \
--cc=fjahr@protonmail.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