From: "Jorge Timón" <jtimon@jtimon•cc>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Introduce N testnet chains to test different block sizes
Date: Mon, 6 Jul 2015 18:50:37 +0200 [thread overview]
Message-ID: <CABm2gDocHGNiRtxci+bdp_QXo4iD7Z1HbW5s=4rFKj79Q8XGyg@mail.gmail.com> (raw)
I have created the following PR that simplifies testing of different
block sizes and (if it were merged) would also slightly simplify a
future block size change hardfork.
https://github.com/bitcoin/bitcoin/pull/6382
I hope someone finds this useful. Please, post to github if you find
any issues. But, please, don't discuss the block size issue itself in
this post or the PR, the size is simply -blocksize.
I repeat the text here:
It would be generally good to have more people collecting data and
conduction simulations related to different consensus maximum block sizes.
This PR attempts to simplify that work.
Even if it may take long until it is merged (because it requires many
little steps to be taken first), this branch (or a fork of it) can be
used right now for
testing purposes.
One can use it, for example, like this: ```./src/qt/bitcoin-qt
-chain=sizetest -debug -printtoconsole -gen=1 -genproclimit=20
-blocksize=2000000```
I will rebase and update the list of dependencies accordingly as
things get merged.
Dependencies:
- Chainparams: Translations: DRY: options and error strings #6235
- CTestNetParams and CRegTestParams extend directly from CChainParams #6381
next reply other threads:[~2015-07-06 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 16:50 Jorge Timón [this message]
2015-08-19 18:30 ` Jorge Timón
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='CABm2gDocHGNiRtxci+bdp_QXo4iD7Z1HbW5s=4rFKj79Q8XGyg@mail.gmail.com' \
--to=jtimon@jtimon$(echo .)cc \
--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