Thanks to all who made the first Regen Network Dev community call!

Hi all!, Just want to let you know that the planned timing for our first public testnet regen-test-1000 is as follows:
- 2019-06-04 21:00UTC (2pm PDT/5pm EDT/11pm CEST) - Finalize genesis.json and regen-ledger version
- 2019-06-05 18:00UTC (11am PDT/2pm EDT/8pm CEST) - Genesis time

You are welcome to submit a gentx and/or genesis account transaction to https://github.com/regen-network/testnets.

Also, I have been working on a script to airdrop testnet tokens to all Cosmos validators and delegators

Hi all!, Just want to let you know that the planned timing for our first public testnet regen-test-1000 is as follows:
- 2019-06-04 21:00UTC (2pm PDT/5pm EDT/11pm CEST) - Finalize genesis.json and regen-ledger version
- 2019-06-05 18:00UTC (11am PDT/2pm EDT/8pm CEST) - Genesis time

You are welcome to submit a gentx and/or genesis account transaction to https://github.com/regen-network/testnets.

We will airdrop testnet tokens to all validators and delegators in the gaia 13k Cosmos Hub testnet. Additionally feel free to let us know either in our public channel https://t.me/regennetwork_public or in DM and we can make sure to air drop you test net tokens if you are interested in our public test net.

regen-network/testnets
Regen Ledger Testnets. Contribute to regen-network/testnets development by creating an account on GitHub.

Regen Ledger Test Net one will focus on testing a coordinated upgrade module. This is an important feature for improving the coordination and ease upgrading a live chain that does not have breaking changes. We will be practicing governance by enabling modules of Regen Ledger including DAO functionality and data base of ecological state. This will give the community the opportunity to achieve three main goals:

1. Test the coordinated upgrade module and feed back any issues to the cosmos hub and cosmos SDK community
2. Test key Regen Ledger functions built for our application specific goals of a censorship resistant ecological ledger and contracting platform.
3. Coordinate around governance process.

For a look at the upgrade module please see this cosmos SDK pull request:
https://github.com/cosmos/cosmos-sdk/pull/4233

Here is a great tutorial by the CypherCore team on setting up a Regen Ledger Node:
https://www.notion.so/jim380/Regen-Ledger-Node-Set-up-67ede4023f1b45f99724ac52386a1130

And here are instructions for creating the gentx from gaia: https://github.com/cosmos/gaia/blob/master/docs/deploy-testnet.md#create-genesis-file-and-start-the-network. Just replace gaiad with xrnd and as a convention please delegate 1000000tree tokens to the validator in genesis.

The finalized genesis.json and xrnversion.txt for regen-test-1000 have been published to https://github.com/regen-network/testnets/tree/master/latest. The genesis time is tomorrow at 18:00 UTC.

If you have not been included as genesis validator but have received tokens, you can spin up a validator once the network launches. If you haven't received tokens, please PM one of us and we'll send you some

We've gone live with our first public testnet: Regen Test 1001 (more fun testnet names to come next time!) https://medium.com/regen-network/regen-network-testnet-regenesis-1001-a4171849781d

We have a community dev call today at 11am PDT/2pm EDT/8pm CEST.

We will discuss coordinating a planned upgrade using the new upgrade module which will likely involve deploying some of the key group/delegation/delegated fees modules that our winning Hackatom team worked on.

We have our weekly community dev call starting in just a few minutes (https://zoom.us/j/405797939). We will try to make it a short call (30min) today.

Here are a few updates on progress:
* There are still a few blockers for the upgrade. In particular, we are waiting for Cosmos SDK v0.36 (https://github.com/cosmos/cosmos-sdk/milestone/16) to be released and that is the version we will try to upgrade to, hopefully with automated state upgrade scripts. We are also trying to get a few early reviews of https://github.com/cosmos/cosmos-sdk/pull/46 which will be launched as part of the upgrade. Once v0.36 is released we will work towards a new binary that we can test. Apologies for the delay, but we feel it is important to line up with ongoing active Cosmos development rather than rushing things.
* We have opened a draft PR around testnet incentives: https://github.com/regen-network/testnets/pull/14. We still have some more details to flesh out, but we welcome comments either in the PR or on the dev call.
* We are busy expanding our dev team so that we have more bandwidth! We are excited to make more announcements soon! Also, we still have a few roles to fill - in particular a solid frontend person with a good grasp of blockchain. If you think of anyone please let us know.

For reference, the most up to date details on our testnet and instructions for joining can be found here: https://github.com/regen-network/testnets

Our main development on Regen Ledger happens here: https://github.com/regen-network/regen-ledger

And we are also actively participating in the following community groups:
* Cosmos Community Group on Key Management: https://t.me/cosmos_cg_key_management
* CosmWasm (Cosmos Community Group on WebAssembly (WASM) integration): https://t.me/cosmwasm

Ee are having our weekly community dev call in just a few minutes at 11am PT/2pm ET/8pm CET (https://zoom.us/j/405797939). Again, we'll keep it short (under 30min)

A few updates for this week:
- we are still waiting on the Cosmos SDK v0.36 release to do our planned testnet upgrade. It appears that they have hit a snag in simulation testing
- you can track our progress towards doing the testnet upgrade in this milestone: https://github.com/regen-network/regen-ledger/milestone/5
- we have rebased our upgrade module PR against Cosmos SDK master: https://github.com/cosmos/cosmos-sdk/pull/4233
- we are working on an in place upgrade handler for v0.36: https://github.com/regen-network/regen-ledger/issues/61 and trying to test it against a single node network before doing the upgrade
- proposed incentivized testnet points are in this PR if anyone would like to review/comment: https://github.com/regen-network/testnets/pull/14/files

Thanks everyone!

We have our weekly community dev call starting at 11am PT/2pm ET/20:00 CET (https://zoom.us/j/405797939). All are welcome to join!

Regen Network Dev Updates for this week:
- we’d like to welcome Ethan Frey, who was on our Gaians team at Hackatom, as engineering lead starting full-time in August
- we have hired an awesome frontend developer to also start in August, announcement coming soon
- we are getting closer to being able to upgrade our testnet to v0.36.0:
- we identified that migrations on the root multistore need to be performed before the ABCI app starts and opened https://github.com/cosmos/cosmos-sdk/pull/4724 to address this
- we are also working on in-place migrations for the the v0.36.0 genesis migration scripts: https://github.com/regen-network/cosmos-sdk/pull/1
- we have updated Lunie to their latest master: https://regen-network.gitlab.io/lunie

Thanks to all the validators who are participating in the testnet! We welcome ION, Cryptium, Comercio.Network, Chainlayer, and Masternode to the network!

We have our weekly community dev call starting in just a few minutes at 11am PT/2pm ET/20:00 CET (https://zoom.us/j/405797939). All are welcome to join!

Updates for this week:
- we have decided to split our testnet plan into two planned upgrades as opposed to just one, which will let us test something sooner and also use the second upgrade to tune things which were learned in the first
- we will be publishing a blog about the testnet incentive program later today and have updated our point system to include the two upgrades as well as a proportional uptime reward: https://github.com/regen-network/testnets/pull/14/files
- the first upgrade will simply change the PowerReduction variable which has turned our tree token into a "micro-tree" and thus reduced people's ability to stake
- the timing of this upgrade will be discussed on today's call and telegram and could potentially happen as soon as next week
- the second upgrade which we have been working on, will test an in-place upgrade to Cosmos SDK v0.36.0 and will be targeted for sometime in August
- we banged out a quick upgrade manager binary to be tested during the upgrades which could be run as a supervisor binary of xrnd or gaiad: https://github.com/regen-network/cosmos-upgrade-manager
- we are changing our community call time to 10am PT/1pm ET/19:00 CET starting next week to better accommodate people joining from Europe

The testnet incentive README has been merged in now and published: https://github.com/regen-network/testnets/tree/master/regen-test-1001

We are planning to submit a governance proposal for the first upgrade next Monday, 7/29 to change the PowerReduction parameter. There will be four days of voting - from Monday through Thursday. So if you haven't joined the testnet yet, there are still a few days left to be involved in this phase

For those interested in participating in the Regen Network Incentivized Testnet, here are all the details, including links to the KYC/AML process, Regen Test-1001 Tech details and timing information: https://medium.com/regen-network/launching-our-first-incentivized-test-net-13afd321e132

We will be closing this poll in 30 minutes right before our community dev call. Please vote if you haven't and have an opinion

Just a reminder that we are having our community dev call in just a few minutes at 10am PT/1pm ET/19:00 CET (https://zoom.us/j/405797939). That's one hour earlier than before to better acommodate Europe.

Welcome to all the new validators on our testnet! So excited to have so many people on board!

Here is the the official timeline for testnet events to the best of our current knowledge, keeping in mind that some of these are related to all of your participation in governance and running of the network:
- at the end of the community dev call today, we will submit a governance proposal for our first planned upgrade code-named el-choco in honor of the Tumbes-Choco-Magdalena bio-region (https://en.wikipedia.org/wiki/Tumbes-Choc%C3%B3-Magdalena). We will name each upgrade and testnet after a bio-region.
- we will also publish the git release which contain the el-choco upgrade for community review today
- there will be four days of voting once voting begins later today. We will publish the exact voting deadline once the voting period begins as well as the CLI command to use to vote
- assuming the governance proposal passes, the upgrade will take place at the time specified in the proposal (most likely 8/5 or 8/6 at 15:00 UTC). This means that your current v0.4 binary will stop working once we reach this upgrade time and you will need to replace this binary with the new binary that contains the el-choco upgrade as soon as possible. We will publish more details on how to do that later this week

The PR for the proposed el-choco testnet upgrade is here for community review: https://github.com/regen-network/regen-ledger/issues/65. This changes the PowerReduction from 1e6 to 1e2 giving all validators 10,000 times more voting power

The gov proposal for the el-choco upgrade is now live with proposal ID 1! Based on the poll results this proposal is for an upgrade on Tue, Aug 6th at 8am PT/11am ET/15:00 UTC/17:00 CEST/00:00 KST.

To vote yes on this proposal the command is xrncli tx gov vote 1 yes --from mykey (you can also substitute yes for no, abstain or no_with_veto if you have a different opinion). You have until 2019-08-03T17:40:15.34929258Z to vote - that's 17:40 UTC on Sat, 8/3.

If this proposal passes, your current v0.4 xrnd binary will stop validating blocks at the time proposed above and every validator will be responsible for starting the new binary with the el-choco upgrade as soon as possible.

The current point system awards up to 200 points for doing this upgrade with 1 point subtracted for every block missed. The idea is not to penalize people for being slow with the upgrade but to incentivize people to figure out the quickest setup for getting their node back up and running with the new binary.

Also, if this upgrade proposal passes we will have our next community call at 7:30am PT/10:30am ET/14:30 UTC/16:30 CEST/23:30 KST - half an hour before the upgrade so that we can all do this upgrade together live and support everyone through the process.

As always we welcome everyone's questions. Thanks all!