From: Ali Sherief <ali@notatether.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: Testnet 4 difficulty/hashrate
Date: Sat, 25 Jul 2026 11:23:02 -0700 (PDT) [thread overview]
Message-ID: <3d57026c-7998-468b-ab72-b57cc2e971f2n@googlegroups.com> (raw)
In-Reply-To: <aiKeSdrUDP8N1Xww@erisian.com.au>
[-- Attachment #1.1: Type: text/plain, Size: 2702 bytes --]
This is having consequences in development workflows. Tests with
bitcoin-related libraries with this kind of block generation is now almost
impossible unless you mine your old blocks. For instance, my testnet4
faucet transactions have been sitting in the almost-empty mempool for
around 30-60 minutes, never confirm, and then drop out.
It is certainly making developing Bitcoin-related stuff much harder
-Ali
On Friday, June 5, 2026 at 1:28:01 PM UTC+3 Anthony Towns wrote:
> On Fri, Jun 05, 2026 at 07:35:27PM +1000, Anthony Towns wrote:
> > compared with current mainnet difficulty of ~138T, or testnet4's
> > current difficulty of ~1239M,
>
> If testnet4's current difficulty is D=1239M [0], and there were
> no min-difficulty blocks, that would be one thing. But there are
> min-difficulty blocks, and sufficient hashrate mining them with the clock
> set forward to saturate them. What's the actual hashrate for testnet4
> given a reported difficulty D?
>
> [0]
> https://mempool.space/testnet4/block/000000000000000359f805aea2a5f18671bf98a1106d0cdbbfbe1f341f5e08dc?showDetails=true&view=actual#details
>
> Suppose the "correct" difficulty corresponding with actual hashrate would
> be H. Then real difficulty blocks are found every (D/H * 10 minutes)
> on average, and minimum time blocks fill up the rest of the retarget
> period. So between blocks 135072 and 137087, I see 192 real-difficulty
> blocks and 1824 min-difficulty blocks, suggesting that the real testnet4
> difficulty should be H=130M.
>
> The limit on not having D/H=2016 is that with 2016 min-difficulty blocks,
> you'd have a retarget period taking up 4 weeks instead of 2 weeks. I think
> a real-difficulty block can reset up to 5 or 6 blocks of min-difficulty
> time (any more than that would violate median time constraints on behalf
> of the real difficulty block, or too-far-in-future constraints on the
> min-difficulty blocks), so I think that means that you want at least
> 1 real block for every 10 or 12 min-difficulty blocks, so a 192:1824
> (1:9.5) ratio seems close to the max already.
>
> This also suggests ~90% of testnet4 blocks are being confirmed via
> competition in network propagation with only ~10% confirmed via
> PoW/hashrate competition.
>
> 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/3d57026c-7998-468b-ab72-b57cc2e971f2n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3801 bytes --]
prev parent reply other threads:[~2026-07-25 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 10:00 [bitcoindev] Testnet 4 difficulty/hashrate Anthony Towns
2026-07-25 18:23 ` Ali Sherief [this message]
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=3d57026c-7998-468b-ab72-b57cc2e971f2n@googlegroups.com \
--to=ali@notatether.com \
--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