#43 This proposal if voted will upgrade the chain to agoric-upgrade-11

The upgrade is primarily intended to fix state-sync and data-encoding formats, and does not change the behavior of any contracts. It fixes at least the following issues: \n- The JavaScript VM export data is now stored more efficiently, without encoding \n- Using state-sync import to create a new node no longer breaks an hour later \n- state-sync import now repopulates all metadata, enabling a later state-sync export \n- Removes Golang version from in-consensus messages \n- Assume all compiler builtins are present \n- enable genesis export with JS VM data This code has satisfied all pre-release/testnet validation checks, and is now recommended for chains to upgrade from the previous mainnet1B release. As a state-machine-breaking upgrade, once approved, all chain validators will need to upgrade from mainnet1B to this new version (after the chain halts due to reaching the height required in a governance proposal). When this upgrade is activated, there will be a slight pause while some database contents are migrated. After the upgrade, state-sync snapshots will include more data than before. Nodes which have inadvertently pruned this data (e.g. those created from an earlier state-sync) will not be able to produce such snapshots, and will need to be restored from a state-sync snapshot made with the agoric-upgrade-11 software. Please see the forum post for more details. ##Discussion Discussion for this release will take place in the Agoric community forum. https://community.agoric.com/t/agoric-upgrade-11/425\n ##Release https://github.com/Agoric/agoric-sdk/releases/tag/agoric-upgrade-11\n ##Details of Upgrade Time The proposal targets the upgrade block to be 11591462, anticipated to be on or around 11th September 2023 at 17:00 UTC.