Security is a continuous effort on IoTeX.
iotex-core v2.5.2 is now running on a majority of mainnet delegates. A huge thank you to security researchers @0x15_eth and @only01Essential, and to GitHub contributors lhphong09t2, gudangkantong and cezo484, for their responsible disclosures that helped harden the network.
Remaining node operators, including API and fullnode operators: we strongly encourage you to upgrade to v2.5.2 as soon as you can.
IoTeX v2.5.2 is out 🛠️
Heads up for node operators: this is a recommended upgrade, not a mandatory one. There's no hardfork, so nodes on v2.5.0 or v2.5.1 keep working and stay in consensus. We still encourage everyone to upgrade, and the network is already moving: 13 of 36 delegates are on v2.5.2 within a day of release.
It's a maintenance release, and the kind of work that keeps a chain trustworthy: hardening and correctness fixes across consensus, p2p, block sync, the action pool, block production and the API.
What's new:
🔒 Safer consensus: delegates now enforce a round lock and keep a durable record of what they've signed, so a restart can't lead a node to sign twice at the same height
🌐 Tougher networking: per-peer limits and throttled block sync, and honest peers no longer get banned for a node's own local errors
⚙️ Steadier block production: one failing transaction is now left out of a block instead of dropping the whole draft
🧰 Tighter API: bounded tracing, websocket and request sizes, plus blockHash support in eth_getLogs
And it's an easy upgrade:
✅ No hardfork, no genesis change, no config change
✅ No resync or snapshot reload, just swap the image
✅ Verified by replaying mainnet history from block 28M to 54M, with every block's state matching
Recommended for every node type: delegates, fullnodes, API and archive nodes. Delegates, please upgrade one node at a time, and read the release note first 👇
Yesterday, @thinkymachines released Inkling 2 Mini as open weights.
Today, it's thinking, calling tools and answering on a Mac. No cloud, no API key, nothing leaving the laptop.
That's Rapid-MLX: a free, open-source engine that turns Apple Silicon into a local AI machine.
A 26B model at 43 tokens per second, in 23 GB of memory. And not on some maxed-out workstation: this is a MacBook with the base 36 GB of memory, the kind of laptop plenty of developers already carry.
This is what open intelligence looks like in practice. Open models from the frontier labs. Open engines to run them. And intelligence you can own and run yourself.
IoTeX: the open, verifiable intelligence network.
Inkling 2 Mini from @thinkymachines, a 26B model, thinking, calling a tool and answering on a Mac. 🧵
Measured on an M5 Max, 36 GB, 4-bit:
⚡ 43 tok/s single stream
🚀 80 tok/s total over 8 parallel requests
💾 23 GB peak memory
🎬 Real time, not sped up
This is Rapid-MLX 1.1.0: a free, open-source local AI engine and desktop app for Apple Silicon.
IoTeX v2.5.2 is out 🛠️
Heads up for node operators: this is a recommended upgrade, not a mandatory one. There's no hardfork, so nodes on v2.5.0 or v2.5.1 keep working and stay in consensus. We still encourage everyone to upgrade, and the network is already moving: 13 of 36 delegates are on v2.5.2 within a day of release.
It's a maintenance release, and the kind of work that keeps a chain trustworthy: hardening and correctness fixes across consensus, p2p, block sync, the action pool, block production and the API.
What's new:
🔒 Safer consensus: delegates now enforce a round lock and keep a durable record of what they've signed, so a restart can't lead a node to sign twice at the same height
🌐 Tougher networking: per-peer limits and throttled block sync, and honest peers no longer get banned for a node's own local errors
⚙️ Steadier block production: one failing transaction is now left out of a block instead of dropping the whole draft
🧰 Tighter API: bounded tracing, websocket and request sizes, plus blockHash support in eth_getLogs
And it's an easy upgrade:
✅ No hardfork, no genesis change, no config change
✅ No resync or snapshot reload, just swap the image
✅ Verified by replaying mainnet history from block 28M to 54M, with every block's state matching
Recommended for every node type: delegates, fullnodes, API and archive nodes. Delegates, please upgrade one node at a time, and read the release note first 👇
Voting on IIP-65: Bunker Mode 🛡️ opens today at 4pm PT (00:00 UTC, Nov 21).
Nobody knows when a quantum computer, or an AI-assisted math breakthrough, will break the ECDSA keys that protect crypto today. Upgrading every account to post-quantum needs exchanges, wallets and hardware vendors to move together. That will take years.
IIP-65 doesn't wait. It gives staked IOTX a shelter IoTeX can build on its own, now.
How it works:
1️⃣ Go in early. Lock your staking bucket with a second, hash-based key (SLH-DSA, NIST FIPS 205). You only need your current key to do this once.
2️⃣ Wait it out. Inside the bunker, your bucket keeps voting and earning rewards. But nothing can unstake, withdraw, transfer or re-vote it without the guard key. A stolen ECDSA key alone can't move it.
3️⃣ Come out later. When post-quantum accounts arrive (IIP-64), sign once with the guard key and move your IOTX out.
Why hash-based? It relies only on well-studied properties of hash functions, not elliptic curves or lattices, so it holds up even if either one breaks. The trade-off is a heavy door: a ~16 KB signature, signed offline. For a vault you open a few times a year, that's fine.
Two bonuses:
🗳️ Guarded votes can't be hijacked, which protects delegate elections, and with them consensus
🔑 Lose your everyday key? The guard key alone can still recover the bucket
It's fully opt-in. The reference implementation has already run every operation end to end on a test network.
IOTX stakers, the vote runs for one week, until Nov 28 at 00:00 UTC. Make your voice heard 👇
IoTeX: the open, verifiable intelligence network.
Read the full proposal and cast your vote here:
hub.iotex.io/governance/iip-…
The IoTeX docs have a new home, rebuilt from the ground up, around what we're building now.
🛡️ Post-quantum, front and center: IIP-64, IIP-65 "Bunker Mode" and a testnet post-quantum wallet, with specs you can test against
⚡ AI inference for agents: QuickSilver Pro gives you 90+ models and cloud dev boxes through one OpenAI-compatible API
👁️ Multimodal decisions: Trio-Spark reads text, images or video and picks the next action, with a probability for every choice. 100 free decisions to start
🤖 Agent-readable by default: every page has a Markdown version, plus llms.txt and llms-full.txt, so your AI can read the whole thing
🔗 Every old link still works
Building with AI, or pointing your agent at IoTeX? Start here 👇
The reviews are in, and Gemini 4 Neon is the real deal.
🏆 Parallel: the highest-performing model they've ever measured on web research, and up to 10x cheaper than the next best
📊 Artificial Analysis: level with Google's own flagship, Gemini 4 Carbon, at about half the cost per task
⚖️ Vals Index: #1, leading on legal research and tax agent tasks
📈 Plotly's data analytics benchmark: a perfect 43 out of 43
Frontier intelligence that's faster and cheaper at the same time. That's the curve every agent builder has been waiting for.
And it's already live on @qspro_ai. Already building on QuickSilver Pro? Same API, same key, change one line and you're on Neon.
When a better model ships, your agents shouldn't have to wait. That's the whole point of QuickSilver.
IoTeX: the open, verifiable intelligence network.
A blockchain shouldn't need a data center to stay secure.
Release after release, we've been tuning IoTeX L1 to do more with less: leaner state storage, smarter caching, faster consensus. The goal is simple. Every CPU cycle, every GB of memory a delegate pays for should go into securing the network, not into waste.
Here's where that lands today. A mainnet delegate node needs:
✅ Minimum: 4 CPU cores, 8 GB RAM, 500 GB SSD
🚀 Recommended: 8 CPU cores, 16 GB RAM, 512 GB NVMe
Our old recommended spec called for 64 GB of RAM.
This isn't a lab number. IoTeX runs mainnet delegates on both setups right now. Each node uses about 1.7 GB of memory and under 5% CPU.
And the chain itself got faster at the same time: a new block every 2.5 seconds, final the moment it's produced, with delegates staking real value behind every block.
Lighter nodes mean more people can afford to run one, in good markets and hard ones. That's how a network stays decentralized and secure for the long run.
Updated hardware guide for delegates and anyone thinking about becoming one 👇
The bell hasn't even rung on Anthropic's IPO, and the crown has already moved.
Gemini 4 Neon just took #1 on the AA Index: 61, ahead of Claude Opus 5.5 at 59 and GPT-6.2 Sol at 57.
Tomorrow, someone else will take it back. The throne of AI changes hands every few weeks now.
That's exactly why IoTeX exists.
In the age of AI, the machines and agents we're building shouldn't be loyal to any one king: not one model, not one lab, not one company. They need a foundation that doesn't move when the throne does.
So we built QuickSilver Pro to bow to no one. 101 models, one key. Gemini 4 Neon was live on day one, and switching to it takes a single line of code.
Builders have noticed: QuickSilver usage is growing about 20% month over month, no matter who sits on the throne.
Kings rise and fall. The infrastructure stays.
IoTeX: the open, verifiable intelligence network.
We stand with @JensenHuang — a once-in-a-generation visionary, a champion of open innovation, a strong advocate for open-source AI, and a leader who believes AI should empower everyone and create a future where we all thrive together.
Someone who truly loves humanity.
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me.
I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA.
I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation.
Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO.
Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours.
Jensen
Post-quantum on IoTeX isn't a slide anymore. It's something you can run.
We just opened a Post-quantum section on our developer portal, with everything builders need to get ready for Q-day:
🔒 IIP-65 "Bunker Mode": lock a staking bucket with a second, hash-based key (SLH-DSA, NIST FIPS 205). A broken ECDSA key can't move your principal or your votes.
🧪 Match the reference byte for byte: test vectors for every operation, and an implementation that passes NIST's ACVP vectors.
💻 Run it locally: bind a guard key with ioctl, watch a plain unstake get refused, then unstake with the guard signature, even signed offline.
👛 A post-quantum wallet prototype, live on testnet, already sending IOTX and ERC-20 transfers with one-time hash-based keys.
🗺️ IIP-64: the plan for the rest of the chain, in five phases through 2033.
Plus an honest status bar: spec done, implementation in review, then forum review, vote, testnet, audit, mainnet. No dates set.
Wallets, exchanges, indexers, node operators: there's a section for you. Link below 👇
Another major chain is getting ready for Q-day.
The XRP Ledger's 2027 roadmap proposes ML-DSA-44, NIST's post-quantum signature standard, for accounts and validators, so holders can add a quantum-safe key and keep their address.
A report last week estimated 7.1M BTC, about 35% of supply, sits in addresses a large enough quantum computer could steal from. Every year the estimated cost of breaking today's keys keeps falling.
IoTeX made the same call, with one difference: we don't want to bet on a single kind of math.
🛡️ IIP-64 moves IoTeX signatures to ML-DSA, paired with a second, independent scheme. Breaking one isn't enough.
🔒 IIP-65 "Bunker Mode" adds a hash-based second lock to staked IOTX, with a reference implementation already in iotex-core.
Both are open proposals headed for a governance vote. Cryptographers welcome.
Post-quantum, post-AI, and a lot more: six months of IoTeX, in one read.
Five doors, one stack for machines:
🛡️ IoTeX L1: getting ready for Q-day with IIP-64 and IIP-65 "Bunker Mode", voter rewards moved fully onchain with the Zanzibar hard fork, and $IOTX coming home: redeem legacy ERC-20 1:1, no fees, same address
🧠 Rapid-MLX: 4,100+ GitHub stars, 400K+ Hugging Face downloads, and 1.0 decoding 82.9 tok/s on a Mac vs 48.8 for llama.cpp and 27.2 for Ollama
⚡ QuickSilver: 90+ models, 9.3B tokens served, 1,000+ users, and agents that pay for themselves in USDC over x402
👁️ Trio: Trio-Spark DI is top 10 on the Decision Index among models ≤9B, and routed 1,000 support tickets for half a cent
👛 ioPay: Robinhood Chain, Arc, prediction markets, and ioPay 6.0
The full newsletter, with videos, in 7 languages 👇
SGLang is one of the open-source engines behind frontier AI inference. This week its summit brings Google, NVIDIA, Meta, AMD, Intel and the teams who serve AI at scale to San Francisco.
Rapid-MLX is a sponsor: the open-source engine for running models locally on Apple Silicon. It started this spring. Today it has 4,100+ GitHub stars, 48 contributors and 400K+ downloads on Hugging Face.
Inference is growing in two directions at once: bigger clusters in the cloud, and capable models on the machines in front of us. An open intelligence network needs both, and the open-source teams building each.
Fort Mason, Nov 12–13. Come find the team for a live demo.
The Rapid-MLX team will be at @sgl_project Summit in SF tomorrow & Thursday (Fort Mason) 🚀
Proud to be a community sponsor. If you're curious how fast open models can run locally on a Mac, come find us — happy to demo and talk shop.
sglang.io/summit
This week, Claude Fable 5.2 coordinated 1,000+ AI agents to build a working operating system in eight days.
Now it's live on QuickSilver: one API for 90+ frontier and open models, running in Claude Code on your own cloud dev box.
When AI writes this much code this fast, the hard question is no longer "can it build?" It's "can you verify what it built?"
That's the layer IoTeX is building: open, verifiable infrastructure, so machine-made work can be checked, not just trusted.
Vitalik made an important point this weekend: ETH's value doesn't come from the fee burn. It comes from stability, which comes from decentralization, censorship resistance and security. And "in the era of AI disruption, stability will be highly valued."
We agree, and it applies to every L1.
Stability isn't a slogan. It's earned block by block. IoTeX L1 has been live since April 2019 and has produced more than 54 million blocks since, through every cycle: bull markets, bear markets, exchange collapses. Today it still finalizes a block every 2.5 seconds, instantly.
But stable doesn't mean frozen. The threats ahead are new: AI that finds exploits faster than any human auditor, and quantum computers that will eventually break today's signatures. A chain that wants to stay stable for the next decade has to keep evolving, in the open, before those threats arrive. That's what we're doing.
In that sense, IOTX is a store of value too: its value rests on the stability of the chain underneath it.
Expanding on why I believe "ETH as store of value (SoV)" makes much more sense to focus on than "ETH as fee-burning token".
Three primary reasons:
1. ETH as fee-burning token never was as strong as it seemed
2. Optimizing for ETH as fee-burning token would demand Ethereum and ETH function in ways that are very hard to make compatible with decentralization and capture resistance.
3. Meanwhile, optimizing for ETH as SoV is aligned with Ethereum focusing on its unique strengths (decentralization and CROPS)
EIP-1559 (including its burn) is fine and good, we should keep them. But we should not feel sad if fee burn is < 10% of breakeven indefinitely; the value of ETH comes from elsewhere.
The core idea: the big thing that people appreciate about Ethereum is decentralization and CROPS. The main pragmatic benefit that these things translate into is stability. SoV is the category where that is not an unneeded extra we merely put effort into for ideological reasons, but rather a pragmatic strength from the perspective of people putting in their assets. And in the era of AI disruption, stability will be highly valued.
2028 for a post-quantum, post-AI Ethereum. 🛡️
At Devcon, @drakefjustin pulled Ethereum's target a full year forward: three forks in 24 months. The message is clear: don't wait for Q-day, and don't wait for AI to crack the math.
IoTeX is moving in parallel, in two steps.
1️⃣ IIP-65: Bunker Mode comes first
Your stake shouldn't have to wait for the whole ecosystem. Bind a hash-based SLH-DSA key (NIST FIPS 205) to your staking bucket, and unstaking, withdrawing, or transferring will then require it. Even if your ECDSA key is broken someday, the attacker hits a wall.
The working PoC is solid: 0.23 ms to verify, a 48-byte key per bucket, fully opt-in, and zero EVM changes.
2️⃣ IIP-64: The full-chain migration
A hybrid of lattice (ML-DSA) + hash-based signatures for consensus, bridges, and admin keys—ensuring a single broken assumption is never enough. User accounts will follow.
Bunker first. Then the whole house. 🏠 Both are open drafts. Cryptographers, come break them:
github.com/iotexproject/iips…
github.com/iotexproject/iips…
JUST IN: CRYPTO RESEARCHER JUSTIN DRAKE JUST WARNED A MAJOR QUANTUM BREAKTHROUGH COULD BE REVEALED WITHIN WEEKS
KEY QUANTUM ADVANCES ARE "BEING CENSORED"
"THERE IS NO DISCUSSION OF Q-DAY TIMELINES –– EVEN WHEN THAT IS THE POINT OF THE PAPERS"
QUANTUM RESEARCHERS ARE "OPERATING IN STEALTH" AND WORKING DIRECTLY WITH THE AMERICAN AND CHINESE GOVERNMENTS
"WHEN YOU TALK TO THESE COMPANIES IT IS ALL HUSH HUSH"
"THIS IS A MATTER OF NATIONAL SECURITY"
HE IS RECOMMENDING ALL #BITCOIN AND CRYPTO HOLDERS ENTER "BUNKER MODE" QUICKLY ‼️
Source: @CryptoTimes_io
Quantum Bucket update: IIP-65 "Bunker Mode" is now Draft 4, featuring a full reference implementation in iotex-core. 🛡️
A few weeks ago, we proposed a doomsday bunker for staked $IOTX: locking buckets with a second, hash-based key. After an independent cryptographic review, we rebuilt the authorization layer to make it bulletproof. Here is what's new:
🔒 Hardened Cryptography: The core choice of SLH-DSA (FIPS 205) remains rock-solid. We upgraded the envelope with chain-instance domains (preventing cross-network replays), recent-block anchors (capping signature life at ~7 days), and exact consent bindings via SHA-512.
🧱 Verify-First Architecture: Every guarded operation verifies all signatures before touching the staking state. No speculative writes, no rollback games.
🔑 Simple Recovery: Guard keys come from a dedicated vault seed. If your everyday ECDSA wallet is compromised, your vault mnemonic alone can rescue your buckets.
⚡ Lightning Fast: Verification takes just ~0.23 ms on an Apple M3 Pro—four orders of magnitude faster than our 2.5s block time.
Where it stands: The code (~13k lines) is running on nightly behind a feature gate. Next up: full-handler benchmarks, an external audit, and a governance vote. Nothing changes on mainnet until then.
Quantum computers or an AI-assisted math breakthrough might take years. Bunkers must be built before the storm. We're building ours now. ⛈️
📄 IIP-65 Spec: github.com/iotexproject/iips…
💻 Implementation: github.com/iotexproject/iote…
What if your $IOTX had a doomsday bunker? 🛡️
We're introducing IIP-65: Bunker Mode—a draft proposal and working proof-of-concept for AI-safe, quantum-safe staking, inspired by @drakefjustin 's call for crypto to plan a "bunker mode."
The Problem
Today, a single ECDSA key controls your onchain asset. If a large enough quantum computer or AI-accelerated breakthrough cracks the math, an attacker could derive your private key from your public key and withdraw everything. Making the entire ecosystem AI & quantum-safe will take years and depends on many partners.
But a bunker doesn't have to wait.
The Solution: A Second Lock
1️⃣ Go in now: Bind a post-AI/quantum key to your bucket once, while your current key is still safe.
2️⃣ Wait it out: Your bucket keeps voting and earning rewards. But any critical action (unstaking, withdrawing, transferring) now requires the new key.
3️⃣ Come out later: Once post-quantum accounts exist, sign once with the new key and safely migrate your IOTX. If Q-day or an AI breakthrough comes while you're inside, the attacker hits a wall.
Why hash-based?
The new lock uses SLH-DSA (NIST FIPS 205). While lattice-based schemes rely on algebraic structures that future math might crack per @VitalikButerin, SLH-DSA rests purely on hash functions. It has no structure to break, making it the most conservative choice.
The trade-off is a "heavy door" (~16 KB signatures, signed offline)—perfectly fine for a vault you only open a few times a year.
Proof-of-Concept Highlights
⚡️ Fast: 0.23 ms to verify a signature on-chain.
🪶 Lightweight: 48-byte public key per bucket.
🔌 Frictionless: Fully opt-in & per-bucket. No EVM changes, no new address formats, no waiting on anyone else.
It's still a draft, and we want your feedback (and vote later) to make it real and bulletproof.
🎥 Explainer below
If your node infrastructure runs on Alpine Linux, please update OpenSSH immediately. A critical vulnerability was just disclosed that allows attackers to bypass key-only authentication.
Please patch your servers to keep your nodes and the IoTeX network secure! 🛡️
















