Juno Moneta Patch Upgrade Proposal\n\nAfter Moneta upgrade two bugs have been found by the Core-2 Team in Smart Contracts, this on-chain proposal is to adopt junod v2.1.x which will fix the issues. \n\n# Details\n\n* Fix submessages, required for complex contracts deployments like JunoSwap\n* Change contract address lenght from 20 bytes to 32\n\nGitHub issues\n\nhttps://github.com/notional-labs/wasmd/pull/13\nhttps://github.com/notional-labs/wasmd/pull/11\n\n# Notes\nThis version has been tested on Uni testnet and a simulation of the upgrade has been done. In case of a failure validators will coordinate with core teams to rollback and cancel the upgrade.\n\n# On-Chain Upgrade Process\n\nWhen the network reaches the halt height, the state machine program of Juno will be halted. The classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. \n\nCosmovisor is a tool that can help you with this process. There is a guide for setting it up in the Juno docs.\n\nValidators can coordinate with each other on Discord in advance of the release. As the target block is more than 5 days away, changes in average block speed might change the target time.\n\nWe are aiming for 1600UTC on the 23th of December (height 1165200), but be aware that this block could arrive +/- 2 hours or more.