New testnet with 5.0 support launched (old one is abandoned). Please use new client with clean db folder and default peers:
It has auto-voting for 5.0 soft-fork by default, starting from height 4,096. In this testnet, average delay between blocks is 5 seconds just. 5.0 activation is expected @ height 12,289
Please note, from this release the node has 9021 port for p2p interactions for the testnet by default (before, it was 9020). Magic network bytes also changed. Testnet relaunched with this release.
The following consensus-critical settings have been changed:
ergo.chain.protocolVersion = 3 - with this setting, a node will vote for a soft-fork and use 5.0 soft-fork code (JIT costing etc) after voting and since activation. Node users should not set value for this setting manually, and so should use default value provided by developers
ergo.chain.blockInterval = 5s - new testnet has 5 sec delay between blocks on average
ergo.chain.monetary.minerRewardDelay = 720 - now there’s no difference in mining fee scripts between mainnet and testnet (previously, scripts were different as testnet had 72 blocks lock, now both mainnet and testnet use 720)
And for non consensus critical changes, the following default values set:
ergo.chain.reemission.checkReemissionRules = false - no EIP-27 data set for the new testnet (yet)
The following setting means voting for soft-fork(5.0 soft-fork in this case), if node’s supported protocol version is above network’s
ergo.voting = { 120 = 1 }
To make voting started at the same time, additional hard-coded filter starting voting from height 4,096 only. Similar thing will be done in the mainnet.
And magic bytes now set to [2,0,0,3] to avoid peers from previous testnet to join