From: Emil Engler <me@emilengler•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] [BIP-able idea] Regular testnet reset
Date: Sat, 14 Sep 2019 01:57:12 +0200 [thread overview]
Message-ID: <5194d5a8-66f6-9be2-d44a-3bee98d1bbd5@emilengler.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
Hello, I'm thinking about writing a BIP about resetting the testnet on
regular/scheduled basis
The idea works like this:
* Every 210000 block is being used as the genesis of a completely new chain.
* The old one gets forgotten
* No chain can be longer than 210000 blocks
The problems are:
* How to get this working with testnet3? Only a hardfork probably.
* Is it that easy to change the chain while Bitcoin Core is running?
Probably the blocks need to be appended to the cureent one. After a
restart it would get patched
* Could the the chain derive into multiple once at every reset? (Planned
attacks)
What do you think about the idea?
Greetings,
Emil Engler
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3199 bytes --]
next reply other threads:[~2019-09-13 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 23:57 Emil Engler [this message]
2019-09-15 13:49 ` Bryan Bishop
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=5194d5a8-66f6-9be2-d44a-3bee98d1bbd5@emilengler.com \
--to=me@emilengler$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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