A few weeks ago we announced and executed an RSK Testnet reset, upgrading all RSK nodes to client version Bamboo v0.3.0. We’ll be undergoing a new Testnet reset in a few days, to move one step closer to our upcoming beta mainnet release.
What does a Testnet reset mean?
A reset is a fresh start of the blockchain. All servers provided by RSK will be restarted and upgraded to a new RSK client version. Hashing power will point to the new network. Existing accounts and contracts will not be migrated. Consensus rules for the new chain will not be compatible with those of the old chain.
When will Testnet reset will take place?
We will start working on the Testnet reset on Tuesday, January 2nd 2018, 11:00 PM (GMT). We cannot guarantee RSK Testnet nodes to be available after that time. RSK new client release will be published in our Github page once Testnet reset is complete.
What can you do if you need to keep working on your already deployed smart contracts?
If you need to continue working on your current Ginger node, preserving the state of smart contracts and accounts, you can have your node run in standalone mode. This means it will not be part of a broader network. You can find instructions on how to do this by following the steps described here.
However, it’s highly recommended that you deploy your contracts on the new Testnet once it becomes available, so you can check they work properly on the new version of the RSK client.
What’s new in the upcoming release?
A non-comprehensive list of changes to be included in the upcoming version is:
- EIP #658 implemented
- New EVM opcodes included in RSK virtual machine (returndatasize, returndatacopy)
- Bridge native contract new features
- Several security improvements
- Bug fixes
More details will be published at the time of release.
If you have any questions or concerns please contact us directly in our RSK Gitter community. Thanks for your comprehension and for your continued support to the RSK platform!