Layer 1 blockchain
Dymension ticker DYM
Summary
Sovereign proof-of-stake chain (dymension_1100-1) that Dymension calls a settlement layer for application-specific rollups named RollApps. It runs the dymd application (v4.0.x on sampled nodes) built on the Cosmos SDK, Ethermint accounts and CometBFT consensus. DYM holders delegate to validators; at most 125 are active, unbonding takes 21 days and double-signing is slashed 5%. A live query on 2026-09-27 found 68 bonded validators; the largest held about 30% of bonded stake and the top two more than a third. A block commits once validators holding more than 2/3 of voting power precommit it. The Hub also registers RollApps, bonds their sequencers, records their state updates and holds deposited funds. It is secured by its own DYM stake, not by Cosmos Hub stake. 1231517181920
Design
- System
- Layer 1 blockchainThe Dymension Hub (chain ID dymension_1100-1) is a sovereign Cosmos SDK chain with its own DYM-staked validator set. It describes itself as a settlement layer: application-specific rollups called RollApps post state updates to it and keep deposited funds in its built-in bridge. The RollApps are the layer 2s; the Hub itself is a layer 1 and does not borrow Cosmos Hub security.
- Settlement family
- Cosmos SDK
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- Validators selected round-robin in proportion to voting power, per the CometBFT consensus specification. RollApp blocks are produced separately by each RollApp's bonded sequencer, not by Hub validators.
- Fork choice
- No fork choice in the Nakamoto sense: a height is decided by +2/3 precommits. Conflicting commits would need at least 1/3 of voting power to double-sign, which is attributable and slashable. If more than 1/3 of voting power is offline the Hub stops producing blocks instead of forking; by that rule the two largest validators in the sampled query could together halt it.
Qualifications
- Ibc · Applies. IBC is messaging between independently governed chains, checked by on-chain light clients. RollApps also use IBC to move funds to and from the Hub, but other IBC chains such as Noble or Kava are not Dymension layer 2s. Recorded in the bridge row.
- Shared security · Not applicable. The Hub is secured by its own validator set bonding DYM (68 bonded in a live query on 2026-09-27). It is not a Cosmos Hub consumer chain. RollApps rely on the Hub, but the Hub does not borrow security from any other chain. Dymension's glossary uses the phrase shared security for what RollApps get from Hub validators; that describes RollApps, not the Hub's own security.
- Rollapp finality · Partial. A Hub commit is final for the Hub, but a RollApp state update recorded on the Hub becomes final only after the dispute window or an accepted hardware attestation. eIBC liquidity providers can pay users earlier and carry that risk themselves.
- Block interval · Contested. The Beyond proposal targeted about one-second blocks (it put the earlier interval at about 5.5 seconds), and the mint parameters assume about 37.9 million blocks a year. Measured blocks averaged about 4.0 seconds from mid-July to late September 2026 and about 4.6 seconds in the last four days. Because the dispute window is counted in blocks, at those speeds it would last roughly 34 to 39 days rather than seven; that is this review's arithmetic, not a Dymension figure.
- Tps · Unknown. No sourced, classed throughput measurement for the Hub or for RollApps was found. The block interval above is a sample, not a capacity figure.
Tradeoffs
- Emphasizes
- Scalability and Security
- Gives up
- Breadth of participation and trust minimization for RollApps. Stake is concentrated (one validator held about 30% of bonded stake in a sampled query), a Hub full node wants 64 GB of memory, each RollApp is normally run by one active sequencer, and fraud claims are currently decided by Hub governance rather than by an automatic on-chain proof.Scalability here means spreading applications across many RollApps, not raising Hub capacity; no classed throughput figure was found. Security refers to the Hub's BFT commit and its built-in bridge bookkeeping for RollApps. Fast RollApp finality relies on hardware attestations from Google Cloud Confidential Space (Intel TDX), which adds trust in that vendor and hardware.
- Full node at home
- Demanding 13637The Hub node FAQ lists 8 cores, 64 GB of RAM, a 1 TB NVMe disk and 100 Mbps. Storage can be kept smaller with pruning: Polkachu's compressed pruned snapshot, which the chain registry lists, was about 5 GB on 2026-09-27, though the unpacked database is larger and still grows. Memory is the main barrier for typical home machines. Checking a RollApp independently also needs that RollApp's own full node and access to the data availability network it posts to.
- Throughput claims
- No classified figure recorded
Scaling layers
- Dymension RollApps · Rollup, mainnet 58142223262736
A bonded sequencer (minimum 100 DYM) orders each RollApp's transactions, posts block data to an outside data availability network (Celestia or Avail in sampled updates) and posts state roots to the Hub. Withdrawals finalize after 725,760 Hub blocks, which Dymension calls seven days, or at once with an accepted Google Cloud Confidential Space attestation. A state update posted on 2026-09-10 was still pending 17 days later. In the reviewed code, fraud claims are executed by Hub governance, not an automatic proof. Forced inclusion is future work.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | Not yet assessed under the current definitions; no hash-time-locked or other cross-party swap mechanism on the Hub was found. Pool swaps settle inside one Hub transaction but trade against a pool, and eIBC lets a liquidity provider pay out a RollApp withdrawal early for a fee; neither is a swap between two parties. 910 |
| Authenticated data publication | Unknown | Not yet assessed under the current definitions; no Hub feature for publishing data against a chain-recorded commitment was found. RollApps publish block data to external data availability networks, which is those networks' feature, and post state roots to the Hub, which is rollup settlement data held in Hub state. Absence was not exhaustively verified, so the rule that absence needs a source makes this unknown rather than not present. 6 |
| Light clients | Built into the protocolLimited scope | CometBFT consensus produces the validator-signed commits that IBC light clients check, and IBC transfers, including those between RollApps and the Hub, are checked by on-chain light clients. Limit: the docs say RollApp light-client headers are confirmed only after the dispute window, so relayers alone cannot forge a transfer but confirmation waits for that window. 716 |
| 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 payment or state channel layer anchored to the Hub was found. IBC channels are messaging paths, not payment channels. 16 |
| Programmable spending | Partial (layer not stated) Earlier definition | The Hub accepts EVM transactions, but its EVM parameters read on 2026-09-27 disable contract creation and there is no CosmWasm module, so users cannot deploy their own contracts on the Hub. Spend logic is limited to the Hub's built-in modules. General smart contracts run on RollApps (EVM or CosmWasm). 111221 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under this row's current definition. |
| Rollups | Native (protocol or core-team software) Earlier definition | Rollup settlement is built into the Hub: its modules register RollApps, bond sequencers, record state updates and hold deposited funds. A live query on 2026-09-27 listed 1,067 registered RollApps, of which 32 had launched (28 EVM, 4 CosmWasm). Only one launched RollApp had posted a state update in the previous 30 days, three had posted at all in 2026, and eight had never posted one. Their trust model is described in the scaling layer entry. 1112232627 |
| 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 | Native to the protocolDymension embedded AMM (constant-product pools), Initial RollApp Offering bonding curves | The Hub runs its own AMM module with two-token constant-product pools, originally priced against DYM. The allowed pool base assets set by governance in November 2025 are DYM, USDC and KAS. The launchpad sells RollApp tokens on bonding curves that later graduate into AMM pools. Liquidity depth was not measured. 4101332 |
| Issuer-native stablecoins | None found | Neither Circle's USDC list nor Tether's protocol list includes Dymension. USDC on the Hub is an IBC voucher from Noble (noble-1) and USDT an IBC voucher from Kava. In July 2026 governance lifted transfer rate limits on both after the limits had blocked outbound transfers. 3031333839 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on the Hub or on RollApps were not reviewed. |
| Bridges | Native to the protocolIBC, eIBC fast withdrawals, Hyperlane routes (Ethereum, Base, BNB Chain, Solana), Kaspa-Dymension bridge | IBC links the Hub to RollApps and other IBC chains. eIBC lets liquidity providers pay out RollApp withdrawals before the dispute window ends, for a fee. Since the Beyond upgrade the Hub runs Hyperlane: its on-chain security settings list routes whose network numbers match Ethereum, Base, BNB Chain and Solana, plus a Kaspa route. The Kaspa bridge escrows KAS in a multisig address on Kaspa and mints a representation on the Hub. Risk: Hyperlane routes and the Kaspa bridge rely on fixed groups of off-chain signers. On the Hub, incoming messages need 6 of 9 signers from Ethereum, 4 of 6 from BNB Chain, 3 of 5 from Base or Solana and 8 of 15 for Kaspa; the Kaspa design post names 5 of 9 for the escrow on Kaspa. A signer quorum or a code bug can lose funds. eIBC liquidity providers lose if a fraudulent RollApp state goes unreported. RollApp withdrawals depend on the dispute window, governance handling of fraud and Google Cloud attestations. 79162425283435 |
| Block explorers | Established in the ecosystemEZStaking, NodeStake Explorer, Staking Explorer | The chain registry lists 14 explorers for dymension_1100-1, most run by validator operators. These three loaded and showed current Hub data on 2026-09-27. The registry's Mintscan page redirected to a not-found page and its Explorer.ist page did not exist, so the registry list is partly out of date. Listing is not a quality or completeness check. 129 |
| Hardware wallets | Unknown | See the custody rows: Trezor says it does not support Dymension, and Ledger support could not be verified from Ledger's own pages. 40 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | UnknownSame as native: Unknown | Ledger coin-page addresses tried for Dymension returned 404, and the static content of Ledger's supported-assets page does not mention Dymension. The Hub uses coin type 60 keys (Ethermint accounts), so signing through a third-party wallet may be possible, but this was not verified. |
| Trezor | None foundSame as native: No | Cannot: Manage Dymension Hub accounts in Trezor SuiteTrezor's page states that it does not currently support Dymension. Third-party wallets that might use a Trezor device for Hub accounts were not checked. 40 |
Public data
iKnow Blockchain has no public-data lookups for Dymension 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
-
Governance removed stuck IBC rate limits on USDC and USDT
Proposal 40 passed on 2026-07-28 and removed the rate limits on Noble USDC and Kava USDT. The proposal said the limits had been measured against an outdated snapshot that never reset, leaving almost no room for outbound transfers.
- Proposal:passed (proposal 40)
- Implementation:executed as a governance message
- Release:no software release required
- Activation:effective on passage
Sources: Dymension Hub governance via NodeStake public API — Proposal 40: Remove IBC rate limits for Noble USDC and Kava USDT (external site) · Dymension Hub via NodeStake public API — IBC denomination trace for USDC (live Hub query) (external site) · Dymension Hub via NodeStake public API — IBC denomination trace for USDT (live Hub query) (external site) · Dymension Hub via NodeStake public API — IBC rate limits (live Hub query) (external site)
-
dymd v4.0.2 released with the CometBFT Tachyon security patch
Dymension contributors published dymd v4.0.2 on 2026-01-21. Its release note is a single line naming a CometBFT security patch, and the tagged build file swaps the consensus engine for a patch build from the cometbft-sec-tachyon repository. Two days later CometBFT published advisory CSA-2026-001 (Tachyon), rated critical: a faulty block proposer could push block time forward, affecting any module, contract or system that relies on block timestamps. The advisory lists no workaround and says patched versions are required.
- Implementation:CometBFT replaced by a cometbft-sec-tachyon patch build in the v4.0.2 go.mod
- Release:released 2026-01-21 as v4.0.2; marked Latest on the releases page on 2026-09-27
- Activation:not established: no upgrade height or governance record was reviewed; adoption is per operator
Sources: Dymension contributors — Dymension v4.0.2 release notes (external site) · Dymension contributors — Go module file (v4.0.2) (external site) · CometBFT maintainers — CSA-2026-001: Tachyon (external site) · Dymension contributors — Releases · dymensionxyz/dymension (external site) · Dymension Hub via NodeStake public API — Node and application version (live Hub query) (external site)
-
Hardware-attested fast finality for RollApps announced and enabled
Dymension described a path where a RollApp node running inside Google Cloud Confidential Space produces signed attestations that let the Hub finalize RollApp state without waiting out the dispute window. Proposal 34 switched the feature on network-wide on 2025-12-08; each RollApp still opts in.
- Proposal:passed (proposal 34)
- Implementation:shipped in v4.0.0
- Release:released with the Beyond upgrade
- Activation:enabled by parameter; per-RollApp opt-in
Sources: Dymension blog — TEE-Backed Fast Cross-Chain Transfers (external site) · Dymension Hub governance via NodeStake public API — Proposal 34: Enable TEE-Based Fast Finality for RollApps (external site) · Dymension Hub via NodeStake public API — Rollapp module parameters (live Hub query) (external site) · Dymension Hub via NodeStake public API — Registered RollApps (live Hub query) (external site) · Dymension Hub via NodeStake public API — Latest state update of RollApp upordowngame_689603-1 (live Hub query) (external site)
-
Kaspa bridge module bootstrapped by governance
Proposal 32 passed on 2025-11-25 and initialized the Hub's Kaspa bridge, which locks KAS in a validator-held multisig on Kaspa and mints a representation on the Hub. A later proposal (38, February 2026) enrolled a Solana route for that token.
- Proposal:passed (proposal 32)
- Implementation:module shipped in v4.0.0
- Release:released with the Beyond upgrade
- Activation:bootstrapped on mainnet by proposal 32
Sources: Dymension Hub governance via NodeStake public API — Proposal 32: Bootstrap KAS Module (external site) · Dymension forum (Dymension team) — Dymension Kaspa Bridge Design Details (external site) · Dymension blog — Kaspa Meets Dymension (external site) · Dymension Hub governance via NodeStake public API — Proposal 38: Enroll KAS Solana remote router (external site) · Dymension Hub via NodeStake public API — Hyperlane security modules and signer thresholds (live Hub query) (external site)
-
dymd v4.0.1 released with a fix for the eth_gasPrice query
Dymension contributors published dymd v4.0.1 on 2025-11-24, a week after v4.0.0. The release notes list one change: a fix for the eth_gasPrice query in the Hub's Ethereum-style JSON-RPC interface, which they describe as malformed (pull request 2114). The notes say the release does not break consensus and can be installed without coordination.
- Implementation:fix merged as pull request 2114
- Release:released 2025-11-24 as v4.0.1
- Activation:no network activation; each operator installs it, and the notes say no coordination is needed
Sources: Dymension contributors — Dymension v4.0.1 release notes (external site) · Dymension contributors — Dymension Hub releases Atom feed (external site)
-
Governance approved and applied the Beyond upgrade (dymd v4.0.0)
Proposal 31 passed on 2025-11-22 and the upgrade plan it scheduled is recorded on chain as applied at height 10,192,266. The release adds Hyperlane routes, a Kaspa bridge module, hardware-attested fast finality for RollApps, IBC rate limits, non-DYM base assets for pools and several launchpad and incentive changes.
- Proposal:passed (proposal 31)
- Implementation:released as v4.0.0; later patches v4.0.1 and v4.0.2
- Release:released 2025-11-17
- Activation:applied on mainnet at height 10,192,266
Sources: Dymension Hub governance via NodeStake public API — Proposal 31: Beyond software upgrade (external site) · Dymension Hub via NodeStake public API — Applied upgrade plan v5 (live Hub query) (external site) · Dymension forum — [PROP# 31] [APPROVED] The RENEWED Beyond Upgrade (external site) · Dymension contributors — Dymension v4.0.0 release notes (external site) · Dymension Hub via NodeStake public API — Node and application version (live Hub query) (external site) · Dymension Hub via NodeStake public API — Latest Hub block (live Hub query) (external site)
Topics your AI can explain
Your AI can explain these topics for Dymension through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Ledger support for Dymension was not verified: Ledger coin-page addresses tried returned 404 and no Ledger page naming Dymension was found.
- The docs describe a permissionless fraud-proof transaction as still in final testing; the reviewed v4.0.2 code routes fraud claims through Hub governance. Whether any RollApp has ever been disputed was not checked.
- The dispute window is set in blocks. Dymension's blog calls it seven days, but at block speeds measured from July to September 2026 it would last roughly 34 to 39 days, and one RollApp's state update from 2026-09-10 was still pending on 2026-09-27. The exact wall-clock length was not confirmed from a finalized example.
- The cause of the slower-than-targeted block interval after the Beyond upgrade was not investigated.
- A live query found about 10% of DYM supply bonded, while a December 2025 proposal cited about 43%; the reason for the drop was not investigated.
- Parts of the docs are out of date against the chain: the integration page lists older Cosmos SDK and CometBFT versions, the supply page gives a 50% staking target while the chain parameter is 30% after proposal 35, and the sequencer penalty page says hourly while the chain counts Hub blocks.
- Most launched RollApps had stopped posting state updates by September 2026. Why, and whether funds bridged into them can still be withdrawn, was not reviewed.
- The latest state updates of launched RollApps named Celestia (22) or Avail (2) for data; the security of each data network was not reviewed.
- The Hub-side signer thresholds for Hyperlane and the Kaspa bridge were read on chain, but who holds those keys, whether the accounts that own the signer lists can change them, and the settings on the other chains were not reviewed.
- The Kaspa-side escrow threshold was not checked on the Kaspa network; the design post names 5 of 9, while the Hub accepts Kaspa messages with 8 of 15 signatures.
- Rollups that post data to Kaspa, and fee payment in non-DYM assets, are described in team posts but were not confirmed live.
- Who operates the approved hardware-attestation image for fast RollApp finality was not reviewed. The one RollApp with it enabled last posted a state update in March 2026.
- Atomic swaps, reversible or delayed transfers and recovery, channel layers and algorithmic stablecoins were not found or not reviewed.
- Only three of the 14 registry explorers were opened, plus the two that failed; the rest were not checked.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Dymension Hub chain registry record (external site)
- Glossary (external site)
- Node FAQs (external site)
- DYM demand (monetary policy) (external site)
- Fraud Proofs (external site)
- Data Availability (external site)
- Transfer security (external site)
- Censorship Resistance (external site)
- Withdraw (external site)
- Liquidity pools overview (external site)
- RollApps overview (external site)
- dymensionxyz/dymension repository (external site)
- Dymension v4.0.0 release notes (external site)
- Rollapp fraud proposal handler (v4.0.2) (external site)
- Byzantine Consensus Algorithm (external site)
- IBC overview (external site)
- Staking parameters (live Hub query) (external site)
- Slashing parameters (live Hub query) (external site)
- Bonded validators (live Hub query) (external site)
- Node and application version (live Hub query) (external site)
- EVM module parameters (live Hub query) (external site)
- Rollapp module parameters (live Hub query) (external site)
- Registered RollApps (live Hub query) (external site)
- Hyperlane token registry (live Hub query) (external site)
- Hyperlane security modules and signer thresholds (live Hub query) (external site)
- First state update of RollApp nftmainnet_292929-1, still pending (live Hub query) (external site)
- Latest state update of RollApp odysphere_224126-1, posted to Avail (live Hub query) (external site)
- Proposal 38: Enroll KAS Solana remote router (external site)
- Dymension Explorer (external site)
- IBC denomination trace for USDC (live Hub query) (external site)
- IBC denomination trace for USDT (live Hub query) (external site)
- Proposal 33: Add KAS as a base asset (external site)
- Proposal 40: Remove IBC rate limits for Noble USDC and Kava USDT (external site)
- [PROP# 31] [APPROVED] The RENEWED Beyond Upgrade (external site)
- Dymension Kaspa Bridge Design Details (external site)
- TEE-Backed Fast Cross-Chain Transfers (external site)
- Dymension Node Snapshot (external site)
- USDC contract addresses (external site)
- Supported protocols (external site)
- Dymension wallet (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