IoTeX

What is IoTeX?

IoTeX is an EVM-compatible Layer 1 blockchain and middleware stack built to verify real-world machine data, device identity, and off-chain computation for decentralized physical infrastructure networks, or DePIN, and emerging “real-world AI” applications.

Its core problem is the “oracle-to-physical-world” gap: blockchains can verify digital state, but AI agents, DeFi contracts, insurers, mobility networks, energy markets, and robotics systems need credible data from sensors, devices, and machines that operate outside the chain. IoTeX’s claimed moat is not simply block production; it is the combination of a purpose-built L1, device identity through ioID, off-chain verifiable compute through W3bstream and related DePIN infrastructure modules, and hardware-oriented work around secure elements and trusted execution environments described in the project’s technical documentation and IoTeX 2.0 whitepaper. (docs.iotex.io)

Who Founded IoTeX and When?

IoTeX was founded in 2017, near the peak of the first major ICO cycle, when many Layer 1 projects were raising capital on the thesis that specialized blockchains could outperform Ethereum for targeted use cases.

In a project interview, CEO and co-founder Raullen Chai described the founding context as a late-2017 effort by himself, Jing Sun, and Qevan Guo to build a blockchain interface between crypto and the physical world; other company-profile sources and project materials also list Xinxin Fan as part of the founding or core technical team, particularly around cryptography and IoT security.

That distinction matters because IoTeX’s early credibility came less from consumer adoption and more from technical specialization: security engineering, machine learning, venture formation, and IoT hardware were central to the project’s original framing. (blog.iotex.io)

The narrative has evolved materially. IoTeX began as an “Internet of Trusted Things” blockchain focused on privacy-preserving IoT, secure devices, and machine-owned data; it later expanded into a DePIN infrastructure narrative after 2021 and, by 2024–2026, repositioned toward real-world AI, where verified device data is treated as input for AI agents and autonomous systems.

The project’s EU whitepaper describes this progression from blockchain-for-IoT to DePIN and modular infrastructure, while the 2026 “anti-roadmap” reframes the product challenge around whether IoTeX can become AI’s interface to the physical world and create sustainable demand for live machine data.

That repositioning is coherent with market trends, but it also raises execution risk because each narrative shift expands the competitive set. (cdn.iotex.io)

How Does the IoTeX Network Work?

IoTeX is a standalone, EVM-compatible Layer 1 using Randomized Delegated Proof of Stake, or Roll-DPoS, rather than proof-of-work or a monolithic validator set. Under Roll-DPoS, IOTX holders stake and vote for delegates; the top delegates form the candidate set, and consensus delegates handle transaction verification and block production. The project’s consensus documentation describes the mechanism as combining delegated proof of stake, PBFT-style finality, and verifiable random functions, with randomized committee selection used to reduce predictability while preserving high throughput and fast finality. The network’s delegate documentation states that the top 36 delegates serve as consensus delegates, while broader staking participation determines voting power and governance influence. (docs.iotex.io)

The distinctive technical layer is the non-consensus stack around real-world data verification. IoTeX’s architecture includes ioID for device identity, W3bstream for off-chain computation over device data, ioConnect and ioDDK for device and app-chain integration, and hardware attestation concepts that reference W3C verifiable credentials, DIDs, Arm TrustZone, and TPM-based trust anchors in its regulatory and technical materials. During the last twelve months, the most concrete protocol upgrades were Mainnet v2.3.0 in November 2025, which introduced slashing mechanisms for unproductive delegates, and Mainnet v2.4.0 “Yap,” activated in June 2026, which brought Pectra-aligned EVM changes such as EIP-7702 and related upgrades plus a candidate exit queue; the follow-on v2.4.1 release was a mandatory staking-package patch for the Yap hard fork. These are meaningful maintenance and compatibility upgrades, but they are not the same as proof of demand for IoTeX’s DePIN data layer. (iotexscan.io)

What Are the Tokenomics of IOTX?

IOTX has a fixed maximum supply of 10 billion tokens, with market aggregators reporting approximately 9.44 billion circulating in early October 2026. The asset exists natively on the IoTeX chain and also through representations on other networks, including the Ethereum ERC-20 contract at 0x6fb3e0a217407efff7ca062d46c26e5d60a14d69 and the Base contract at 0xbcbaf311cec8a4eac0430193a528d9ff27ae38c1, but the native token is the unit used for gas, staking, and network security. The tokenomics are not purely deflationary in the Bitcoin sense: IoTeX materials describe mild inflationary staking rewards balanced against deflationary mechanisms such as EIP-1559-style gas burns and device-registration burns tied to ioID and DePIN module usage. The practical conclusion is that IOTX’s net supply profile depends on whether real network usage and device registration become large enough to offset staking emissions. (coinmarketcap.com)

The token’s value-accrual logic is straightforward but unproven at scale. Users need IOTX to pay transaction fees, deploy contracts, stake and vote for delegates, register devices, obtain credentials, and potentially collateralize or settle activity in DePIN infrastructure modules. The IoTeX token documentation describes gas, staking, delegate election, rewards, and Burn-Drop mechanics, while the IoTeX Hub staking page showed a broad 6%–11% staking reward range in early October 2026. The critical distinction for investors is that staking rewards are protocol incentives rather than claims on issuer revenue, dividends, or cash flow; the project’s EU whitepaper explicitly states that holding IOTX does not create ownership, redemption, dividend, or profit-share rights. (docs.iotex.io)

Who Is Using IoTeX?

IoTeX usage should be separated into three categories: exchange trading, on-chain DeFi, and real-world data infrastructure. Trading volume in IOTX does not necessarily demonstrate demand for IoTeX blockspace, and IoTeX’s DeFi activity remains modest by L1 standards, with DefiLlama listing small TVL, low DEX volume, and protocols such as Mimo, MinMax Finance, and Loxodrome rather than a broad DeFi complex. The stronger adoption claim is in DePIN and real-world-data tooling: DePINscan, powered by IoTeX, tracks DePIN projects and devices, and the project has reported hundreds of DePINs and tens of millions of devices tracked across the broader DePINscan universe. The analytical caveat is important: devices tracked by an IoTeX-powered explorer are not necessarily equivalent to devices transacting directly on the IoTeX L1 or burning IOTX at meaningful scale. (defillama.com)

Enterprise and institutional adoption is credible but should not be overstated. IoTeX completed a Google BigQuery integration to make blockchain data available to Google Cloud users, collaborated with Arm Research on confidential-computing concepts for DePIN and privacy-preserving device data, built the Pebble tracker with Nordic Semiconductor, and lists standards work including IEEE-related contributions through its research page. Samsung-related exposure appears more clearly as Samsung Next’s participation among MachineFi investors rather than evidence that Samsung is operating core IoTeX infrastructure. These relationships support technical legitimacy, but they do not by themselves establish recurring protocol revenue or durable token demand. (blog.iotex.io)

What Are the Risks and Challenges for IoTeX?

Regulatory risk is moderate and mostly generic to crypto assets, staking, and exchange listings rather than centered on a known protocol-specific enforcement action.

This review did not identify an active SEC lawsuit, ETF approval process, or U.S. classification dispute specific to IOTX as of October 9, 2026; however, that should not be read as regulatory immunity. In Europe, IoTeX published a MiCA-oriented whitepaper classifying IOTX as an “other crypto-asset” rather than an asset-referenced token or e-money token, and the same disclosure emphasizes that IOTX does not grant ownership, dividend, redemption, or profit rights. Centralization risk is more concrete: Roll-DPoS improves performance, but the top-36 consensus-delegate structure means block production and governance responsiveness depend on a relatively small elected validator set, even if broader token-holder voting and slashing mechanisms reduce some accountability concerns. (cdn.iotex.io)

Operational and bridge risk became visible in 2026. On February 21, 2026, IoTeX disclosed an ioTube bridge exploit affecting the Ethereum-side bridge and unauthorized CIOTX minting; governance proposal IIP-56 subsequently deprecated CIOTX across networks and established claims and wind-down procedures, while the project stated that legitimate affected holders would be compensated.

The incident did not appear to be a core L1 consensus failure, but it exposed key-management, bridge-design, and liquidity-fragmentation risks that are material for any multi-chain asset ecosystem.

Competitive risk is also substantial: Solana has become a major home for DePIN projects such as Helium, Hivemapper, and Render, IOTA has repositioned around a programmable real-world infrastructure stack, and peaq and other machine-economy networks compete directly for DePIN builders. IoTeX’s challenge is therefore not whether the DePIN theme is relevant, but whether its specialized stack can win developers before larger ecosystems commoditize the same functionality. (iotex.io)

What Is the Future Outlook for IoTeX?

IoTeX’s future depends less on short-term token performance and more on whether it can convert its verified-device and real-world-AI narrative into measurable network demand. The verified roadmap items from the last twelve months show a project maintaining EVM compatibility, adding slashing and delegate-accountability features, patching staking logic after the Yap hard fork, and trying to redesign cross-chain architecture after the ioTube incident, including references in IIP-56 to a future ZK-based bridge approach under IIP-57. The 2026 anti-roadmap is unusually candid in acknowledging that IoTeX must prove who pays for real-world AI data, how the network sustains itself if the core team becomes less central, and whether AI-agent demand can become economically significant rather than promotional. Those are the right questions; the unresolved issue is whether IoTeX can turn technical breadth into a narrower, monetizable wedge where device identity, verifiable compute, and live real-world data are indispensable rather than merely interesting. (github.com)