From: vjudeu@gazeta•pl
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] One testnet to rule them all
Date: Fri, 04 Mar 2022 21:46:04 +0100 [thread overview]
Message-ID: <158234619-439597ed4ddc4a9f90ea573513b5f5a3@pmq4v.m5r2.onet> (raw)
In testnet3, anyone can become a miner, it is possible to even mine a block on some CPU, because the difficulty can drop to one. In signet, we create some challenge, for example 1-of-2 multisig, that can restrict who can mine, so that chain can be "unreliably reliable". Then, my question is: why signets are introducing new coins out of thin air, instead of forming two-way peg-in between testnet3 and signet?
The lack of coins is not a bug, it is a feature. We have more halvings in testnet3 than in mainnet or signets, but it can be good, we can use this to see, what can happen with a chain after many halvings. Also, in testnet3 there is no need to have any coins if we are mining. Miners can create, move and destroy zero satoshis. They can also extend the precision of the coins, so a single coin in testnet3 can be represented as a thousand of coins in some signet sidechain.
Recently, there are some discussions regarding sidechains. Before they will become a real thing, running on mainnet, they should be tested. Nowadays, a popular way of testing new features is creating a new signet with new rules. But the question still remains: why we need new coins, created out of thin air? And even when some signet wants to do that, then why it is not pegged into testnet3? Then it would have as much chainwork protection as testnet3!
It seems that testnet3 is good enough to represent the main chain during sidechain testing. It is permissionless and open, anyone can start mining sidechain blocks, anyone with a CPU can be lucky and find a block with the minimal difficulty. Also, because of blockstorms and regular chain reorgs, some extreme scenarios, like stealing all coins from some sidechain, can be tested in a public way, because that "unfriendly and unstable" environment can be used to test stronger attacks than in a typical chain.
Putting that proposal into practice can be simple and require just creating one Taproot address per signet in testnet3. Then, it is possible to create one testnet transaction (every three months) that would move coins to and from testnet3, so the same coins could travel between many signets. New signets can be pegged in with 1:1 ratio, existing signets can be transformed into signet sidechains (the signet miners rule that chains, so they can enforce any transition rules they need).
next reply other threads:[~2022-03-04 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 20:46 vjudeu [this message]
2022-03-05 16:19 ` Jeremy Rubin
2022-03-05 18:17 ` vjudeu
2022-03-05 23:40 ` Jeremy Rubin
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=158234619-439597ed4ddc4a9f90ea573513b5f5a3@pmq4v.m5r2.onet \
--to=vjudeu@gazeta$(echo .)pl \
--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