From: Saint Wenhao <saintwenhao@gmail.com>
To: Antoine Poinsot <darosior@protonmail.com>
Cc: Murch <murch@murch.one>, bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Unbreaking testnet4
Date: Thu, 25 Dec 2025 08:21:00 +0100 [thread overview]
Message-ID: <CACgYNOLc=c5jx8jWGbCczKkLhPNq_+gLNxKi3Tf50-oPQhWuRQ@mail.gmail.com> (raw)
In-Reply-To: <vgcVopNpWCowIGaIpVgjsCWyTMjxVKoWtRdDVnTNrM8tYPjKtC6MJ6S-2KxIYdJYgAhG8iNPig-xijwd7DtAm6tHN3T3xgIMUNUSTBYvT_A=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 4402 bytes --]
> The given rationale for a difficulty reset was to let developers
occasionally mine blocks on their laptop.
This rationale is partially solved by Signet faucets. Miners constantly
sweep coins from signet addresses like
tb1pruektj90gg8nysa7yuk07w7ucwlywrf4p02lq3sz49f05xd00djscyt2fw,
tb1pffsyra2t3nut94yvdae9evz3feg7tel843pfcv76vt5cwewavtesl3gsph, or
tb1pf2v25yk7m8mv203pvjusmk2a8r6tu8p59nhvwux86ck3s3pp0nkqt30dvt.
The only missing thing, is buying a given coinbase transaction, or block,
by a given user. Because now, it is centralized in the hands of signet
creators. However, if it would be possible to pay the same or greater
amount, as set in the coinbase transaction (which now means 25 sBTC or
more) and be rewarded with some block, or coinbase transaction, then it
would pretty much cover it.
Because when it comes to being rewarded, it is covered by the mining
faucet. The only missing part is the control, related to manually
constructing a block. As far as I know, this is the only case, where
testers need to switch from signet to testnet: to test some aspects of
mining.
> I propose to fix this by removing the difficulty reset rule from testnet4
through a flag day hard fork on 2026-01-01.
This date is quite close. Even if we add a week or two, it is quite likely,
that either something will be deployed in the nearest future, or it won't
happen at all, and we will be stuck with what we have.
For now, I switched from testnet4 to signet, but I wonder, how it will turn
out.
Also, using some constructions, based on OP_CAT, or something similar, may
be enough, to mine both at the same time, through Merged Mining. Which
would then mean, that people could try to mine testnet4 blocks, and also
hit signet coins from faucets, with the same power.
pon., 31 mar 2025 o 22:50 'Antoine Poinsot' via Bitcoin Development Mailing
List <bitcoindev@googlegroups.com> napisał(a):
> Good point on not having the flag day on a holiday. One or two weeks
> sounds good to me.
>
>
>
>
> On Monday, March 24th, 2025 at 8:25 AM, Murch <murch@murch.one> wrote:
>
> >
> >
> > Errr, I wrote the same date as you, but I meant a week later, 2026-01-08
> > instead.
> >
> > -Murch
> >
> > On 2025-03-21 14:20, Murch wrote:
> >
> > > Hey Antoine and everyone,
> > >
> > > What you suggest makes sense to me. Since the 20-minute difficulty
> > > exception is now exploited perpetually, it doesn’t serve its intended
> > > purpose of allowing developers to mine themselves a few coins easily or
> > > confirm their own non-standard transactions. In that case, it would be
> > > better to not have it at all.
> > >
> > > On 2025-03-18 07:29, 'Antoine Poinsot' via Bitcoin Development Mailing
> > > List wrote:
> > >
> > > > I propose to fix this by removing the difficulty reset rule from
> > > > testnet4 through a flag day hard fork on 2026-01-01.
> > >
> > > I would suggest to pick a date that’s not a holiday in many places to
> > > avoid disrupting people’s holiday, how about 2026-01-01 instead?
> > >
> > > Cheers,
> > > Murch
> >
> >
> > --
> > 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/7c6800f0-7b77-4aca-a4f9-2506a2410b29%40murch.one
> .
>
> --
> 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/vgcVopNpWCowIGaIpVgjsCWyTMjxVKoWtRdDVnTNrM8tYPjKtC6MJ6S-2KxIYdJYgAhG8iNPig-xijwd7DtAm6tHN3T3xgIMUNUSTBYvT_A%3D%40protonmail.com
> .
>
--
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/CACgYNOLc%3Dc5jx8jWGbCczKkLhPNq_%2BgLNxKi3Tf50-oPQhWuRQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 5802 bytes --]
next prev parent reply other threads:[~2025-12-27 0:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 14:29 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-18 21:34 ` Melvin Carvalho
2025-03-19 7:01 ` [bitcoindev] " Garlo Nicon
2025-03-19 7:56 ` [bitcoindev] " Sjors Provoost
2025-03-19 8:43 ` Garlo Nicon
2025-03-19 8:32 ` Sjors Provoost
2025-03-19 9:11 ` Melvin Carvalho
2025-03-19 17:03 ` bitcoin-dev-ml.void867 via Bitcoin Development Mailing List
2025-03-20 18:58 ` Melvin Carvalho
2025-03-21 21:20 ` Murch
2025-03-24 7:00 ` Garlo Nicon
2025-03-31 7:32 ` Saint Wenhao
2025-03-24 12:25 ` Murch
2025-03-24 13:57 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-04-27 11:44 ` Saint Wenhao
2025-04-27 22:49 ` Jameson Lopp
2025-04-28 6:11 ` Saint Wenhao
2025-04-28 10:45 ` Jameson Lopp
2025-04-28 11:59 ` 'emsit' via Bitcoin Development Mailing List
2025-04-28 12:47 ` Sjors Provoost
2025-04-28 13:33 ` Saint Wenhao
2025-04-28 18:15 ` Saint Wenhao
2025-04-28 18:50 ` Sjors Provoost
[not found] ` <20250428110655.D4A1C7C0AE9@smtp.postman.i2p>
2025-04-28 11:48 ` pithosian
2025-12-25 7:21 ` Saint Wenhao [this message]
2025-05-05 22:25 ` [bitcoindev] " Greg Maxwell
2025-05-06 11:48 ` Saint Wenhao
2025-05-09 13:07 ` Garlo Nicon
2025-05-12 5:21 ` Anthony Towns
2025-05-17 5:11 ` Saint Wenhao
2025-07-05 4:31 ` Garlo Nicon
[not found] ` <20250512110323.B14F27C0B49@smtp.postman.i2p>
2025-05-12 12:05 ` pithosian
2025-05-12 18:17 ` Saint Wenhao
[not found] ` <20250512181809.5705B7C114F@smtp.postman.i2p>
2025-05-12 20:19 ` pithosian
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='CACgYNOLc=c5jx8jWGbCczKkLhPNq_+gLNxKi3Tf50-oPQhWuRQ@mail.gmail.com' \
--to=saintwenhao@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=darosior@protonmail.com \
--cc=murch@murch.one \
/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