Tgrade Public Testnet : The dry run

Martin Worner
TgradeFinance
Published in
2 min readApr 11, 2022
Photo by Jeffrey F Lin on Unsplash

We have run a series of testnets, from the highly successful Testnet-3 which was supported by nearly 400 validators, building on Testnet-3 we had patchnet which fixed the issue with swapping between digital assets, fixed a number of UX issues, and introduced a much more robust QA system to ensure quality. We also tried a chain upgrade with a new binary. We snuck in spotnetto test a network launch with 3 external validators to test our processes.

We are now getting ready for the final Testnet

Goals for the final testnet: dryrunnet

Given the success of our testnets, we are building on this and have a targeted set of goals for the final testnet as a rehearsal for the mainnet launch where we test the processes and the final functionality that the team has been completing.

  • Start the chain with as many validators from our Genesis validator set as possible.
  • We test the range of Oversight Community Tools.
  • We test the validator voting on the proposals through the dashboard.
  • Test the distribution of rewards based on Engagement Points

What steps the validators need to take

We are starting dryrunnetwith the genesis validator set. The validators will have received an email outlining what we need in order to generate the genesis file.

Once the chain is launched, then non-genesis validators may join but must be aware that:

  • This is not an incentivized testnet
  • The validator cap is set to 100 for this testnet

The instructions for joining the final testnet will be published once the dryrunnethas been launched by our genesis validator set.

When are we launching dryrunnet?

The collection of the genesis validator information will be done by 24:00 UTC on 12th April and we aim to launch the dryrunnetwith the genesis validators at 15:00 UTC on Wednesday 13th April.

How long will the final testnet run?

It is envisaged thatdryrunnet is a short-lived testnet and will finish at the end of April, or latest early May. We will then enter the final phase of bug fixing and preparation before themainnetlaunch.

--

--