Also, this gov proposal is not showing up in Lunie or Big Dipper, likely because it is a different proposal type specifically for software upgrades.

To see proposal status run xrncli query gov proposal 1 and to see votes run xrncli query gov votes 1

We have now tagged the v0.4.1 release of regen-ledger for the el-choco upgrade: https://github.com/regen-network/regen-ledger/releases/tag/v0.4.1. Linux binaries are now being built via Gitlab CI and can be downloaded directly from Gitlab here: https://gitlab.com/regen-network/regen-ledger/pipelines.

Most validators have voted on the upgrade proposal but many haven't. If you haven't voted yet you have a little more than a day left. Voting will close at 2019-08-03T17:40:15.34929258Z .

We have published the following faucet terms of appropriate use: https://github.com/regen-network/testnets/tree/master/regen-test-1001#faucet-terms-of-use. We see that the terms were not explicitly clear and that there is a need to have this clarity in order to maintain the health of the testnet for all. Please review these terms and abide by them if you would like to receive testnet rewards. Thank you

The software upgrade proposal passed over the weekend and the el-choco upgrade will happen tomorrow, Aug 6th at 15:00 UTC - that's 8am PT/11am ET/17:00 CEST/00:00 KST.

Please see this guide for details on how to perform the upgrade including instructions for setting up an automated script: https://medium.com/@ethan.frey/el-choco-upgrade-guide-65a74b469ad0

We will have our community dev call (https://zoom.us/j/405797939) tomorrow half an hour before the upgrade at 7:30am PT/10:30am ET/14:30 UTC/16:30 CEST/23:30 KST so that we can do the upgrade together. (Please ignore any other meeting invites to the contrary! There have been some weird calendar snafus)

In less than two hours at 15:00 UTC (8am PT/11am ET/17:00 CEST/00:00 KST) regen-test-1001 will halt for the el-choco upgrade

Please prepare your nodes if you haven't done so yet following this upgrade guide which explains how to setup an automated upgrade script: https://medium.com/@ethan.frey/el-choco-upgrade-guide-65a74b469ad0

In an hour and a half at 7:30am PT/10:30am ET/14:30 UTC/16:30 CEST/23:30 KST we will meet for our community dev call (https://zoom.us/j/405797939) so we can answer any questions preparing for the upgrade and troubleshoot any issues that arise

We're excited to test this functionality with a large group of validators! Thank you all who are participating

Community dev call starting now to debrief on last week's upgrade and discuss the future roadmap: https://zoom.us/j/405797939

In this week's dev call we went over the debriefing of last week's upgrade detailed in this medium post: “The Upgrade Experience” by Ethan Frey https://link.medium.com/7Y0CMg957Y. We also briefly discussed roadmap updates that are in progress. We will be providing updated timing regarding testnet events as soon as we have that available

A reminder that we are having our regularly schedule community dev call in just a few minutes at 10am PT/1pm ET/7pm CEST (https://zoom.us/j/405797939)!

Updates for this week:

- the second test of our upgrade module will involve testing a watcher process that makes automatically takes care of the upgrade giving that the proper binary is installed (or can be downloaded from a trusted source). The code is being worked on here: https://github.com/regen-network/cosmos-upgrade-manager. Our updated timing for this test is after Labor Day in the US so that this is not happening in the summertime - likely the second or third week of September. We welcome comments on the ideal timing and will post a poll with days when we're a bit closer

- we have started working on the specification for Ecosystem Service Credits here https://github.com/regen-network/regen-ledger/pull/67. These are essentially non-fungible tokens (NFTs) that have a uniqueness constraint around a given polygon for a given period of time. These are being worked on in close coordination with a biodiversity credit pilot project that will be using them. Eventually this specification will lead to an on-chain decentralized exchange for ecosystem service credits, as well as on-chain geospatial indexing to prevent double selling ecosystem services for a given piece of land

- we have fixed an issue on our RPC/LCD node that caused block explorers and Lunie not to work after the upgrade - it was completely unrelated to the upgrade itself, just a side effect of messing with that node's configuration

In today's call we will be givinig an overview of our near and mid term roadmap to give context to what we are working on and testing in the testnet

Also: a quick reminder that our token sale is open. It's been moving quickly and if you'd like to get in before the end of the first round, details are on the website: https://www.regen.network/investors.html

A reminder that we are having our regularly scheduled community dev call in just half an hour at 10am PT/1pm ET/7pm CEST (https://zoom.us/j/405797939)!

Looking forward to the dev call. The main planned topics today are:

* More clarification on the roadmap. Aaron presented it at the last dev call, this is now captured in https://link.medium.com/7Y0CMg957Y

* Presentation of plans for the upgrade manager to help with the next testnet upgrade. Feedback very welcome, current spec at https://github.com/regen-network/cosmos-upgrade-manager/blob/organize-readme/README.md

* Progress on other promised upgrade improvements https://github.com/regen-network/cosmos-sdk/pulls?q=is%3Apr+is%3Aclosed

* Tentative planning for next testnet upgrade

And of course, any questions that come up from the community. Looking forward to seeing many of you soon.

A reminder that we are having our regularly scheduled community dev call in just about 40 minutes at 10am PT/1pm ET/7pm CEST (https://zoom.us/j/405797939)! Hope to see many of you there

Updates for this week:
* we are preparing a new Regen Ledger binary with https://github.com/regen-network/cosmos-sdk/pull/4, https://github.com/regen-network/cosmos-sdk/pull/3, and https://github.com/regen-network/regen-ledger/pull/51 merged in, as well as an internally tested release of https://github.com/regen-network/cosmos-upgrade-manager
* we have decided to rotate upgrade times between 9:00, 17:00 and 1:00 UTC so that the awkward timing of upgrades is equally distributed. Sometimes it will be really inconvenient, sometimes convenient, but we'll rotate the burden. The next upgrade is planned for 9:00 UTC - that is 02:00 US Pacific, 05:00 US East, 11:00 Central Europe, 17:00 China. Last time it was pretty inconvenient for Asia, this time it will be better. *Please note these are target times, not precise - this time the upgrade will be based on block height not clock time*
* we will post a poll soon for the upgrade day, close that by this Friday and start a governance poll soon after

Based on the results of our poll, we will aim (by block height) to do the upgrade on Tue 9/24

We will be having our telegram AMA with CTO Aaron Craelius and Lead Engineer Ethan Frey on our public channel in just 15 short minutes: https://t.me/regennetwork_public

Our community validator call will still be taking place this week at 10am PT/1pm ET/7pm CEST (https://zoom.us/j/405797939). Soon we will be shifting to another time TBA. Today we will discuss preparation for next week's upgrade targeted for Tue 9/24 at 9am UTC. We will also be submitting a governance proposal later today to trigger this upgrade based on our best estimate of the block height corresponding to our target time

Governance proposal 2 for the amazonas upgrade to regen-test-1001 has been submitted to occur at block height 1722050 which is targeted for approximately 13:00UTC on Thursday 9/26. The voting window goes until 2019-09-26T02:53:44.409860456Z - basically Wednesday night. In order to vote yes you can use the command xrncli tx gov vote 2 yes --from <your-key>.

We intend to publish an upated upgrade guide on medium Monday which gives new instructions and hopefully a streamlined process with https://github.com/regen-network/cosmos-upgrade-manager

For those of you that missed the discussion we moved the upgrade from Tuesday to Thursday next week so as to not overlap with the Cosmos Hub upgrade.

We will be meeting with the Cosmos SDK team shortly after the upgrade test on Thursday to discuss upstreaming of this code.

Here is the upgrade guide for the amazonas upgrade: https://medium.com/regen-network/amazonas-upgrade-guide-b31e9e18e0be. We have also published a first release of https://github.com/regen-network/cosmosd (used to be cosmos-upgrade-manager)

Please let us know ASAP if you encounter any issues setting up cosmosd and we will look for a fix

Also, please vote for gov proposal 2!

If you haven't voted on gov proposal 2 yet you have until 2019-09-26T02:53:44.409860456Z - basically later today: xrncli tx gov vote 2 yes --from <your-key> --chain-id regen-test-1001

Regen Testnet Validators, we are wrapping up Regen Test 1001 Incentivized Testnet. If any validators would like to earn bonus points we will adding extra points for the creation of a proposal to modify the missed block—jail setting from 50 blocks. Bonus points will also be allocated to all voting participants. This will be the last action of the test net. After this proposal and vote the test net will be closed and the points will be tallied. We will announce the details of the next incentivized testnet series before the end of October. If no proposal is created before 0800 UTC Monday, October 7th the testnet will simply be ended. Have fun!