Proposals of #282

Juno Upgrade: Aurora v14

Exec Legacy Content
passed
Expected result
Turnout / Quorum
103.10% / 33.40%
Voting start 2023.04.10 at 21:04:15
Voting end 2023.04.15 at 21:04:15
99.89%
41 826 410 juno
Yes
0.00%
1 684 juno
No
0.00%
110 juno
Veto
0.11%
46 009 juno
Abstain

Details

logo
Proposer
-
Total deposit
1 000 juno
Submit time
2023.04.10 at 20:04:27
Deposit end time
2023.04.20 at 20:04:27

Description

Juno Aurora Upgrade (v14)\n\nJuno Medium v14 Article\n\nThis upgrade brings the following major changes to Juno Network:\n- x/GlobalFee Module\n- x/IBC-Hooks Module\n- 0 Fee IBC Relaying\n- Stargate Staking Queries\n- Tokenfactory: ForceTransfer, MintTo, and BurnFrom (admin only)\n- x/wasmd 0.31\n- wasmvm 1.2.1\n- Skip's mev CometBFT by default\n\n## x/GlobalFee Module\n\nSignaling proposal from December 13th, 2022: PASSED\n\nCurrently on cosmos based chains, the validators are fully in control of the network fees. With this new module, a minimum gas fee is set by governance to set the gas floor.\n\nAt the upgrade, gas fees are set to our setup documentation gas prices default:\n- 0.0025ujuno\n- 0.001uatom (ibc/C4CFF46FD6DE35CA4CF4CE031E643C8FDC9BA4B99AE598E9B0ED98FE3A2319F9)\n\nAt any time, governance can increase these fees across the network to help deliver more for developers (through feeshare) and stakers. It can also add new tokens to be accepted as fees, such as OSMO and/or USDC in the future.\nIf an transaction attack occurs on Juno, validators are still able to raise their fees ABOVE the minimum gas fee to protect the network as needed.\n\nThe only exception to this are bypassed messages for IBC relaying and transfers. These messages are exempt from the minimum gas fee within reasonable limits. For this to work, validators must set their fees to be: '0ujuno,0ibc/C4CFF46FD6DE35CA4CF4CE031E643C8FDC9BA4B99AE598E9B0ED98FE3A2319F9' in their app.toml. No other denoms can be accepted UNLESS governance passes a proposal to do so.\n\n## x/IBCHooks Module\n\nThis module from the osmosis team allows for token transfers (of the ICS-20 spec ) to call contracts cross chain. The primary importantance of this is allowing cross chain swaps. \n\n## x/wasmd 0.31 & wasmv 1.2.1\n\nWasmd 0.31 Confio Article\nwasmvm 1.2.1 Confio Article\n\nThe main feature from this update which many development teams have requested is instantiate2 to replicate a contract with predictable addresses. You can find an example of this with the contract example. Some other notable improvements include:\n- Governance based weighted votes\n- new queries from wasmvm 1.2 (add the cosmwasm_1_2 feature in your contract toml)\n- Uint128/Decimal multiplication\n- A new 'Never' type\n\n## New Token Factory Methods\n\nFrom the previous upgrade, v13, we added the x/TokenFactory module to deliver a better UX for developers and users alike. As the admin of a token denomination you can now Force transfer tokens between accounts, Mint directly to an account, and burn from another account. In the future we will also add support for disabling the sending of tokens, and only allowing minting/burning for specific application needs.\n\n## Stargate Staking Queries\n\nContracts can now query the chain for an accounts: Delegation, Redelegations, and Unbonding information.\n\n## Skip MEV by default\n\nWith the passing of Juno proposal 275, Skip's MEV CometBFT consensus is now used by default.\n\n## Command Line improvements\n\nYou can now specify the following configurations for any transaction commands you run:\n- Gas\n- Gas Prices\n- Gas Adjustment\n- Fees\n- Fee-Account\n- Note (memo)\n\nSet these with junod config fees 5000ujuno or junod config gas-prices 0.0025ujuno.\n\n---\n\n\n## Voting Options\n\nYES: Agree to proceed with Juno v14 network upgrade.\n\nNO: Disagree with the Juno v14 network upgrade.\n\nNO WITH VETO: Disagree with the Juno v14 network upgrade and want depositors penalized.\n\nABSTAIN: Decline to give an opinion on the Juno v14 network upgrade.\n\n

Votes

Voter
Answer