Osmosis v9 Nitrogen Upgrade

Osmosis Nitrogen Upgrade\n\nThis is a proposal to do a software upgrade to the v9.0.0 software tag of the Osmosis codebase on block height 4707300, which is estimated to occur on Tuesday June 7th, UTC 16:00. Block times have high variance, so please monitor the chain for more precise time estimates.\n\n## Upgrade Features\nThis upgrade adds the following features:\n\n### GAMM API changes\nAPI changes were done to enable more CFMM's to be implemented within the existing framework.\nIntegrators will have to update their messages and queries to adapt, please see https://github.com/osmosis-labs/osmosis/blob/main/x/gamm/breaking_changes_notes.md\n\n### Governance Changes\n* Superfluid stakers now have their votes override their validator's votes\n* Governance can set a distinct voting period for every proposal type\n\n### IBC\n* Upgrade to IBC v3\n* Enable Interchain account host module\n* See here for the supported messages\n\n### Txfees\n* Non-osmo txfees now get swapped into osmo every day at epoch, and then distributed to stakers.\n\n### Cosmwasm\n* Upgrade from wasmd v0.23.x to v0.27.0. This has the following features:\n * State sync now works for cosmwasm state\n * Cosmwasm builds on M1 macs\n * Many security fixes\n\n* The TokenFactory module is added to the chain, making it possible for users and contracts to make new native tokens.\n * Cosmwasm bindings have been added, to make swapping and creating these new tokens easier within the contract ecosystem.\n\n\n## Getting Prepared for the Upgrade\nAs always, we recommend validators utilize 64GB of RAM. Since state migration is relatively negligible in this upgrade, it is likely possible to get away with less, but still not recommended. If you are unable to have 64GB of RAM, at a minimum have a total of 64GB of swap set to prevent out of memory errors.\n\nIf using cosmovisor, either auto-download binaries or manually build & copy the osmosisd binary to /cosmovisor/upgrades/v9/bin/.\n\nIf not using cosmovisor, wait for your node to halt at the upgrade height, then install and run the v9.0.0 binary.\n\n\n## Details of Upgrade Time\nThe proposal targets the upgrade proposal block to be 4707300, anticipated to be on Tuesday June 7th 16:00 UTC. This uses an average block time of 6.3730 seconds per block, derived from the Mintscan block explorer. Note that block times have high variance, so keep monitoring the time. See countdown here\n\nThe upgrade is anticipated to take approx 30 minutes, during which time, there will not be any on-chain activity on the network.\n\nIn the event of an issue at upgrade time, we should coordinate via the validators channel in discord to come to a quick emergency consensus and mitigate any further issues.