Other system
Evmos ticker EVMOS
Historical network. Its profile describes the design as history. The evidence is in the system note below.
Summary
Until May 2026 Evmos was a Cosmos SDK proof-of-stake chain that ran an Ethereum Virtual Machine as a module and ordered blocks with CometBFT. EVMOS holders delegated to validators; the docs describe an active set made of the 150 validators with the most stake at launch. A block committed once validators holding more than two thirds of voting power precommitted it. Double-signing and downtime were slashable and unbonding took two weeks. Governance proposal 331, Evmos shutdown, was submitted on 13 May 2026, passed with about 99.98% of the voting stake in favour, and scheduled a halt at height 37,318,000 (around 18 May). No consensus runs today. 312181921272831
Design
- System
- Other systemEvmos no longer runs. It was a permissionless proof-of-stake layer 1 built with the Cosmos SDK and CometBFT, running an Ethereum Virtual Machine as a module (Cosmos chain ID evmos_9001-2, EVM chain ID 9001). Governance proposal 331, Evmos shutdown, passed in May 2026 and set a halt at height 37,318,000, around 18 May 2026; the Cosmos chain registry now marks the chain as killed. The package table listed it as a layer 1; because the chain has halted it uses the other class here, and the design is described as history.
- Settlement family
- Cosmos SDK
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- While the chain ran, validators in the active set proposed blocks in turn, weighted by voting power, under CometBFT. The size of the active set and its operators at the time of the halt were not verified; the docs describe 150 slots.
- Fork choice
- No open fork choice: each height was decided by more than two thirds of precommits, so committed blocks were not reorganized in normal operation. The first mainnet, evmos_9001-1, ended on version v2.0.1 according to Evmos's mainnet page, and its upgrade table marks the next version, v3.0.0 (released April 2022), as unplanned, manual-only and requiring a data reset; the network continued as evmos_9001-2. The final committed state is fixed because no new blocks are produced.
Qualifications
- Live chain status · Not applicable. Proposal 331 scheduled nodes to halt at height 37,318,000, around 18 May 2026. The chain registry marked the chain as killed on 3 June 2026, and on 27 September 2026 no public RPC endpoint or explorer tried in this review served new blocks. Block time, fees, validator counts and node requirements describe how the chain ran.
- Scarce resource · Not applicable. No Evmos block production exists since the May 2026 halt, so nothing currently secures new blocks. While the chain ran, bonded EVMOS selected validators and could be slashed.
- Finality · Not applicable. No new blocks are produced, so the state at the halt is fixed and nothing further can be finalised. While the chain ran, a block was final once validators with more than two thirds of voting power precommitted it.
- Settlement family · Partial. Evmos was built with the Cosmos SDK, CometBFT and IBC, but users mostly saw its EVM environment: 0x addresses, MetaMask and EVM contracts. It never settled to Ethereum and was not an Ethereum layer 2.
- Block time · Contested. Evmos's architecture page describes blocks of about 2 seconds, while its validator configuration page describes a default commit timeout meant to bring the network to about 4-second blocks. No measured figure was verified before the halt.
- Throughput · Not applicable. Evmos's docs describe high throughput without a sourced, classed figure, and the chain no longer processes transactions, so no throughput claim is recorded.
- Shutdown rationale · Unknown. The on-chain text of proposal 331 states only the halt height and that it carried the messages of the failed proposal 330. No official statement of why the chain was shut down, or what holders should do, was found.
Tradeoffs
- Emphasizes
- Security and Scalability
- Gives up
- Broad participation and continuity. Consensus was limited to a capped set of the top validators by stake, validator machines needed 32 GB of RAM and NVMe storage, and stake-weighted governance was able to vote to halt the whole chain permanently, which it did in May 2026. Holders who disagreed could not keep the chain running on their own: new blocks needed validators holding more than two thirds of voting power.The scalability reading follows Evmos's own description of fast finality, high throughput and short blocks; no throughput figure was verified. The security reading refers to the two-thirds commit rule and slashing while the chain ran. The shutdown vote passed with about 99.98% of voting stake, but turnout relative to all staked EVMOS was not verified.
- Full node at home
- Not applicable 1218There is no live Evmos network to follow: the chain halted in May 2026 and the registry marks it as killed. While it ran, Evmos listed at least 4 physical CPU cores, 32 GB of RAM, 500 GB of NVMe SSD storage and 100 Mbps of bandwidth for mainnet validator nodes and said requirements would rise with use; separate figures for non-validating full nodes were not found.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Not present | Since the May 2026 halt (proposal 331) no transaction can execute, so nothing performs a swap on Evmos. Before the halt, no protocol swap mechanism was reviewed; EVM contracts could have implemented hash-time-locked swaps, but none was verified. IBC token transfers are not swaps. 3 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Not present | None on mainnet now: no new state can be verified after the halt. While the chain ran, its IBC connections relied on on-chain light clients; several of those clients expired and were restored by governance proposals between May 2025 and February 2026. No user-facing light client for Evmos itself was reviewed. 39101132 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No source was cited for absence, so the rule that absence needs a source makes this unknown rather than not present. Earlier finding: no payment or state channel layer anchored to Evmos was found, and none can operate on a halted chain. IBC channels are messaging paths, not payment channels. |
| Programmable spending | None found Earlier definition | Nothing can execute since the halt. While the chain ran, spend conditions were EVM smart contracts, which could also call built-in extensions for staking, reward distribution, IBC transfers and vesting, and Cosmos transactions could be signed with Ethereum wallets through structured-data signing. 31725 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Not present | Nothing can execute since the halt, so no transfer can be reversed or delayed. While the chain ran, the vesting module offered a clawback vesting account whose funder could take back unvested tokens at any time, a delayed transfer the sender could cancel; Evmos used it for team and advisor allocations. It was not a recovery path a user could set up for their own funds. 324 |
| Rollups | Unknown | No source was cited for absence, so the rule that absence needs a source makes this unknown rather than not present. Earlier finding: no rollup settling to Evmos was found. Chains that reused Evmos-derived EVM software for the Cosmos SDK are separate chains, not rollups on Evmos. |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | None foundForge (inactive), Diffusion Finance (inactive), SpaceFi (inactive) | No exchange can operate on the halted chain. DefiLlama's protocol list still names former Evmos exchanges, including Forge, Diffusion Finance, SpaceFi, Cronus Finance and EvmoSwap, all with no value locked on Evmos; their own shutdown notices were not reviewed. Evmos docs also described an Osmosis swap outpost that routed trades to Osmosis over IBC; the node software changelog lists the outpost built-in contracts as removed in v19.0.0 (July 2024). 326293334 |
| Issuer-native stablecoins | None found | No issuer listed a native stablecoin on Evmos: Circle's USDC list names Noble but not Evmos, so USDC on Evmos was a representation carried from another chain, such as the 0.1 USDC that a March 2026 governance test withdrew over IBC to Axelar. No stablecoin can move on the halted chain. 735 |
| Algorithmic stablecoins | Unknown | No source was cited for absence, so the rule that absence needs a source makes this unknown rather than not present. Earlier finding: no stablecoin of any design can operate on the halted chain; algorithmic or hybrid stablecoins used on Evmos before the halt were not reviewed. |
| Bridges | None found | No bridge transfer to or from Evmos can complete after the halt. While it ran, Evmos used IBC channels to Cosmos chains; its docs and the 2026 governance proposals name the Cosmos Hub, Osmosis, Noble, Kava, Stride, Axelar and Gravity Bridge, while the full channel list the docs pointed to was on Mintscan, which no longer serves Evmos. DefiLlama lists Axelar, Nomad, Multichain and Connext among bridges once deployed there. In the final weeks governance moved funds held in IBC channels toward the Cosmos Hub and disabled incoming IBC transfers; a proposal to restore the Osmosis connection failed. Risk: Assets that other chains had sent to Evmos, and Evmos-origin tokens held elsewhere, now depend on whatever governance recovered before the halt. Where the funds moved by proposals 328 and 329 ended up, and whether individual holders were made whole, was not verified. 345623263336 |
| Block explorers | ThinStakeflow (archived governance pages) | Evmos docs listed Mintscan, Escan, BigDipper, ATOMScan and NGExplorer. On 27 September 2026 Mintscan's Evmos page redirected to not found, ATOMScan loaded but could not fetch chain data, and Escan and NGExplorer did not respond. Stakeflow still showed Evmos governance proposals. Explorer data is provider-indexed and not consensus. 3223637 |
| Hardware wallets | ThinLedger (through MetaMask), Trezor (through MetaMask or Rabby) | See the custody section: both vendors still list Evmos, but only through third-party wallet apps, and the chain no longer processes transactions. 3839 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Through an intermediaryMetaMask, named on Ledger's Evmos pageSame as native: No | Can: Keep the key for an Evmos 0x address on a Ledger device and connect it to MetaMask, as Ledger's Evmos page describes Can: Recognise that the same device key controls the matching address on every network that uses Ethereum's key path (coin type 60), which Evmos accounts use Cannot: Send, receive or swap on Evmos: the chain stopped producing blocks in May 2026, although Ledger's page still describes these actions Cannot: Manage Evmos inside Ledger Wallet itself; the page points only to a third-party walletEvmos's docs say Cosmos transactions could also be signed by Ethereum signers, including Ledger devices, through structured-data signing; that path also ended with the halt. 3151738 |
| Trezor | Through an intermediaryMetaMask or Rabby, listed on Trezor's Evmos pageSame as native: No | Can: Keep the key for an Evmos 0x address on a Trezor Safe 3, 5 or 7 and connect it to MetaMask or Rabby, as Trezor's Evmos page lists Can: Recognise that the same device key controls the matching address on every network that uses Ethereum's key path (coin type 60), which Evmos accounts use Cannot: Manage Evmos in Trezor Suite; the page lists only MetaMask and Rabby Cannot: Send or receive on Evmos: the chain stopped producing blocks in May 2026 31539 |
Public data
iKnow Blockchain has no public-data lookups for Evmos yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Cosmos chain registry marks Evmos as killed
A merged change to the Cosmos chain registry set Evmos's status from live to killed, stating that mainnet evmos_9001-2 was shut down through proposal 331 and halted at about block 37,318,000 around 18 May 2026.
- Implementation:Merged
- Release:published in the registry's master branch
- Activation:in effect
Sources: Cosmos chain-registry maintainers — chore(evmos): mark chain status as killed (#7710) (external site) · Cosmos chain-registry maintainers — Evmos chain registry record (external site)
-
Evmos governance passes proposal 331 to shut the chain down
Proposal 331, titled Evmos shutdown, was submitted as a software-upgrade proposal and passed with about 99.98% of the voting stake in favour. It set nodes to halt at height 37,318,000, around 18 May 2026, and carried the messages of proposal 330, which had failed to execute.
- Proposal:Passed
- Implementation:halt height set in the approved upgrade plan
- Release:no new release published in the evmos/evmos repository
- Activation:chain halted around 18 May 2026; registry marks it killed
Sources: Stakeflow — Evmos Proposal #331: Evmos shutdown (external site) · Stakeflow — Evmos Proposal #330: Restore IBC connection with osmosis & IBC transfer (external site) · Cosmos chain-registry maintainers — chore(evmos): mark chain status as killed (#7710) (external site) · ChainCatcher — The Cosmos ecosystem Evmos network has been shut down (external site)
-
Evmos turns off incoming IBC transfers and moves funds out of channels
Proposal 329 set IBC transfers into Evmos to disabled and moved pending funds in the Gravity Bridge and Axelar channels. The day before, proposal 328 had moved funds held in channels with the Cosmos Hub, Noble, Kava and Axelar toward the Cosmos Hub.
- Proposal:Passed
- Implementation:executed by governance
- Release:parameter change and governance transfers; no software release
- Activation:effective from proposal execution in early May 2026
Sources: Stakeflow — Evmos Proposal #329: Disable receipt of IBC tokens & Gov IBC transfer from Gravity (external site) · Stakeflow — Evmos Proposal #328: Gov IBC Transfer to Cosmoshub (external site)
-
Evmos approves v20.2.0 so governance can force IBC withdrawals
Proposal 326 approved the Evmos Mainnet v20.2.0 software upgrade, which lets only the governance module force IBC transfers that withdraw tokens from remote chains. Proposal 327 then tested the path with a 0.1 USDC transfer to Axelar. This followed February proposals restoring expired IBC light clients.
- Proposal:Passed
- Implementation:upgrade approved; code location not verified
- Release:not listed among evmos/evmos releases
- Activation:upgrade height not verified; the governance transfer in proposal 327 passed by 11 March 2026
Sources: Stakeflow — Evmos Proposal #326: Evmos Mainnet v20.2.0 (external site) · Stakeflow — Evmos Proposal #327: Gov IBC Transfer (evmos->axelar) (external site) · Stakeflow — Evmos Proposal #325: Update IBC light client for Cosmos, Axelar and Gravity (external site) · Evmos core maintainers — evmos/evmos releases (external site)
Topics your AI can explain
Your AI can explain these topics for Evmos through the connection, with sources.
Known gaps
What this profile's review did not establish:
- No official statement of why Evmos was shut down, who proposed it, or what holders should do was found. The newest thread on the Evmos Commonwealth forum dates from September 2025 and none discusses a shutdown, the Evmos blog feed's latest post is from July 2024, and evmos.org still showed pre-shutdown content with no notice.
- The final block height and time were not confirmed from a live node or explorer; the halt height comes from the proposal text and the chain-registry change, and news reports relaying Stakeflow.
- Where the funds moved by the 2026 governance transfer proposals ended up, and how balances left on Evmos can be recovered, if at all, was not verified.
- The source code of the v20.2.0 upgrade approved in March 2026 was not found; the evmos/evmos repository's latest release is v20.0.0.
- Which node software version mainnet ran at the halt was not verified: the chain registry still recommends v19.1.0, the repository's latest release is v20.0.0, and governance approved v20.2.0 in March 2026.
- The full list of Evmos IBC channels was not verified: Evmos's docs pointed to Mintscan for it, and Mintscan no longer serves Evmos; the chains named here come from the docs and the 2026 governance proposals.
- The active validator set size, slashing parameters and governance turnout at the time of the halt were not verified from a primary source; the docs describe 150 active slots.
- Stakeflow's proposal pages show times without a time zone, so proposal dates may be off by one day.
- Former exchanges, bridges and stablecoin representations on Evmos were identified from DefiLlama's list and governance texts, not from each project's own pages.
- Whether contract deployment was restricted after the permissioned EVM feature in v19.0.0 was not verified.
- No sourced, classed throughput figure was found, so none is recorded.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Evmos chain registry record (external site)
- chore(evmos): mark chain status as killed (#7710) (external site)
- Evmos Proposal #331: Evmos shutdown (external site)
- Evmos Proposal #330: Restore IBC connection with osmosis & IBC transfer (external site)
- Evmos Proposal #329: Disable receipt of IBC tokens & Gov IBC transfer from Gravity (external site)
- Evmos Proposal #328: Gov IBC Transfer to Cosmoshub (external site)
- Evmos Proposal #327: Gov IBC Transfer (evmos->axelar) (external site)
- Evmos Proposal #326: Evmos Mainnet v20.2.0 (external site)
- Evmos Proposal #325: Update IBC light client for Cosmos, Axelar and Gravity (external site)
- Evmos Proposal #323: Update IBC light client for Kava (external site)
- Evmos Proposal #322: IBC light client update for Kava (external site)
- Technical Architecture (external site)
- Tokens (external site)
- Gas and Fees (external site)
- Accounts (external site)
- Chain ID (external site)
- Signing (external site)
- Validators overview (hardware and active set) (external site)
- Validator FAQ (external site)
- Validator configuration (block time) (external site)
- List of Upgrades (external site)
- Block Explorers (external site)
- IBC Channels (external site)
- x/vesting module (external site)
- EVM Extensions (external site)
- Outposts (external site)
- Mainnet (external site)
- evmos/evmos releases (external site)
- evmos/evmos CHANGELOG (external site)
- Chain 9001 (Evmos) record (external site)
- Byzantine Consensus Algorithm (external site)
- IBC overview (external site)
- DefiLlama protocols list (API) (external site)
- Evmos historical chain TVL (API) (external site)
- USDC contract addresses (external site)
- Mintscan Evmos explorer (redirects to not found) (external site)
- Evmos (EVMOS) Blockchain Explorer (external site)
- Evmos wallet (external site)
- Evmos wallet (external site)
- Evmos | EVM x Cosmos (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding