• Overview

  • Overview
  • Blockchain

  • Blockchain
  • BlocksTransactionsTop accountsContracts & Code ID
  • Validators

  • Validators
  • Proposals

  • Proposals
  • Utilities

  • Utilities
  • ParametersConsensusUptimeAPI
  • Relayers

  • Relayers
  • Nodes

  • Nodes

mainnet

archway-1

Latest Block

‌
‌

Powered by

STAKEME
Backend: —Frontend: v4.6.0-f0b53440

Company

About usStakingFaucetBrand kit

Contribute

Contact usBug reportStatus page

Socials

Proposal details

#21 v4.0.2

Passed
SoftwareUpgradeProposal

This is a proposal to do a software upgrade to the v4.0.2 software tag of the Archway codebase on block height `1215711`, which is estimated to occur on `Sep 25th 2023, 09:23 UTC`. Block times have high variance, so please monitor the chain for more precise time estimates.\n\n### Where is v3.0.0 ?\n\nThe version v3.0.0 was tagged but never released to testnet/mainnet due to upstream depencdency of Cosmwasm receiving an update soon after. This upgrade proposal combines both changes from v3.0.0 and v4.0.2\n\n# Upgrade Features\n\nThis upgrade adds the following features:\n\n## [Fee Burn](https://github.com/archway-network/archway/pull/422)\n\nTo better accommodate inflationary rewards increases within the Archway protocol, we are introducing transaction (TX) fee burning. This strategy permits us to offer more inflationary rewards to contracts safely, while simultaneously incinerating the TX fees which were previously distributed to validators and stakers.\n\n__For Contract Developers__ - Contract Execution txs will consume more gas now (approximately 12000). As such, the fees to interact with your contracts will get more expensive. By roughly 0.0108arch more.\n\nYou can find more details about the fee burn mechanism here: [ADR-007 – Introduction of fee burning](https://github.com/archway-network/archway/blob/0f74dfbf6178578bc30fb2cbee3ae1ed5bc63dd9/docs/adr/ADR-007-fee-burning.md)\n\n## [Cosmwasm_1_3 capabilities](https://github.com/archway-network/archway/pull/429)\n\nBy bumping the wasmd to v0.33.0, archway now supports [`cosmwasm_1_3` capabilities](https://github.com/CosmWasm/cosmwasm/blob/f3d57ce2a92c55495267c426e3c9c0364bf98596/docs/CAPABILITIES-BUILT-IN.md).\n\nSee the [Full Change Log](https://github.com/archway-network/archway/blob/v4.0.2/CHANGELOG.md) here.\n\n# Details of Upgrade Time\n\nThe proposal targets the upgrade proposal block to be `<block_height>`, anticipated to be on `<block_time>`. Note that block times have high variance, so keep monitoring the time. See countdown [here](https://www.mintscan.io/archway/blocks/<block_height>).\n\nIn the event of an issue at upgrade time, we should coordinate via the [#mainnet-validators](https://discord.com/channels/892203409418092615/1077414874042355852) channel in Discord to come to a quick emergency consensus and mitigate any further issues.\n\n## Upgrade Instructions\n\nRecommended Go version: **1.20**\n\n```sh\narchwayd version --long\n> name: archwayd\n> server_name: archwayd\n> version: 4.0.2\n> commit: 23404f906b9f767d09d525672b962b5a19f3efee\n> build_tags: netgo,ledger\n> go: go version go1.20.1 linux/amd64\n> cosmos_sdk_version: v0.45.16\n```\n\nYou can find more details on how to upgrade your node [here](https://docs.archway.io/validators/becoming-a-validator/chain-upgrade).\n

Submit time: 15 Sep 2023, 12:18

Details

Voting period

100.00%

15 Sep 2023, 12:2622 Sep 2023, 12:26

Software Upgrade Proposal

  • Title

    v4.0.2

  • Type

    SoftwareUpgradeProposal

  • Name
    v4.0.2
  • Height
    1 215 711
  • Data
    {
    "plan":{
    "name":"v4.0.2"
    "time":{
    "seconds":"-62135596800"
    }
    "height":"1215711"
    "info":"{"binaries":{"linux/amd64":"https://github.com/archway-network/archway/releases/download/v4.0.2/archwayd_linux_amd64"}}"
    }
    "@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal"
    }