We're going to cancel today's validator update call and start again in 2 weeks.

We can do a testnet post-mortem then and will have the results compiled in advance of the call.

Please come with your feedback ready and thank you again for participating 🌞🌱

The post mortum and results from the Algradigon - 1 Testnet are here! https://medium.com/regen-network/postmortem-of-algradigon-1-eb2dc7652850

Hello Regen Validators,
Thanks for waiting. Here is the testnet news!

Regen Network's next incentivized Cosmwasm Kontraŭa Testnet is coming.

We will be using cosmwasm release from here: https://github.com/regen-network/wasmd/releases/tag/v0.7.1

For more details about the testnet program please check our blog post here: https://medium.com/@gregorylandua/cosmwasm-kontra%C5%ADa-testnet-plan-2756490ccdf4

Currently gentx submissions are active. You can submit your gentx to be part of the testnet from genesis by following the instructions here: https://github.com/regen-network/testnets/blob/master/kontraua/README.md

Genesis time is scheduled at : 13th March, 2020. Gentx submissions will close on: 12th March, 0900UTC. Hurry up. There's a bonus for early gentx submissions too

Wow!!!
We have received a massive total of 62 gentx submissions and all valid 🥳🚀🚀.

We are excited to announce that the genesis has been finalized with 62 validators at genesis block. You can download the genesis file from here:
https://raw.githubusercontent.com/regen-network/testnets/master/kontraua/genesis.json

Instructions to setup your node are available here: https://github.com/regen-network/testnets/blob/master/kontraua/README.md#genesis--seeds

Congratulations to all the validators who made it the genesis. Cheers!!!

Note: There was 1 validator who submitted the gentx after 0900UTC, which is not part of the genesis. Those who missed, remember you can always join the network after the genesis time.

Here's the Kontraua explorer -

https://explorer.regen.vitwit.com/

=== KONTRAUA TESTNET ANNOUNCEMENT ===

Dear Regenerates,

Following the chaotic start to the Kontraua testnet, and debugging of the issues that have taken place, the Community Lead Validators team wanted to release a short update on the events that have taken place so far:

- At genesis time, the advertised seed nodes failed to come online; this was found to be a build issue leading to a missing library. This is in the process of being rectified.
- Peers were shared by the community, but operators not online for genesis were unable to update their config in time.
- The downtime slashing/jailing window was too short; the genesis file contained the default cosmos-sdk values, which only permit 50 blocks on downtime, so this combined with the above caused the jailing of 13 validators.
- Unjailing transactions failed - due to the 10 minute period between being jailed and being able to unjail, enforced by the cosmos-sdk - however, a bug present in the cosmos-sdk appears lead to the error message not being handled properly, causing concern that unjailings were not possible.
- An existing issue with declaration of seed nodes in config.toml is not yet resolved, so potentially further impacted validators trying to recover.

Given the combination of events listed, the Regen Lead Validators team have decided that we will continue the running of the Kontraua testnet, however, tracking of validator uptime will not start until block 15000, at approximately 16:15 UTC on Saturday 14th March 2020. Thats give everyone around 23h to unjail and get nodes online and signing.

Similarly, jail and slash events incurred *before block 15000*, will not impact the rewards earned by validators during this testnet.

The software-related issues above are being raised with the relevant upstream teams, but at present these are not deemed to be significantly affecting the running of the testnet. This is the nature of running bleeding-edge software, it is absolutely not risk-free!

We apologise for the uncharacteristically bumpy genesis, and as always, we appreciate your continued support, and wish you all the very best for the upcoming challenges.

Kindest regards,

Joe, Chris and Anil - Regen Lead Validators team

Phase-2 challenge updates:

Instructions will be out today at 1600UTC. The challenge starts on 16th March, at 0500UTC. Everyone will have 24 hours to participate and submit their details (deadline is at 0500UTC, 17th March).

Note: Those who are interested can try out the official cosmwasm docs meanwhile to deploy and execute transactions.

Dear all,

In light of recent global events, and continued disruption to business-as-usual, combined with the less time-critical nature of deploying a contract in a real-world scenario, we have decided to relax the timings of the Phase 2 challenge of the Kontraua testnet. The new deadline will be 0500UTC on Thursday 19th March, giving a 72 hours window for completion of the task.

It is important to note that despite appearances, this is not a coding challenge, but rather deployment of contracts and does not require writing new code. As previously, the documentation relating to this phase will be release in approximately three hours, at 1600UTC today.

Regards,

Regen Lead Validator team

Dear all,

Here are the instructions for Phase-2 challenge.
https://github.com/regen-network/testnets/blob/master/kontraua/challenges/phase-2/instructions.md

The challenge will start tomorrow at 0500UTC.

Dear all,

Here are the updates on Phase-3:
This phase is about upgrading existing binary to a new version:v0.7.2. It will have following updates:
- Increase slashing params signed_blocks_window to 1000 blocks (it is 100 now)
- Update regen-network/wasmd to use coswasm/wasmd@0.7.1 (https://github.com/CosmWasm/wasmd/releases/tag/v0.7.1)

Ameliorate network (High-noon upgrade) 26th March, 1200UTC
Upgrade Name: Himalaya
Upgrade proposal : 23rd March, ~1300 UTC
Binary release - 23rd March, ~1800 UTC
Voting Period : 23rd - 25th March (Relative to proposal time)
Upgrade time: 26th March, 1200UTC

Note: Validators are expected to vote on the proposal, upgrade their nodes and update validator signing-info. Upgrade instructions will be shared on 24th March, 1200UTC (tomorrow)

Attention everyone

A new software upgrade proposal is created 🚀, https://regen-lcd.vitwit.com/gov/proposals/1 and is currently in Voting Period.

Proposal ID: 1
Proposal Title: Himalaya
Proposed Time: 2020-03-23,13:03:27 UTC
Total Deposit: 10TREE
Current Status: Voting Period
Voting Period End Time: 2020-03-25 13:12:02 UTC


What's next?
All the validators are expected to cast their vote before Voting period end time. You can use following command to vote for the proposal.

xrncli tx gov vote 1 <option> --chain-id kontraua --node <rpc_end_point> --fees 4000utree -y --from <key>

Gov Proposal has following vote options:
yes
no
abstain
no_with_veto

Dear All,

The new release v0.7.2 is out : https://github.com/regen-network/wasmd/releases/tag/v0.7.2

Here is the guide to upgrade your node : https://github.com/regen-network/testnets/tree/master/kontraua/challenges/phase-3/README.md

Those who tweeted about network upgrade proposal, please raise a PR. The instructions can be found here: https://github.com/regen-network/testnets/tree/master/kontraua/challenges/phase-3#tweet-bonus

Note: Do not run v0.7.2 before 1200 UTC on 26 March. If you do, you will see this error -

BINARY UPDATED BEFORE TRIGGER! UPGRADE "himalaya" - in binary but not executed on chain module=main
panic: BINARY UPDATED BEFORE TRIGGER! UPGRADE "himalaya" - in binary but not executed on chain

And you'll have to downgrade to v0.7.1 until 1200 UTC on 26 March.

Dear Regenerates,
Here is the update for Phase-3.1 i.e., Twilight Drama Upgrade

Context
There could be cases where the planned upgrades might need to be skipped due to issues in updated binary or decision changes after the proposal goes through. Upgrade module allows a way to handle such scenarios with SKIP UPGRADE functionality. This phase focuses on testing SKIP UPGRADE feature from upgrade module.

Schedule
Upgrade proposal time: 30 March, 1411 UTC
Binary release (Dummy release) - 31 March, 1600 UTC
Voting Period : 30, March - 1 Apr, 1417 UTC
Upgrade Height: 288888

Proposal Details
Proposal ID 2
Name twilight-drama
Title Twilight Drama Upgrade
Description Twilight Drama Upgrade Proposal to test SKIP UPGRADE functionality from upgrade module. Expect some drama
Proposal Time 2020-03-30 1411 UTC
Voting Start Time 2020-03-30 1417 UTC
Voting End Time 2020-04-01 1417 UTC
Upgrade Height 288888
Link https://regen-lcd.vitwit.com/gov/proposals/2

Voting for proposal
Use the following command to vote on the proposal.

xrncli tx gov vote 2 yes --chain-id kontraua --node http://<ip>:26657

Though you have yes/no/abstain/no_with_veto options to vote, it is recommended to chose only yes on the proposal as this is not about taking decision on the upgrade features and there won't be any changes on the network after this phase.

Please feel free to reach out in DVD channel in case of any queries.

The proposal currently is in Voting Period state and voting ends on 1st April 1417 UTC (Wednesday).

Instructions about tweet bonus and SKIP UPGRADE will be shared on Wednesday.

Attention Everyone

The upgrade proposal with title "Twilight Drama Upgrade" is Passed (98.61% voted YES) and the upgrade is scheduled for height: 288,888 (https://regen-lcd.vitwit.com/gov/proposals/2)

As stated previously, we are not going to perform this upgrade and use SKIP UPGRADE feature from upgrade module to continue the network with current binary.

What will happen if we don't do SKIP UPGRADE?
The binary will stop at height : 288,888 (nearly at 1300 UTC tomorrow) with consensus failure as it expects twilight-drama upgrade as per the original plan. The network will stop at height 288,888 as there's no binary available for upgrade.

What happens if we SKIP UPGRADE?
The network will continue and there won't be any consensus issues at upgrade height.

What is expected from the Validators?
All the validators should restart their nodes with SKIP UPGRADE flag and continue the network. You can restart your node anytime from now. If you do not restart your node before the upgrade time, your validator will start missing blocks.

Hurry up!!! Here are the instructions to SKIP the scheduled upgrade:
https://github.com/regen-network/testnets/blob/master/kontraua/challenges/phase-3-1/README.md#how-to-skip-upgrade

Note: We are testing SKIP UPGRADE for the first time at a scale, expect chaos 😂

Dear Regenerates,

Gear up for next phase, i.e., Deploying Escrow Contract

Schedule : 7th Apr, 2100UTC (Today) - 9th Apr, 2100UTC (Thursday)
Total Points Allocated for Phase - 4: 100+

Here are the instructions from Phase-4 challenge: https://github.com/regen-network/testnets/blob/master/kontraua/challenges/phase-4/README.md

What is expected from validators?
Upload, Instantiate and execute escrow contract. Submit the details with a PR

Happy Deployment 🚀🚀🚀

Dear Regenerates,

As discussed on the community validators call on Wednesday, in light of the Tendermint vulnerability disclosed yesterday, we have released version 0.7.3 of xrnd here: https://github.com/regen-network/wasmd/releases/tag/v0.7.3

There are no specific deployment instructions for this release, it is completely backwards compatible with v0.7.2 and there is no specific upgrade height, but given the nature of the vulnerability we encourage validators to do upgrade at the earliest opportunity. This xrnd binary is a drop in replacement for the existing binary and contains no functional changes.

Happy validating :)

Note: there is no incentivisation tied to this upgrade procedure.