Hello World! 🌎🤖 @iotex_dev is the official Twitter account for IoTeX developer tech updates. Follow us to stay up-to-date on the latest IoTeX code releases, DApps, tools, and all things tech! $IOTX

This is just a sneak peek of the infrastructure we're laying down. Big things are coming. Stay tuned. 👀 👇 Join the build quicksilverpro.io

@iotex_io v2.4.0 is shipping — our biggest mainnet upgrade of 2026. It's a mandatory hardfork activating at block 48,985,561 (≈ June 7, 2026 · 23:52 UTC). Two things we've been working toward all year: ⚡ Pectra EVM — IoTeX is now aligned with Ethereum's latest execution layer: · EIP-7702 — EOAs can act as smart accounts · EIP-2537 — native BLS12-381 (bridges, light clients, ZK) · EIP-2935 — historical block hashes from state · EIP-7623 — recalibrated calldata pricing 🛡️ Candidate Exit Queue — delegates can no longer unwind their self-stake instantly. Exits now go through a request → schedule → confirm flow, with admission rate-limited at the protocol level. A cleaner, more predictable lifecycle for our delegate set. What you need to do 👇 ▸ Delegates / Full Nodes / API Nodes — upgrade to v2.4.0 before block 48,985,561. Miss it = fork off mainnet. ▸ Wallets & dApps — check your gas estimator against the new EIP-7623 calldata floor, and add support for TxType 0x04 (SetCode) if you serialize raw transactions. ▸ Indexers / Explorers — new on-chain events from the exit queue and 7702 authorization tuples are ready to be indexed. Release notes: github.com/iotexproject/iote… Huge thanks to the core team, delegates, and every dev who helped pressure-test this release. Run a node. Build on it. See you on the other side of 48,985,561. LFG. 🟢

Major power-up for the IoTeX L1! ⚡️ The v2.4.0 upgrade landing June 7 introduces: 🔹 Native Account Abstraction (EIP-7702) 🔹 3-Stage Exit Queue for security 🔹 Better BLS key management for node ops By integrating EVM Pectra, we're bringing EIP-7702 to the ecosystem—meaning smoother onboarding and "smart" wallet features for every user. Build the future of Real-world AI on the most advanced stack. 🚀

1,000 GitHub stars in just 75 days! 🌟 Massive congrats to @Raullen and the IoTeX team for leading the charge in decentralized AI. 0.08s TTFT and 4.2x faster —Rapid-MLX is a foundational tool for the future of local compute and the fastest local AI engine for Apple Silicon. 🍎 Check and Star it on GitHub: github.com/raullenchai/Rapid…

COMMUNITY UPDATE: Bridge Compensation Claim is Now Live 📢 As promised, the IoTeX Foundation is providing 100% compensation for all assets affected during the Feb 21st bridge incident. The claim portal has been officially updated and is ready for the CLAIM. CLAIM STEPS: 1️⃣ Visit: iotube-claims.iotex.io 2️⃣ Check your claim status 3️⃣ Head to the Payout page to claim your assets Thank you for your patience and continued support as we ensure the security and transparency of our ecosystem. 🛡️

2026: The year AI gets "eyes and ears." 👁️👂 We're transitioning from simple motion alerts to Edge AI models that actually understand their environment. @iotex_io is providing the infrastructure to decentralize and secure this new nervous system of the physical world.

IIP-56 is live on IoTeX Hub and open for vote. 🗳️ Following the @iotube_org exploit on February 20th, we're moving decisively: full deprecation of CIOTX across Ethereum, Base, Solana, BSC, Polygon, and IoTeX with a clean, differentiated wind-down for each network. ✅Affected chains (ETH, Base, Solana): bridge permanently shut down, attacker-minted tokens disregarded, and a dedicated claims portal already live for legitimate holders to reclaim equivalent IOTX → iotube-claims.iotex.io ✅Unaffected chains (BSC, Polygon, IoTeX): bridges reopen after a full security review for self-serve migration back to IOTX. This is step one. IIP-57: Trustless Bridge: Replacing Keys with Proofs is already in the pipeline. We're not patching, we're rebuilding. Voting closes March 11th. Read the full proposal and cast your vote 👇 hub.iotex.io/governance/iip-…

🚨 IoTeX Core v2.3.0 Mainnet Release This release introduces a hardfork at block height 41,648,761 (ETA Nov 4, 2025 – 03:45 UTC) and includes two key protocol upgrades that strengthen reliability and prepare the network for future scalability. ✅ IIP-50 — Slashing for Underperforming Delegates: Establishes economic incentives to maintain high-performance infrastructure and ensures reliable consensus participation across all validators. ✅ BLS PublicKey Registration: Enables BLS key registration and updates in candidate transactions, paving the way for upcoming signature aggregation — a major step toward scalable finality. 🔐 This upgrade is mandatory for all delegates to remain in sync with the @iotex_io L1 blockchain. 👉 No changes required to config.yaml or genesis.yaml; simply restart your node with the new image. Full bootstrapping instructions can be found on the IoTeX Github at github.com/iotexproject/iote… 💥 This update marks a significant milestone for the IoTeX L1 — reinforcing performance, accountability, and readiness for large-scale DePIN and RWAI workloads. 📘 Full release notes: github.com/iotexproject/iote…

🚨 Update on @iotex_io Core v2.3 A minor bug was identified during the Testnet rollout and has now been fixed in v2.3.0-rc13. 🔧 Testnet hardfork details: Block height: 36,826,561 ETA: Oct 20, 2025 – 11:35 UTC ✅ All Testnet nodes should upgrade to v2.3.0-rc13 and update their genesis.yaml (linked in the release notes below 👇). With this patch in place, the Mainnet release schedule will be announced shortly, following the successful Testnet validation. 📘 Release notes: github.com/iotexproject/iote…

IoTeX Core v2.3 is live on Testnet ⚙️ @iotex_io continues evolving its L1 toward stronger decentralization, scalability and reliability! ✅IIP-50: This hardfork activates IIP-50 — a major step toward improving network reliability and delegate accountability by rewarding consistency and enforcing fairness. Delegates who fall below the 85% productivity threshold will see deductions from their self-stake. The goal: ensure every consensus participant operates high-performance infrastructure that supports the network’s growth, while protecting voters and maintaining stable rewards. ✅Also in this release BLS key registration for delegates — setting the foundation for upcoming IIP-52 signature aggregation. 🚨Mainnet activation expected in the next 1–2 weeks — delegates will receive ample notice ahead of the upgrade. Please note that this is a mandatory upgrade for all nodes to stay in sync. 📘 Full release notes: bit.ly/43eFT7x

🚨 IIP-52: BLS Signature Aggregation — Voting is Live ℹ️ Right now, every @iotex_io L1 block finalized by consensus carries a signature from each delegate: that’s ~2.3KB of extra data in every block. It's been working faultlessly until now, but it slows propagation and limits scalability. 💊 IIP-52 proposes a fix: aggregate all validator signatures into a single 96-byte BLS signature with a lightweight bitmap showing who signed. The result? ✅ Blocks shrink dramatically → faster propagation across the network ✅More room for transactions → better throughput ✅ Technical foundation to safely scale validators This change is already common in networks like @ethereum 2.0, and now it’s on the table for @iotex_io. 🔗 Review the details and cast your vote on the IoTeX Governance Hub: bit.ly/42fGdCE

At @iotex_io, protocol upgrades follow a clear, transparent path: Every change — from consensus rules to scalability features — goes through the IoTeX Improvement Proposal (IIP) process: ✅Drafted openly by devs & community ✅Reviewed in the Forum ✅Voted on-chain via the Governance Hub ✅Implemented into IoTeX L1 Recent IIPs covered slashing, stake-weighted consensus, BLS signature aggregation, and dynamic delegate scaling — upgrades that make the network more decentralized, reliable, and capable of supporting RWAI. 🔗 Learn how IIPs work & join the discussion: community.iotex.io/t/the-iip…

🚨 IIP-52: BLS Signature Aggregation is open for discussion in the @iotex_io community forum 🗳️ ℹ️ This proposal introduces BLS signature aggregation, compressing all delegate signatures for block finality into one single proof instead of storing them individually. Today, every delegate signs a block separately. With 24 delegates, that means 24 different signatures — adding ~2KB to each block and slowing down propagation. Why this matters: ✅Shrinks block footers from ~2KB → 96 bytes ✅Faster block propagation → quicker confirmations ✅More room for transactions → higher throughput ✅Scales smoothly as the number of delegates grows This is the same cryptographic upgrade used by Ethereum 2.0 and other top chains to improve efficiency and scalability. Join the discussion in the IoTeX community forum and help shape the future of IoTeX governance. 👇 🔗 bit.ly/3HVjrck

🚨 IIP-50 is now open for voting on the @iotex_io Hub! 🔹 This proposal introduces slashing for underperforming delegates, adding a real economic cost to missed blocks. 👉 It’s a big step toward fairness and stronger network reliability. Why it matters: ✅ Delegates under 85% productivity are penalized—losing self-stake, not just rewards. ✅ Penalties go back to the reward pool, not lost. ✅ Delegate replacement thresholds prevent unreliable nodes without being overly harsh. ✅Stronger incentives for top-performing nodes, and clear disincentives for poor reliability. Be part of shaping IoTeX’s governance—vote now! 🔗 hub.iotex.io/governance/iip-…

🚨 IIP-50 is open for discussion! The goal of this proposal is to strengthen @iotex_io consensus by holding validators accountable. The proposal introduces slashing for chronically underperforming delegates, protecting network reliability and rewarding those who keep IoTeX running at full speed. A stronger network means: ✅ Better uptime for dApps & users ✅ More fairness for stakers ✅ A healthier reward pool Your feedback will shape the final decision—join the conversation: 🔗 community.iotex.io/t/iip-50-…

The @Bino_AI swarm just got an update that our community will surely enjoy: Thanks to the new Discourse integration, Bino will be able to participate in our community discussions on @iotex_io IIPs, governance, and general community debates. Head over to community.iotex.io/ and join the convo! Your move, entropy! 😉