From: Garlo Nicon <garlonicon@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Unbreaking testnet4
Date: Mon, 24 Mar 2025 00:00:09 -0700 (PDT) [thread overview]
Message-ID: <85db9980-f6c9-48d8-a650-c69f16cd835fn@googlegroups.com> (raw)
In-Reply-To: <5c13e130-aaa2-4866-be26-7498100e868b@murch.one>
[-- Attachment #1.1: Type: text/plain, Size: 1877 bytes --]
> The given rationale for a difficulty reset was to let developers
occasionally mine blocks on their laptop.
It is technically possible to allow CPU users to get some coins, if they
provide some Proof of Work.
Example Script: "OP_SIZE 60 OP_LESSTHAN OP_VERIFY
0279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798
OP_CHECKSIG".
Related topic:
https://delvingbitcoin.org/t/proof-of-work-based-signet-faucet/937
And because this method is network-independent, and can be deployed
anywhere (all testnets, mainnet, signet, regtest, doesn't matter), then it
is probably a good idea to disable 20 minute rule, that way or another.
poniedziałek, 24 marca 2025 o 02:29:17 UTC+1 Murch napisał(a):
> 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/85db9980-f6c9-48d8-a650-c69f16cd835fn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2428 bytes --]
next prev parent reply other threads:[~2025-03-24 13:56 UTC|newest]
Thread overview: 14+ 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 [this message]
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
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=85db9980-f6c9-48d8-a650-c69f16cd835fn@googlegroups.com \
--to=garlonicon@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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