From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Sun, 24 May 2026 11:29:26 -0700 Received: from mail-oi1-f191.google.com ([209.85.167.191]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wRDZl-0003Cb-BE for bitcoindev@gnusha.org; Sun, 24 May 2026 11:29:26 -0700 Received: by mail-oi1-f191.google.com with SMTP id 5614622812f47-482dd33c4e2sf15824124b6e.2 for ; Sun, 24 May 2026 11:29:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1779647359; x=1780252159; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=LlS6A6UVs/0bkkT2VwEjYMU/4medNliIb1iIRb0ePmE=; b=R+tFeYQOA6xJ6FQkh4mr1M1yrrgN9drXCAD4RQFvzWefESL4xBQtTMJpYx2O4m99qh Uh67FIE/jw0F8vXMmzYDkTRWojgfkuLuHIGZrU26dwIIdw7Xicl5V1jRwa17nS0FAtO+ ho4nc9ljyHFmYSZreSNmU6RqP+j0Aie8/nfcoHd5A/H9EIMUFM4A1rI9GxVszdzINNih oF9JbfFX7w0dgguZXGppgMHx7HB5iz0Xe5SHGqR0v9Tp2fEVTlIDJ4jgzxyqCRTYFxDQ 3UzGG6NrFSbvdaplDM3v2LICw9Gj0B+hj8Mz9rcT1xR4sv/3TZGm5qHKHBGwLLNoGtJI EVfg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=voskuil.org; s=google; t=1779647359; x=1780252159; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=LlS6A6UVs/0bkkT2VwEjYMU/4medNliIb1iIRb0ePmE=; b=PjRDD1ZbHa4GidkqD7JC8kfMT7IbYs6Mg560N0kFTRFW3s3Pu0keLE9FdQIPl11zeM 9d+cUwEXD7HQ6acZAyx4dpKF7nmOr3VeIMhw6uWPpvJOfznIFITRl0vzLk40PtmouZQk 1Gtp/eDs1G2oDBDWavFO7UBAutmNOORH+5zkbMGIK0MWmzLI+YSRrAKrUl4dzbGSjjxH ulhay4/gtvj/aRBXXXHshmqX9icoMK1n+a/fdaM18MnwTzBRrQ2r6iNeN0HGezmnbNaR HJ8v1J2G/rI24gIgox3TrGMGFnOxIUVLb14vlWtvDV6i/E2aPoXakTIhV3XoR1pbDgxv tl3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1779647359; x=1780252159; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=LlS6A6UVs/0bkkT2VwEjYMU/4medNliIb1iIRb0ePmE=; b=cdTSe9+60YX/Q4pYC8WugI9kmW2AwHJDVtA2quB53exlpQNvns5cuZqNdJZ05p0qOS 46FsQBBKhwxhBqQD6wKbcwT7Qk8ei4tcs7Fea05JzvcjntDJH2whkroR3TJvBWK7hfHy +gm7sMmhMvcf7m7+RsNp0YVg2wWkjw2o639aqk+1+pokalbI0EbuJfAgWhwz4n7IipeZ F1/9+lgJVmawiBQKZ/V476sNd6pRUM3fPHxlh78zfpwTrOsUNs8ukri6qonB/miGEyDS IVi5eUWLVj4Qs0d6kt+3IAVwtBo9gzCcrgts4/BC3ixibU0DoDUFvxMsCZOhyMQxjZmv 90fA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AFNElJ+IvYS3DwgyF1IaF0yRQPazBCSXtRiMymq5P3fxkLrwsnTAYjxPVOo0Fnq2tMbK+OIUzonvOZhqZyfe@gnusha.org X-Gm-Message-State: AOJu0YzrWDE3IA3WpcVejtfGvwDvQwamHC8PjdprY2hco8xhY2kOOEbg I02hGtRPi5ORw/JFs4IJ9eFn+omkKGnFPy70sMvgTm+JGArf/1fkR5Gp X-Received: by 2002:a05:6808:6d91:b0:482:6617:d48c with SMTP id 5614622812f47-4854a3fa3ecmr6556058b6e.25.1779647358805; Sun, 24 May 2026 11:29:18 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="AUV6zMPFlef8DIlqiqbugkCF05EZNOw00s2Nf+pbF1CPd+8iWA==" Received: by 2002:a05:6870:c088:b0:42f:eb75:2e78 with SMTP id 586e51a60fabf-43a01f61cc8ls4870054fac.2.-pod-prod-06-us; Sun, 24 May 2026 11:29:11 -0700 (PDT) X-Received: by 2002:a05:6808:1827:b0:47c:3f6f:db9a with SMTP id 5614622812f47-4854a0deb0dmr7933645b6e.15.1779647351723; Sun, 24 May 2026 11:29:11 -0700 (PDT) Received: by 2002:a05:690c:a081:20b0:7ba:f1b3:9504 with SMTP id 00721157ae682-7d36931b84cms7b3; Sun, 24 May 2026 08:53:29 -0700 (PDT) X-Received: by 2002:a05:690c:260f:b0:7b4:b591:e79a with SMTP id 00721157ae682-7d335fc0391mr117282797b3.14.1779638006421; Sun, 24 May 2026 08:53:26 -0700 (PDT) Date: Sun, 24 May 2026 08:53:25 -0700 (PDT) From: Eric Voskuil To: Bitcoin Development Mailing List Message-Id: <929d44f7-42d8-4670-8cf6-d01d44c36c2en@googlegroups.com> In-Reply-To: References: <19616822-8a03-4de1-99be-72d50479208fn@googlegroups.com> <02c201dce227$e808e050$b81aa0f0$@voskuil.org> <002301dce4cf$27bc3040$773490c0$@voskuil.org> Subject: Re: [bitcoindev] Re: [BIP Draft] P2P UTXO Set Sharing MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_402638_360474200.1779638005963" X-Original-Sender: eric@voskuil.org Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.7 (/) ------=_Part_402638_360474200.1779638005963 Content-Type: multipart/alternative; boundary="----=_Part_402639_1142532613.1779638005963" ------=_Part_402639_1142532613.1779638005963 Content-Type: text/plain; charset="UTF-8" Responding to a few earlier comments. > The same applies to the 32 GB RAM minimum noted for libbitcoin... which > already excludes a large share of consumer hardware outside high-income > regions... > Following the trajectory of the last few years to its conclusion, the > minimum is likely to be 64 GB next year, then 128 GB the year after, and > validating with libbitcoin will soon require the latest generation of > Nvidia chips. Validation time will keep going down on that path, but the > user base it serves will keep shrinking. Libbitcoin significantly outperforms bitcoind on a 16GB Raspberry Pi5. https://x.com/evoskuil/status/2058574669708443756 All it takes is changing the config settings that target larger machines. Despite 16 years of optimization and money poured into bitcoind, and its various clones and ports, it underperforms on both modest and high end hardware. We are a small team of volunteers, just getting started on performance tuning and optimization. > I am obviously exaggerating somewhat to make a point: You aren't just exaggerating, you sound delusional. > it is easy to construct a plausible-sounding slippery slope argument, "plausible-sounding" is one way to put it, and yet the truth of it was clearly demonstrated 13 days after you dismissed it. > including one about libbitcoin's hardware trajectory. And I don't think > you are able to prove today that libbitcoin will not follow this path in the > future. That is exactly why I don't find your similar argument persuasive. Well it only took me 13 days for the stunning arrival of the very scenario you denied. And the hardware fantasy that you fabricated to make this point actually applies to bitcoind architectures, not Libbitcoin. I would call that unpersuasive. > And in all seriousness, I think at least some Bitcoin implementations should > aim to be accessible with low bandwidth and minimum hardware requirements > compatible with widely available consumer hardware outside high-income regions. > That is what many of the developers I work with are aiming for. No, that is what we are doing. What you are doing here is called snake oil. My suggestion is you roll the clock back a decade and do the work that needed to be done in order to avoid this predicted outcome. 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/929d44f7-42d8-4670-8cf6-d01d44c36c2en%40googlegroups.com. ------=_Part_402639_1142532613.1779638005963 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Responding to a few earlier comments.

> The same applies to t= he 32 GB RAM minimum noted for libbitcoin... which
> already exclud= es a large share of consumer hardware outside high-income
> regions= ...
> Following the trajectory of the last few years to its conclus= ion, the
> minimum is likely to be 64 GB next year, then 128 GB the= year after, and
> validating with libbitcoin will soon require the= latest generation of
> Nvidia chips. Validation time will keep goi= ng down on that path, but the
> user base it serves will keep shrin= king.

Libbitcoin significantly outperforms bitcoind on a 16GB Ra= spberry Pi5.

https://x.com/evoskuil/status/2058574669708443756
All it takes is changing the config settings that target larger m= achines. Despite 16 years of optimization and money poured into bitcoind, a= nd its various clones and ports, it underperforms on both modest and high e= nd hardware. We are a small team of volunteers, just getting started on per= formance tuning and optimization.

> I am obviously exaggerati= ng somewhat to make a point:

You aren't just exaggerating, you s= ound delusional.

> it is easy to construct a plausible-soundi= ng slippery slope argument,

"plausible-sounding" is one way to p= ut it, and yet the truth of it was clearly demonstrated 13 days after you d= ismissed it.

> including one about libbitcoin's hardware traj= ectory. And I don't think
> you are able to prove today that libbit= coin will not follow this path in the
> future. That is exactly why= I don't find your similar argument persuasive.

Well it only too= k me 13 days for the stunning arrival of the very scenario you denied. And = the hardware fantasy that you fabricated to make this point actually applie= s to bitcoind architectures, not Libbitcoin. I would call that unpersuasive= .

> And in all seriousness, I think at least some Bitcoin imp= lementations should
> aim to be accessible with low bandwidth and m= inimum hardware requirements
> compatible with widely available con= sumer hardware outside high-income regions.
> That is what many of = the developers I work with are aiming for.

No, that is what we a= re doing. What you are doing here is called snake oil. My suggestion is you= roll the clock back a decade and do the work that needed to be done in ord= er to avoid this predicted outcome.

e

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/929d44f7-42d8-4670-8cf6-d01d44c36c2en%40googlegroups.com.
------=_Part_402639_1142532613.1779638005963-- ------=_Part_402638_360474200.1779638005963--