Layer 1 blockchain

IoTeX ticker IOTX

No public-data lookups yet
4 reviewed developments
40 cited sources

Summary

IoTeX calls its consensus Roll-DPoS (randomized delegated proof of stake). IOTX holders stake at least 100 IOTX in buckets and vote for delegates; the 36 delegates with the most votes are consensus delegates, and each hourly epoch 24 of them produce blocks in turn. A proposed block is final once over two-thirds of those 24 (at least 17) endorse it in a PBFT-type vote, and blocks have come every 2.5 seconds since the Wake hard fork of June 2025. Delegates below 85% productivity in an epoch go on probation for six epochs and, since the Xingu hard fork of November 2025, lose self-stake equal to the block reward times the blocks they missed. In February 2026 the delegates halted the chain for about 68 hours after an exploit of IoTeX's ioTube bridge and restarted it with a node release that blacklists attacker addresses. 2 3 16 17 21 22 27 29

Design

System: Layer 1 blockchainIndependent proof-of-stake chain, live since April 2019, run by elected delegates; it does not settle to another chain. Its node software, iotex-core, is IoTeX's own Go implementation that embeds a forked Ethereum library to run an EVM, so contracts, 0x addresses and Ethereum JSON-RPC tools work, while staking, delegate elections, rewards and the io1 address format are IoTeX's own. IoTeX 2.0 adds DePIN infrastructure modules and a planned app-chain kit on top of this base chain.
Settlement family: Its own design
Scarce resource: Stake (proof of stake)
State model: Accounts
Finality: Other
Who makes blocks: Within an epoch the 24 active delegates propose in fixed rotation by block height. IoTeX's docs and EU white paper say the 24 are drawn from the top 36 with a verifiable random function; in the reviewed node code they are ordered by hashing each address with a hard-coded seed and the epoch start height, which anyone can compute in advance, and the code comment calls the seed a placeholder to be replaced. Delegate candidacy needs a 1.2 million IOTX self-stake (or an endorsement covering it).
Fork choice: No open weight-based chain selection. A block is appended only with endorsements from over two-thirds of the epoch's 24 delegates, counted one per delegate, and IoTeX's consensus docs describe this as instant block finality. If a third or more of the 24 stop endorsing, no block can reach the threshold, so the chain stops and does not fork (an inference from the threshold rule).

Qualifications

Settlement family · Partial. Recorded as other. IoTeX's own terms: Roll-DPoS run by iotex-core, IoTeX's own Go node software, with native actions for transfers, contract execution and staking, staking buckets that vote for delegates, and one account shown in two address formats (io1 and 0x); smart contracts run on an EVM through an embedded, forked Ethereum library.
Finality · Partial. Recorded as other. IoTeX's own terms: Roll-DPoS single-block finality. A block is final once over two-thirds of the epoch's 24 active delegates endorse it, one vote per delegate. The protocol penalizes missed blocks (IIP-50) but the reviewed sources show no penalty for signing conflicting blocks, so this is not recorded as stake-backed economic finality.
Committee randomness · Contested. IoTeX's docs and EU white paper say a verifiable random function picks the 24 producers each epoch. The reviewed iotex-core code orders the top 36 by a hash of each address, a hard-coded seed and the epoch start height, so the selection can be computed in advance; the code comment calls the seed a placeholder.
Slashing · Partial. Since the Xingu hard fork (v2.3.0, November 2025) a delegate under 85% productivity in an epoch loses self-stake equal to the block reward times its missed blocks and goes on probation (IIP-50). IoTeX's EU white paper also claims up to 5% slashing for double signing; no such rule was found in the reviewed IIPs or release notes.
Censorship resistance · Contested. After the February 2026 ioTube exploit, delegates halted the chain from 21 to 24 February and restarted it on v2.3.4, which blacklists 29 attacker addresses in the node; IoTeX called the freeze permanent. v2.5.0 schedules the Zanzibar hard fork (block 53,533,081, estimated 19 October 2026), which stops treating 13 of the 29 as blacklisted.
Fee burn · Contested. IoTeX's EU white paper says the base part of each fee is burned. In the reviewed node code the base fee is deposited into the protocol's rewarding fund, which pays delegate and voter rewards, and the priority fee passes through that fund to the block's producer on top of the fixed block reward; no burn of the base fee was found.
Evm compatibility · Partial. IoTeX runs an EVM with the Cancun opcodes and blob transactions since the Vanuatu hard fork (December 2024) and four Pectra changes since the Yap hard fork (June 2026). It sets its own calldata pricing, applies an abuse-prevention blacklist to delegated-code accounts, keeps staking and elections as native protocol actions, and its docs page still names an older EVM release.
Tps · Contested. The only throughput figures are IoTeX's design claims without a published method; they are kept in the classified claims list and are not comparable with observed rates.

Tradeoffs

This view follows one way of thinking about design priorities, often called the blockchain trilemma. The design-priorities lesson sets out the counter-view. Read the design-priorities lesson.

Emphasizes

Scalability and Security Contested

Gives up

Open block production. Only the 36 most-voted delegates can produce blocks and 24 do so each hour, chosen in an order anyone can compute in advance. In February 2026 the delegates halted the chain for about 68 hours and restarted it with a node release (v2.3.4) that blacklisted 29 addresses; the next hard fork (Zanzibar, scheduled for October 2026) lifts 13 of those entries. This shows that the delegate set, coordinating with IoTeX's core team, can stop the chain and freeze accounts.IoTeX's docs describe the network as decentralized and permissionless and advertise single-block finality and a throughput figure that is kept, with its caveats, in the classified throughput claims; IoTeX's 2025 review cites a Nakamoto coefficient of 9, a figure not checked here. Reading these claims as all three corners at once is contested. The reviewed sources show a penalty only for missed blocks, not for signing conflicting blocks, which weakens the stake-at-risk side of the security argument.

Full node at home

Demanding 14 15 33IoTeX publishes hardware only for delegates: 64 GB of RAM, 500 GB of SSD or NVMe storage, an 8-core CPU and a 1 Gbit connection are recommended, with a backup node. The node guide starts new nodes from a snapshot of about 190 GB downloaded from IoTeX's storage, which means trusting that snapshot; syncing from genesis also needs legacy delegate-election data from Ethereum or a downloaded copy. No separate specification for a non-producing full node was found, and IoTeX's EU white paper gives much lower figures that were not reconciled.

Throughput claims

Theoretical peak: 2,000 tx/s 1 21 30Theoretical peak; not comparable across chains or with observed load.IoTeX's docs state 2,000+ TPS and its 2025 review says IIP-42 doubled throughput to that figure (the review attributes it to v2.3.0, while the release notes put IIP-42 in v2.2.0, the Wake hard fork); no method, transaction mix, window or hardware assumption is published. The figure follows from halving the block interval to 2.5 seconds, a design change, not from a measured load. IoTeX's own sources disagree: the iotex-core repository description still says 1,000 TPS, and the EU white paper gives both 1,000 and 2,000. No observed rate was measured for this profile.
Theoretical peak: 10,000,000 19 26Theoretical peak; not comparable across chains or with observed load.Gas per second: a 25 million gas block limit every 2.5 seconds (IIP-42).This is a protocol ceiling from the block gas limit and interval, not observed use. How many transactions fit depends on their gas cost; a gas ceiling is not a transaction rate.

Headline figures are not comparable across chains. A theoretical peak is never a like-for-like number.

Scaling layers

ioDDK DePIN app chains (described in the IoTeX 2.0 white paper) · Unknown family, research 32
The June 2024 IoTeX 2.0 white paper describes ioDDK as a kit for DePIN projects to launch their own chains that anchor to the IoTeX L1 and draw security from the Modular Security Pool. No live ioDDK chain, and no fraud-proof or validity-proof design, was verified, so its trust model and scaling family are unknown. (as of Sep 29, 2026)

Capabilities

Capabilities of IoTeX: how each one is provided, or its research status
Capability	How it is provided	Notes and sources
Account abstraction	Structured assessment pending	Not yet assessed for any chain.
Atomic swaps	Unknown	No hash-time-locked or other trust-minimized swap contract documented for IoTeX was reviewed; the EVM could host one, but that is a building block only. IoTeX's EU white paper says ioTube supports atomic token swaps, but ioTube releases tokens on signatures from at least two-thirds of its witnesses, which is a bridge, not a two-party swap. 31 33
Authenticated data publication	Built into the protocolLimited scope	Since the Vanuatu hard fork (v2.1.0, December 2024) blob transactions carry data whose commitments the chain records in the transaction; nodes serve the blob data through the eth_getBlobSidecars method, and IoTeX's guide shows readers checking the data against the commitments with KZG proofs. Limited: blob data is kept for about 20 days, and no way to discover later versions of published data is documented. 6 18 20
Light clients	Unknown	No light client that checks delegate endorsements was found. IoTeX's embedded-device SDK reads the chain through a JSON-RPC gateway, which means trusting that gateway, and the EU white paper lists FlyClient light-client proofs only as a planned upgrade. The same paper says ioTube lets other chains check IoTeX block headers with light-client proofs, but ioTube's architecture docs describe releases on attestations from two-thirds of its witnesses. 7 31 33
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 network on IoTeX was found in the reviewed sources.
Programmable spending	Native (protocol or core-team software) Earlier definition	Smart contracts run on IoTeX's EVM and pay gas in IOTX, with Cancun opcodes since v2.1.0 and delegated code for ordinary accounts (EIP-7702) since the Yap hard fork in June 2026. IoTeX's docs also support smart-contract accounts under ERC-4337 version 0.6.0. These are contract accounts and delegated code, not spend conditions in the native transfer action. 4 5 20 24
Protocol-verified messaging	Structured assessment pending	Not yet assessed for any chain.
Reversible transfers or recovery	Unknown	No protocol path for a sender to cancel a payment, and no live recovery wallet on IoTeX, was reviewed. Smart-contract accounts and delegated code are building blocks only. The February 2026 address blacklist was an emergency node release coordinated with delegates, not a feature users can invoke. 5 23
Rollups	Unknown	No rollup anchored to IoTeX was verified. IoTeX's guide presents blob transactions for rollup data, and the IoTeX 2.0 white paper describes ioDDK chains anchored to IoTeX, but no live rollup was found. 6 32
Shielded transfers	Structured assessment pending	Not yet assessed for any chain.
Signed partial offers	Unknown	Not yet assessed under this row's current definition; no maker-signed trade format settled by IoTeX's protocol was found in the reviewed sources.

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.

Definitions, schema version and review history

Ecosystem & custody

Ecosystem products for IoTeX
Product type	Status	Notes and sources
Automated market makers	Thinmimo (V2 and V3), MinMax Finance, PinSwap, Loxodrome, iZiSwap	IoTeX's docs describe mimo as a decentralized exchange built from Uniswap code, with liquidity pools, a DePIN liquidity hub and an NFT marketplace. DeFiLlama lists mimo V2 and V3 as IoTeX-only exchanges, plus smaller venues and the multichain iZiSwap. Operators, audits and liquidity depth were not reviewed. 12 34 As of Sep 29, 2026.
Issuer-native stablecoins	None found	Neither Circle's USDC list nor Tether's supported-protocol list includes IoTeX. The dollar tokens on IoTeX, USDC.e (formerly ioUSDC) and ioUSDT, are bridged through ioTube; about $4.4 million of the Ethereum-side reserves behind ioTube was drained in the February 2026 exploit, and the IoTeX Foundation says it is compensating affected holders. 13 29 35 36 As of Sep 29, 2026.
Algorithmic stablecoins	Unknown	DeFiLlama lists collateralized-debt protocols on IoTeX (xDollar, Magma Finance); none was reviewed, and no algorithmic stablecoin with material use was verified. 34 As of Sep 29, 2026.
Bridges	UnknownioTube (IoTeX's bridge; paused after the February 2026 exploit, current route status not verified)	ioTube, published by IoTeX, moves tokens between IoTeX and Ethereum, BNB Smart Chain, Polygon and Solana by locking or burning on one side and minting on the other. After the February 2026 exploit IoTeX paused it pending a security review and says its contracts moved to multi-signature control. IIP-56 permanently shut the CIOTX routes from Ethereum, Base and Solana; the BNB Smart Chain and Polygon routes were to reopen only for migration. No reopening was verified, so whether any transfer works today is unknown. IIP-57, a proof-based bridge, is a draft. Risk: ioTube mints on signatures from at least two-thirds of its witnesses, so users trust the witnesses and whoever controls the bridge contracts. In February 2026 an attacker who had compromised an IoTeX employee's machine upgraded the Ethereum-side validator contract, minted 410 million CIOTX and drained about $4.4 million of reserves. A wrapped asset is only as sound as the bridge that minted it. 9 28 29 31 As of Sep 29, 2026.
Block explorers	First-partyIoTeXScan	IoTeX's docs call IoTeXScan the official explorer; it also serves a keyless, rate-limited API that follows the Etherscan request format, which answered block-height reads on 2026-09-29. No independent second explorer was reviewed. Listing is not a quality or completeness check. 10 11 As of Sep 29, 2026.
Hardware wallets	ThinLedger (through MetaMask, Rabby or IoTeX Hub), Trezor (through MetaMask or Rabby)	See custody rows: both vendors' devices sign for the IoTeX network through other wallets, and neither vendor's current wallet code lists the IoTeX network. 8 38 39 40 As of Sep 29, 2026.

Hardware-wallet custody

Hardware-wallet custody for IoTeX
Device maker	Status	What users can and cannot do
Ledger	Through an intermediaryMetaMask or Rabby with the Ledger Ethereum app, or IoTeX Hub with the IoTeX Ledger appSame as native: Unknown	Can: Sign native IOTX transfers, token transfers and staking actions on IoTeX from MetaMask or Rabby with the Ledger Ethereum app, which IoTeX's Ledger guide names as the preferred setup Can: Use the IoTeX Ledger app with the IoTeX Hub and staking portals, which IoTeX's docs describe for users of its older Ledger integration Cannot: Manage native IOTX on the IoTeX network in Ledger Live: IoTeX's guide says Ledger Live handles IOTX only as an ERC-20 token on other chains Cannot: Find an IoTeX network or chain ID 4689 in Ledger's published currency list (@ledgerhq/cryptoassets 13.56.0)Ledger's IoTeX page (modified 2026-02-20) is a generic template inviting users to manage IoTeX in Ledger Wallet, but Ledger's own currency list has no IoTeX network, so the documented working paths run through MetaMask, Rabby or IoTeX Hub. 8 37 38 As of Sep 29, 2026.
Trezor	Through an intermediaryMetaMask or Rabby (listed on Trezor's IoTeX page)Same as native: Unknown	Can: Use a Trezor with MetaMask or Rabby on the IoTeX network; Trezor's IoTeX page lists Trezor Suite, MetaMask and Rabby as wallet apps and IoTeX, Ethereum and Base as networks, without saying which app covers which network Cannot: Add the IoTeX network in Trezor Suite: Suite's current network list (develop branch, read 2026-09-29) has no IoTeX entryTrezor's IoTeX page also tells users to receive IOTX in Trezor Suite; with no IoTeX network in Suite's code, that path appears to cover IOTX tokens on Ethereum and Base (an inference). IoTeX's own wallet docs cover Ledger but not Trezor. 39 40 As of Sep 29, 2026.

Public data

iKnow Blockchain has no public-data lookups for IoTeX yet. This is a limit of the service, not a statement about the network.

Public-data lookups for IoTeX
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.

A lookup covers one address or transaction from one provider. It is never a complete wallet, and an error or private value is reported as unknown, not zero. About public data · Connect your AI

Sourced developments

Developments: Reviewed Sep 29, 2026 Next review due Oct 9, 2026, 12:00 UTC.

Publication date · newest first

Published Sep 28, 2026ProtocolVerified against sources

iotex-core v2.5.0 schedules the Zanzibar hard fork: protocol-paid voter rewards and partial blacklist removal

IoTeX released node version 2.5.0, required before mainnet block 53,533,081 (estimated 19 October 2026 02:00 UTC, moved from an earlier schedule for 8 October). The Zanzibar hard fork moves voter reward payouts from the Hermes service into the protocol (IIP-59), requires BLS proof of possession when candidates register, makes the BLS key optional, applies several execution and staking corrections (on mainnet the Beta and Gamma corrections activate at the same block) and stops treating 13 of the 29 addresses blacklisted in February 2026 as blacklisted.
- Proposal:IIP-59, created 2026-03-20, updated 2026-08-07
- Implementation:shipped in iotex-core v2.5.0; active on testnet since August and September 2026
- Release:required release published 2026-09-28
- Activation:scheduled for mainnet block 53,533,081 (estimated 2026-10-19); not yet active at review
Date basis: GitHub release timestamp 2026-09-28T02:34Z; the release note gives the activation block and estimated date.

Sources: IoTeX (GitHub) — iotex-core v2.5.0 release (external site) · IoTeX (iotex-bootstrap, GitHub) — v2.5.0 release note (Zanzibar hard fork) (external site) · IoTeX Improvement Proposals (GitHub) — IIP-59: Protocol-Native Voter Reward Distribution (external site) · IoTeX (GitHub) — IoTeX Delegate Manual (iotex-bootstrap README) (external site)
Published May 7, 2026ProtocolVerified against sources

iotex-core v2.4.0 shipped the Yap hard fork: four Pectra changes and a delegate exit queue

IoTeX released node version 2.4.0, a mandatory upgrade activating at block 48,985,561 (estimated 7 June 2026). Under IIP-60 it adds delegated code for ordinary accounts (EIP-7702) with an IoTeX abuse-prevention blacklist, a calldata cost floor, recent block hashes kept in state and BLS12-381 precompiles. It also replaces immediate delegate exits with a queue that admits at most one departing candidate every 24 epochs (the default interval); the candidate's self-stake stays locked from the exit request until the scheduled exit height is reached and the owner confirms the exit. A mandatory fix, v2.4.1, followed on 14 May 2026.
- Proposal:IIP-60, created 2026-01-08
- Implementation:shipped in iotex-core v2.4.0, with fixes in v2.4.1
- Release:mandatory release published 2026-05-07
- Activation:scheduled for block 48,985,561 (estimated 2026-06-07); mainnet was past that height on 2026-09-29
Date basis: GitHub release timestamp 2026-05-07T23:21Z; the release page gives the activation block and estimated date.

Sources: IoTeX (GitHub) — iotex-core v2.4.0 release (Yap hard fork) (external site) · IoTeX (iotex-bootstrap, GitHub) — v2.4.0 release note (Yap hard fork) (external site) · IoTeX Improvement Proposals (GitHub) — IIP-60: Enable Ethereum Pectra Upgrade (external site) · IoTeX (iotex-bootstrap, GitHub) — v2.4.1 release note (external site) · IoTeX Foundation — IoTeX mainnet Ethereum JSON-RPC endpoint (read 2026-09-29) (external site)
Published Feb 23, 2026ProtocolVerified against sources

Delegates halted IoTeX after the ioTube bridge exploit and restarted it with an address blacklist

On 21 February 2026 an attacker upgraded ioTube's Ethereum-side validator contract with a stolen owner key, minted 410 million CIOTX and drained about $4.4 million of bridge reserves. IoTeX says its delegates suspended the chain the same day. They restarted it on 24 February at 06:06 UTC on node release v2.3.4, which blacklists 29 attacker addresses; v2.3.5 enforces the list from block 45,404,174. IIP-56 later deprecated CIOTX on every network, and the IoTeX Foundation opened a claims portal to compensate affected holders.
- Implementation:blacklist shipped in iotex-core v2.3.4; height-gated enforcement added in v2.3.5
- Release:v2.3.4 published 2026-02-23 (its release note labels it recommended) and run by delegates to restart the chain
- Activation:chain resumed 2026-02-24 06:06 UTC per IoTeX; enforcement from block 45,404,174
Date basis: IoTeX blog post timestamped 2026-02-23T07:14Z and GitHub release v2.3.4 dated 2026-02-23; later posts give the halt and restart times.

Sources: IoTeX blog — Security Incident Update: ioTube Bridge Exploit and Recovery Roadmap (external site) · IoTeX blog — ioTube Bridge Incident Update No.2: Chain Resumed, Recovery Underway (external site) · IoTeX (iotex-bootstrap, GitHub) — v2.3.4 release note (external site) · IoTeX (iotex-bootstrap, GitHub) — v2.3.5 release note (external site) · IoTeX blog — How IoTeX Responded to the ioTube Bridge Incident: A Full Month in Review (external site) · IoTeX Improvement Proposals (GitHub) — IIP-56: Deprecation of CIOTX Across All Networks (external site)
Published Oct 22, 2025ProtocolVerified against sources

iotex-core v2.3.0 scheduled the Xingu hard fork, which penalizes delegates that miss blocks

IoTeX released node version 2.3.0, a mandatory upgrade that enables IIP-50: a delegate whose block production falls below 85% in an epoch loses self-stake equal to the block reward times the blocks it missed, and is dropped from the delegate list if its self-stake falls below 1 million IOTX. The release also lets delegates register BLS public keys, preparing for aggregated block signatures (IIP-52). Activation was set for block 41,648,761, estimated for 4 November 2025.
- Proposal:IIP-50, created 2025-07-02; the file's status field still reads draft
- Implementation:shipped in iotex-core v2.3.0
- Release:mandatory release published 2025-10-22
- Activation:scheduled for block 41,648,761 (estimated 2025-11-04); mainnet was past that height on 2026-09-29
Date basis: GitHub release timestamp 2025-10-22T02:13Z; the release page gives the activation block and its estimated date.

Sources: IoTeX (GitHub) — iotex-core v2.3.0 release (Xingu hard fork) (external site) · IoTeX Improvement Proposals (GitHub) — IIP-50: Slash Underperforming Delegates (external site) · IoTeX (iotex-core, GitHub) — blockchain/genesis/genesis.go (external site) · IoTeX Foundation — IoTeX mainnet Ethereum JSON-RPC endpoint (read 2026-09-29) (external site)

Topics your AI can explain

Your AI can explain these topics for IoTeX through the connection, with sources.

What IoTeX is: a delegated proof-of-stake chain for DePIN
Roll-DPoS: staked votes, 36 delegates and a 24-member committee
Accounts, actions and the IoTeX EVM
Fees, gas and units on IoTeX
Finality in one block, and what happens when delegates stop
Running an IoTeX node: iotex-core, snapshots and delegate hardware
Wallets and hardware-wallet custody for IOTX
The ioTube bridge and the February 2026 exploit
IoTeX 2.0: DePIN Infrastructure Modules and the Modular Security Pool

Known gaps

What this profile's review did not establish:

Who operates each consensus delegate and how much stake the largest delegates control were not measured; IoTeX's own Nakamoto-coefficient figure of 9 was not checked.
The docs and EU white paper say a verifiable random function selects the 24 producers; the reviewed code uses a hard-coded seed. Whether another randomness path is active at current mainnet heights was not exhaustively checked.
No penalty for signing conflicting blocks was found in the reviewed IIPs, release notes or code; the EU white paper's claim of up to 5% slashing for double signing was not reconciled.
The EU white paper says base fees are burned while the reviewed code deposits them into the rewarding fund; the fund's balance and actual fee flows were not measured on chain.
Current IOTX supply and yearly staking emission were not verified; IoTeX's token page says tokenomics are being updated for IoTeX 2.0.
Hardware needs for a non-producing full node are not published; the delegate specification was used.
How much blob data mainnet actually carries, and how long nodes keep it in practice, was not tested. IoTeX's release note and guide say about 20 days and the node's default setting keeps 21 days, but the protocol's minimum window of 345,600 blocks, set when blocks came every 5 seconds, now spans about 10 days.
Whether any ioTube route has reopened since the February 2026 pause, and who now holds the multi-signature upgrade control IoTeX describes over the bridge contracts, were not verified.
Zanzibar (v2.5.0) is scheduled for block 53,533,081, estimated 19 October 2026; its activation, and which 16 addresses stay blacklisted, were not checked.
How the February 2026 halt and blacklist were approved (delegate vote, IIP or core-team decision) was not documented in the reviewed sources.
Trezor Suite's handling of IOTX was read from its code, and Ledger Live's from IoTeX's guide; neither was tested with a device.
No light client, atomic swap contract, recovery wallet, rollup or channel network was found; absence was not exhaustively verified.
The throughput figures have no published method, and no observed rate was measured.
mimo's operator, audits and liquidity depth were not reviewed.

Sources

Oldest dated source check: Source checked Sep 29, 2026 Next check due Oct 29, 2026.

All 40 sources were checked in the last 30 days.

IoTeX L1 Blockchain (external site)IoTeX Documentation · retrieved Sep 29, 2026
Roll-DPoS Consensus (external site)IoTeX Documentation · retrieved Sep 29, 2026
Voters and Delegates (external site)IoTeX Documentation · retrieved Sep 29, 2026
EVM Compatibility (external site)IoTeX Documentation · retrieved Sep 29, 2026
Accounts & Identities (external site)IoTeX Documentation · retrieved Sep 29, 2026
Blob Transactions (EIP-4844) (external site)IoTeX Documentation · retrieved Sep 29, 2026
Embedded Blockchain Clients (external site)IoTeX Documentation · retrieved Sep 29, 2026
Ledger Nano S & X (external site)IoTeX Documentation · retrieved Sep 29, 2026
iotube Bridge (external site)IoTeX Documentation · retrieved Sep 29, 2026
iotexscan Explorer (external site)IoTeX Documentation · retrieved Sep 29, 2026
IoTeXscan API (external site)IoTeX Documentation · retrieved Sep 29, 2026
mimo DEX (external site)IoTeX Documentation · retrieved Sep 29, 2026
Mainstream Assets (bridged assets on IoTeX) (external site)IoTeX Documentation · retrieved Sep 29, 2026
Hardware Specs (external site)IoTeX Delegate Documentation · retrieved Sep 29, 2026
IoTeX Delegate Manual (iotex-bootstrap README) (external site)IoTeX (GitHub) · retrieved Sep 29, 2026
crypto/cryptosort.go: candidate ordering with a hard-coded seed (external site)IoTeX (iotex-core, GitHub) · retrieved Sep 29, 2026
consensus/scheme/rolldpos/roundctx.go: two-thirds endorsement rule (external site)IoTeX (iotex-core, GitHub) · retrieved Sep 29, 2026
api/web3server.go: Ethereum JSON-RPC methods including eth_getBlobSidecars (external site)IoTeX (iotex-core, GitHub) · retrieved Sep 29, 2026
blockchain/genesis/genesis.go: mainnet parameters and hard-fork heights (external site)IoTeX (iotex-core, GitHub) · retrieved Sep 29, 2026
v2.1.0 release note (Vanuatu hard fork: Cancun, blob and dynamic-fee transactions) (external site)IoTeX (iotex-bootstrap, GitHub) · retrieved Sep 29, 2026
v2.2.0 release note (Wake hard fork: 2.5-second blocks, IIP-42) (external site)IoTeX (iotex-bootstrap, GitHub) · retrieved Sep 29, 2026
iotex-core v2.3.0 release (Xingu hard fork: IIP-50 delegate slashing) (external site)IoTeX (GitHub) · retrieved Sep 29, 2026
v2.3.4 release note (default address blacklist) (external site)IoTeX (iotex-bootstrap, GitHub) · retrieved Sep 29, 2026
v2.4.0 release note (Yap hard fork: Pectra changes, candidate exit queue) (external site)IoTeX (iotex-bootstrap, GitHub) · retrieved Sep 29, 2026
v2.5.0 release note (Zanzibar hard fork: IIP-59, blacklist removal) (external site)IoTeX (iotex-bootstrap, GitHub) · retrieved Sep 29, 2026
IIP-42: Halving Blocktime and Doubling the TPS of the IoTeX L1 (external site)IoTeX Improvement Proposals (GitHub) · retrieved Sep 29, 2026
IIP-50: Slash Underperforming Delegates (external site)IoTeX Improvement Proposals (GitHub) · retrieved Sep 29, 2026
IIP-56: Deprecation of CIOTX Across All Networks (external site)IoTeX Improvement Proposals (GitHub) · retrieved Sep 29, 2026
How IoTeX Responded to the ioTube Bridge Incident: A Full Month in Review (external site)IoTeX blog · retrieved Sep 29, 2026
IoTeX 2025 in Review (external site)IoTeX blog · retrieved Sep 29, 2026
ioTube: Overview and Architecture (external site)ioTube Documentation · retrieved Sep 29, 2026
IoTeX 2.0 - DePIN for Everyone! (white paper, 18 June 2024) (external site)IoTeX · retrieved Sep 29, 2026
IoTeX (IOTX) crypto-asset white paper under EU Regulation 2023/1114 (dated 2025-10-05) (external site)IoTeX Foundation · retrieved Sep 29, 2026
DeFiLlama protocols API (IoTeX entries: ioTube, mimo, MinMax Finance, xDollar, Magma Finance and others) (external site)DeFiLlama · retrieved Sep 29, 2026
USDC contract addresses (external site)Circle · retrieved Sep 29, 2026
Supported protocols (external site)Tether · retrieved Sep 29, 2026
IoTeX Wallet - Buy, manage & hold your IOTX (external site)Ledger · retrieved Sep 29, 2026
@ledgerhq/cryptoassets 13.56.0 currency list (external site)Ledger (npm package via jsDelivr) · retrieved Sep 29, 2026
Safe & secure IoTeX wallet (external site)Trezor · retrieved Sep 29, 2026
Trezor Suite network list (suite-common/legacy-network-config/src/networksConfig.ts, develop branch) (external site)Trezor (trezor-suite, GitHub) · retrieved Sep 29, 2026

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.

Report an error about IoTeX Corrections 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