# \[Proposal #65\] agoric-upgrade-13: smart-wallet auto-provisioning, interchain stack, **URL:** \ **Category:** Network Upgrades\ **Created:** [December 7, 2023, 7:06pm UTC](https://community.agoric.com/t/proposal-65-agoric-upgrade-13-smart-wallet-auto-provisioning-interchain-stack/560 "2023-12-07T19:06:12Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![JD-Agoric](https://sea1.discourse-cdn.com/flex019/user_avatar/community.agoric.com/jd-agoric/32/113_2.png) [@JD-Agoric](https://community.agoric.com/u/JD-Agoric)\ **Post date:** [December 7, 2023, 7:06pm UTC](https://community.agoric.com/t/proposal-65-agoric-upgrade-13-smart-wallet-auto-provisioning-interchain-stack/560/1 "2023-12-07T19:06:12Z")
👋 Hello Agoric Validators & BLD Community, Agoric OpCo is happy to announce that a new software release, agoric-upgrade-13, is now available for the agoric-3 chain. 🙌 Release details: - Auto smart-wallet provisioning - Interchain stack We’ve prepared the following: > **[Release agoric-upgrade-13-rc0 · Agoric/agoric-sdk](https://github.com/Agoric/agoric-sdk/releases/tag/agoric-upgrade-13-rc0)** > > The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-13-rc0 release candidate. This release is primarily intended to offer a new smart wallet provisioning flow, update the int... Upgrade Handlers: Emerynet: **agorictest-upgrade-13** Mainnet: **agoric-upgrade-13** ### 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 OpCo recommends that validators evaluate the following milestones before launching an on-chain governance proposal on the agoric-3 mainnet. _Note: 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._ 0️⃣ – **Choose a testnet coordinator to kick off the Emerynet upgrade**. Traditionally, the testnet coordinator submits the on-chain proposal for mainnet software upgrade. 1️⃣ **Evaluate core mainnet functionality**. This could include: - Exercising the new VM functionality of the release by participating in the upgrade - Restarting your node after a successful upgrade - Exercising on-chain governance parameters - Creating a state-sync snapshot - Spinning up a node using a state-sync snapshot 2️⃣ – **Keep the community updated on testnet progress** by posting updates to this thread and/or sharing details in Discord so that the entire community can follow progress towards launch. 3️⃣ – **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**. 4️⃣ – **Testnet Lead (or another validator) create a mainnet proposal**, if needed seek support from the community for deposit. ### Calculating an upgrade height [GitHub - Agoric/estimator 4 2](https://github.com/agoric/estimator) ### Creating an Emerynet upgrade proposal: **Confirm the commit hash and upgrade name** BEFORE submitting a proposal. ```auto # Edit as needed FROM_WALLET=yourwallet UPGRADE_HEIGHT="1234-get-blockheight-from-estimator" # Verify values UPGRADE_TO="agorictest-upgrade-13" CHAIN_ID="agoric-emerynet-8" COMMIT_ID=$(git rev-parse HEAD) ZIP_URL="https://github.com/Agoric/agoric-sdk/archive/${COMMIT_ID}.zip" CHECKSUM=sha256:$(curl -L "$ZIP_URL" -o- | shasum -a 256 | cut -d' ' -f1) UPGRADE_INFO="{\"binaries\":{\"any\":\"$ZIP_URL?checksum=$CHECKSUM\"}}" agd tx gov submit-proposal software-upgrade $UPGRADE_TO --upgrade-info="$UPGRADE_INFO" --upgrade-height="$UPGRADE_HEIGHT" --title="Upgrade to $UPGRADE_TO" --description="This proposal if voted will upgrade the chain to $UPGRADE_TO" --from=$FROM_WALLET --chain-id=$CHAIN_ID ``` 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-13. ### Creating a Mainnet upgrade proposal: **Confirm the commit hash and upgrade name** BEFORE submitting a proposal. ```auto # Edit as needed FROM_WALLET=yourwallet UPGRADE_HEIGHT="1234-get-blockheight-from-estimator" # Verify values UPGRADE_TO="agoric-upgrade-13" CHAIN_ID="agoric-3" COMMIT_ID=$(git rev-parse HEAD) ZIP_URL="https://github.com/Agoric/agoric-sdk/archive/${COMMIT_ID}.zip" CHECKSUM=sha256:$(curl -L "$ZIP_URL" -o- | shasum -a 256 | cut -d' ' -f1) UPGRADE_INFO="{\"binaries\":{\"any\":\"$ZIP_URL?checksum=$CHECKSUM\"}}" agd tx gov submit-proposal software-upgrade $UPGRADE_TO --upgrade-info="$UPGRADE_INFO" --upgrade-height="$UPGRADE_HEIGHT" --title="Upgrade to $UPGRADE_TO" --description="This proposal if voted will upgrade the chain to $UPGRADE_TO" --from=$FROM_WALLET --chain-id=$CHAIN_ID ``` ### Important note for anyone generating state-sync snapshots or restoring from state-sync In order to produce state-sync snapshots, beginning with 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 have been 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 before agoric-upgrade-11, or if you used a community snapshot that had itself restored from state-sync, then your DB will not be complete. You can restore from state-sync with agoric-upgrade-13 to obtain a complete DB. We are aware of continued performance issues related to state-sync. In particular, we’ve observed that on the agoric-3 chain, the current implementation can require 100 GB of free disk space and 16GB of memory during a state-sync restore, and the process can take almost an hour depending on the characteristics of the machine. ---
**Author:** ![JD-Agoric](https://sea1.discourse-cdn.com/flex019/user_avatar/community.agoric.com/jd-agoric/32/113_2.png) [@JD-Agoric](https://community.agoric.com/u/JD-Agoric)\ **Post date:** [December 11, 2023, 6:01pm UTC](https://community.agoric.com/t/proposal-65-agoric-upgrade-13-smart-wallet-auto-provisioning-interchain-stack/560/2 "2023-12-11T18:01:11Z")
Update: Emerynet was successfully upgraded to agorictest-upgrade-13 ---
**Author:** ![toliaqat](https://sea1.discourse-cdn.com/flex019/user_avatar/community.agoric.com/toliaqat/32/418_2.png) [@toliaqat](https://community.agoric.com/u/toliaqat)\ **Post date:** [December 14, 2023, 9:21pm UTC](https://community.agoric.com/t/proposal-65-agoric-upgrade-13-smart-wallet-auto-provisioning-interchain-stack/560/3 "2023-12-14T21:21:33Z")
I did testing of IBC transactions with testnet tokens. Created IBC channel between emerynet and devnet and tested IBC transfers to both sides. Agoric Emerynet → Agoric Devnet Emerynet Tx hash [https://explorer.kjnodes.com/agoric-testnet/tx/F1953E32201EDEB809650DB3009D42D48379936603C4942E51D31F229FB530E6](https://explorer.kjnodes.com/agoric-testnet/tx/F1953E32201EDEB809650DB3009D42D48379936603C4942E51D31F229FB530E6) Devnet Tx hash [https://devnet.explorer.agoric.net/agoric/tx/85BFCF1D3F9AC76FB1A29F541BC315A5FB5DDCC8352150D87E8684CAFD5488C0](https://devnet.explorer.agoric.net/agoric/tx/85BFCF1D3F9AC76FB1A29F541BC315A5FB5DDCC8352150D87E8684CAFD5488C0) Agoric Devnet → Agoric Emerynet Devnet tx hash [https://devnet.explorer.agoric.net/agoric/tx/46D772E1EE3B1AF1103D69FFCAE42378E6E1CEBE921FD1E414AFA1C7A4105707](https://devnet.explorer.agoric.net/agoric/tx/46D772E1EE3B1AF1103D69FFCAE42378E6E1CEBE921FD1E414AFA1C7A4105707) Emerynet tx hash [https://explorer.kjnodes.com/agoric-testnet/tx/302EAF1EF0D84901C243360F05A71AA19AAF5090AF9FE4F50F090B1FB104F8A0](https://explorer.kjnodes.com/agoric-testnet/tx/302EAF1EF0D84901C243360F05A71AA19AAF5090AF9FE4F50F090B1FB104F8A0) ---
**Author:** ![Kristaps\_Jahimovics](https://sea1.discourse-cdn.com/flex019/user_avatar/community.agoric.com/kristaps_jahimovics/32/177_2.png) [@Kristaps\_Jahimovics](https://community.agoric.com/u/Kristaps_Jahimovics)\ **Post date:** [December 15, 2023, 12:56pm UTC](https://community.agoric.com/t/proposal-65-agoric-upgrade-13-smart-wallet-auto-provisioning-interchain-stack/560/4 "2023-12-15T12:56:59Z")
We have testnet on-chain governance with proposal [#24](https://explorer.kjnodes.com/agoric-testnet/gov/24) ✅ ---
**Author:** ![JD-Agoric](https://sea1.discourse-cdn.com/flex019/user_avatar/community.agoric.com/jd-agoric/32/113_2.png) [@JD-Agoric](https://community.agoric.com/u/JD-Agoric)\ **Post date:** [December 15, 2023, 6:52pm UTC](https://community.agoric.com/t/proposal-65-agoric-upgrade-13-smart-wallet-auto-provisioning-interchain-stack/560/5 "2023-12-15T18:52:24Z")
Update: After a successful Emerynet period with milestone tests led by Hindsight, @joeleiAfish, @Kristaps_Jahimovics, and testing complete by OpCo engineering, the `agoric-upgrade-13` release has been updated with the rc tag removed and is now ready to be proposed to mainnet. > **[Release agoric-upgrade-13 · Agoric/agoric-sdk](https://github.com/Agoric/agoric-sdk/releases/tag/agoric-upgrade-13)** > > The Agoric OpCo engineering team is pleased to publish the agoric-upgrade-13 release. This release is primarily intended to offer a new smart wallet provisioning flow, update the interchain stack ... ---
**Author:** ![JD-Agoric](https://sea1.discourse-cdn.com/flex019/user_avatar/community.agoric.com/jd-agoric/32/113_2.png) [@JD-Agoric](https://community.agoric.com/u/JD-Agoric)\ **Post date:** [December 19, 2023, 4:50pm UTC](https://community.agoric.com/t/proposal-65-agoric-upgrade-13-smart-wallet-auto-provisioning-interchain-stack/560/6 "2023-12-19T16:50:52Z")
agoric-upgrade-13 is now in the voting period. > **[Proposal Details](https://bigdipper.live/agoric/proposals/65)** > > Big Dipper is an open-source block explorer and token management tool serving over 10 proof-of-stake blockchains. It has been forked more than 100 times on GitHub and has served audiences from 140 countries and regions. Voting ends: 03:19 UTC Upgrade height: Block `13017175` ---
**Author:** ![JD-Agoric](https://sea1.discourse-cdn.com/flex019/user_avatar/community.agoric.com/jd-agoric/32/113_2.png) [@JD-Agoric](https://community.agoric.com/u/JD-Agoric)\ **Post date:** [December 21, 2023, 3:32am UTC](https://community.agoric.com/t/proposal-65-agoric-upgrade-13-smart-wallet-auto-provisioning-interchain-stack/560/7 "2023-12-21T03:32:56Z")
Proposal 65 has passed! This means that the Agoric chain will be upgraded to agoric-upgrade-13. The upgrade height is expected to arrive on Dec. 21st around 13:00 UTC. ---
**Author:** ![JD-Agoric](https://sea1.discourse-cdn.com/flex019/user_avatar/community.agoric.com/jd-agoric/32/113_2.png) [@JD-Agoric](https://community.agoric.com/u/JD-Agoric)\ **Post date:** [December 21, 2023, 6:05pm UTC](https://community.agoric.com/t/proposal-65-agoric-upgrade-13-smart-wallet-auto-provisioning-interchain-stack/560/8 "2023-12-21T18:05:58Z")
The chain upgrade was successful! The upgrade process took 14 minutes to go from upgrade height to new blocks. Big thanks to the validators for coordinating another smooth upgrade of the Agoric chain! 🙌