[Mainnet] Update two protocol parameters for IBC Eureka activation

Following the incoming upgrade to v201.0.7 as described here, we must also increase the values two protocol parameters - the max_tx_bytes and max_proposal_code_size.

This is needed so that subsequently, we can upgrade the tx_ibc.wasm on-chain, which will activate the IBC Eureka connection via that transaction. This wasm is quite large, and these protocol parameter value increases are needed in order to put the new large wasm on-chain.

These db changes have been made on Housefire testnet in Props 41 and 44 successfully.

4 Likes

:white_check_mark: Hashes match on both governance proposal (#38) and namada-governance-upgrades repository.

Data: Hash: 51C29AC1D380438F184D7ED3053825B5F5A2529FAA11ECB84E2D68B3BB0AB213
sha256sum update_params_pre_ibc_eureka.wasm
51c29ac1d380438f184d7ed3053825b5f5a2529faa11ecb84e2d68b3bb0ab213  update_params_pre_ibc_eureka.wasm
3 Likes