public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Anthony Towns <aj@erisian.com.au>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] Testnet 5 launch
Date: Tue, 10 Nov 2026 04:14:54 +1000	[thread overview]
Message-ID: <avINnoG-1r242rAw@erisian.com.au> (raw)

Hello world,

I propose mining testnet 5's genesis block at the end of the week,
aligned with the next mainnet retarget at block 975,744.

If people want to point hashrate at bootstrapping testnet5, I've got
some docs on the process available at:

  https://gist.github.com/ajtowns/ebb148819c6028387271e6f0dce5e1da

and the 0%-fee solo-mining pool to point to is available at:

  https://lapis.erisian.com.au/chain.html

It will keep running tests at lower difficulty for the rest of the week
until shortly before block 975,744 is mined.



Couple of extra bits of info:

This setup involves a couple of tweaks to the genesis block structure,
documented in https://github.com/bitcoin/bips/pull/2347 . These are to
make pooled mining of the genesis block easier (providing extranonce
space and expicitly allowing nVersion rolling), and also to make it a
bit closer to previous genesis blocks (having the commitment be text in
the pszTimestamp field rather than the output, and making the output an
unspendable OP_RETURN rather than a potentially-post-quantum spendable
x-point).

When bootstrapping a new chain, the ambiguity in how BIP 34 block height's
are encoded tends to bite: bitcoin core expects blocks 1 to 16 to use
OP_1 to OP_16 in the coinbase, but a lot of mining software expects to
see a one-byte push, so 0x0101 to 0x0110, so if you see weird behaviour
at low height blocks, this might be a cause. References:

  * https://github.com/bitcoin/bips/pull/2342
  * https://github.com/bitaxeorg/ESP-Miner/pull/2089

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/avINnoG-1r242rAw%40erisian.com.au.


                 reply	other threads:[~2026-11-09 18:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=avINnoG-1r242rAw@erisian.com.au \
    --to=aj@erisian.com.au \
    --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