Hello Agoric Validators & BLD Community
Agoric OpCo is happy to announce that a new software release, agoric-upgrade-11, for the agoric-3 chain is now available. 
This release contains a few important upgrades including:
- State Sync fixes
- Bug fixes
We’ve prepared the following:
Upgrade Handlers:
Emerynet: agorictest-upgrade-11
Mainnet: agoric-upgrade-11
Important note for anyone generating state-sync snapshots for use by new nodes:
In order to produce state-sync snapshots after agoric-upgrade-11, your node must have a “complete” JS database. If your DB isn’t complete, the state-sync generation process will fail. If you were running a node continuously since the Mainnet 1B upgrade (agoric-upgrade-10), then your DB will be complete.
If you created your node from a state-sync restore, or if you used a community snapshot that had itself restored from state-sync, then your DB will not be complete.
Agoric OpCo has follower nodes that are complete, and we’ll make sure that they’re available to create state-sync snapshots and help “seed” the network if needed.
Recommended Testnet Milestones
By running long-lived testnets and using that environment to evaluate software before promoting it to mainnet, validators play a vital role in maintaining a healthy, robust network for the Agoric community. Qualifying or certifying any new software release as production ready requires significant testing, and Agoric core developers recommend that validators evaluate the following milestones before launching an on-chain governance proposal on the agoric-3 mainnet.
– Choose a testnet coordinator to kick off the Emerynet upgrade. Traditionally, the testnet coordinator submits the on-chain proposal for mainnet software upgrade.
– Ensure that you’re up to date on golang and node versions for this release, and that you’ve upgraded to the newest version of Cosmovisor that supports the upgrade handler.
– Evaluate core mainnet functionality. This could include:
- Creating a state-sync snapshot
- Spinning up a node using a state-sync snapshot
- Exercising the new VM functionality of the release by participating in the upgrade
- Restarting your node after a successful upgrade
- Making IBC transactions with testnet tokens
- Exercising on-chain governance parameters
- Test Inter Protocol Vaults and Liquidations
– Take Vaults for a test drive. Once the UIs are wired up and the Econ Committee has set economic parameters on Emerynet, this could include:
- Creating a Vault
- Adjusting your Vault balances
- Closing a Vault
- Test out liquidations
– Keep the community updated on testnet progress by posting updates to this thread or sharing details about mainnet-1b in Discord or Twitter so that the entire community can follow progress towards launch.
– Coordinate with your fellow validators to determine if this release is ready to be promoted to mainnet and, when ready, the Testnet Coordinator should notify the OpCo team that they’d like the pre-release tag removed.
– Testnet Lead or another validator create a mainnet proposal, if needed seek support from community for deposit.
Calculating an upgrade height
Creating an Emerynet upgrade proposal:
Confirm the commit hash BEFORE submitting a proposal.
upgradeto="agorictest-upgrade-11"
height="123get-blockheight-from-estimator"
agd tx gov submit-proposal software-upgrade $upgradeto --upgrade-info= <see release notes for instructions> --upgrade-height="$height" --title="Upgrade to $upgradeto" --description="This proposal if voted will upgrade the chain to $upgradeto" --from=yourwallet --chain-id=agoric-emerynet-8
When the testnet milestones are complete and validators have fully qualified the release on Emerynet, the testnet coordinator should inform Agoric OpCo to promote the release from rc to final and update tags accordingly, then create and submit a similar on-chain proposal to upgrade the agoric-3 chain to agoric-upgrade-11.
Creating a Mainnet upgrade proposal:
Confirm the commit hash BEFORE submitting a proposal.
upgradeto="agoric-upgrade-11"
height="123get-blockheight-from-estimator"
agd tx gov submit-proposal software-upgrade $upgradeto --upgrade-info=<see release notes for instructions> --upgrade-height="$height" --title="Upgrade to $upgradeto" --description="This proposal if voted will upgrade the chain to $upgradeto" --from=yourwallet --chain-id=agoric-3
2.1. Creating a state-sync snapshot
