IoTeX (@iotex_io) header
IoTeX (@iotex_io) profile picture

The blockchain platform for Real-World AI.

U.S.A. 🇺🇸
Joined December 2017
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.
Days before the $ANT IPO, $GOOG just dropped a bomb. The bell hasn't even rung yet. And the throne already has a new name. Gemini 4 Neon. Live on QuickSilver Pro right now. Same key!
1
3
1
34
3,544
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
27
5
254
15,482
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 👇
37
8
1
499
33,909
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.
🔥 NEW: The XRP Ledger Foundation proposes quantum-resistant signing keys, with Ripple targeting a full transition by 2028.
34
9
1
209
9,641
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 👇
65
5
2
345
18,385
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
4
1
42
4,520
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.
Claude Fable 5.2 is live on QuickSilver Pro 🚀 We gave it a failing test suite in Claude Code. 10 seconds later: root cause found, bug fixed, all tests green. It even caught a docstring mismatch we didn't ask about. $2 / $10 per 1M tokens, 75% below Anthropic list.
3
10
2
55
4,971
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.
4
7
3
54
4,876
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
18
7
146
8,872
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
37
11
1
199
17,594
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! 🛡️
Alpine Linux OpenSSH security bug that's been there for 10 years. Apply the fixes if you haven't.
27
7
124
6,649
Rapid-MLX 1.0.2: video with synchronized sound, generated locally on a Mac. 🎬🔊 Plus the everyday wins: paste any Hugging Face link and know if it runs before you download, a 1.6 GB first run, and idle models that free your RAM while the local API stays online. We started with a simple bet: machines would get smart. Now every release makes the machine on your desk a stronger node in an open intelligence network. 🐆
🚀 Rapid-MLX 1.0.2 is live. Local AI on your Mac just took a massive leap forward. What’s new? 🎬 Local Video + Audio generation (Pika H3 Flex) 🛑 "Stop Generating" for video jobs 🔗 Paste Hugging Face links anywhere ⚡ 1.6GB hyper-fast first run 💤 Idle Unload (save RAM, keep API up) Upgrade: `rapid-mlx upgrade`, or download the new DMG: rapidmlx.com/download Notes: github.com/raullenchai/Rapid…
37
10
1
179
7,599
The engine improves the model. The model improves the engine. 🔁 Open-source RSI => an open intelligence network that is self-evolving!
🤖 New Rapid-MLX policy: AI-assisted PRs welcome. Our contributor base keeps growing, so let's make it official 👇 🧑‍💻 Human-written PR → welcome 🤖 AI-assisted PR → very welcome 🍎 Local AI-assisted PR (powered by Rapid-MLX) → instant legend status A local model improving its own inference engine 🔁 This is the most beautiful closed loop in open source!
2
12
1
47
4,036
Agents don't just need models. They need machines. 🖥️🤖 QuickSilver Machines: a cloud dev box with Claude Code, Codex, OpenCode and Hermes preinstalled. Open a tab, let your agent work. 20 machines in the open beta, first come first serve. ⚡
QuickSilver Machines is open: a dev box for your agents. A Linux desktop + terminal in your browser, with Claude Code, Codex, OpenCode and Hermes preinstalled. Open it and let your agent work. 🇺🇸 US exit IP 💸 $0.02/h, billed per minute, paused is free ⚡ 2 vCPU / 4 GB, bursts to 4 vCPU 20 machines in the open beta. First come, first served. Free trial, no card. quicksilverpro.io/machines
22
14
2
144
9,816
🚨 Security advisory for all IoTeX delegates and node operators. CVE-2026-98432 is a critical Linux kernel bug (CVSS 9.8) that can let an attacker get remote root over TCP. If you are running an IoTeX delegate on an affected Linux kernel, please patch today. 🧵 Why nodes are affected: Go 1.24+ turns on Multipath TCP (MPTCP) for listeners by default, so iotex-core's P2P port 4689 listens over MPTCP. That is exactly the path the demonstrated remote-root exploit uses. You don't need to have enabled anything yourself. Fix: upgrade the kernel, then reboot • Debian 12/13: apt update && apt install linux-image-amd64 → 6.1.190+ / 6.12.113+ • Ubuntu (all releases): no fixed kernel yet. Apply the mitigation below 👇 Mitigation (no reboot): Drop IPv4 packets that carry IP options, which the exploit needs: nft add table ip ipopt_guard nft add chain ip ipopt_guard pre '{ type filter hook prerouting priority -300; }' nft add rule ip ipopt_guard pre ip hdrlength gt 5 drop We've been working with delegates directly and many have already patched. If you run a node, please don't wait. 👀
🚨 Critical Linux kernel TCP flaw enables remote root code execution; CVE-2026-98432 A race condition in the Linux kernel’s IPv4 TCP implementation can trigger a use-after-free before application authentication, potentially allowing an unauthenticated remote attacker to leak kernel memory, corrupt memory or crash the system. Anthropic says Claude developed a working exploit that executed attacker-chosen commands as root against Linux servers with a Multipath TCP listener. The exploit took approximately 53 minutes to complete during testing and has not been publicly released. ⠀ • CVSS: 9.8 Critical, according to the Linux kernel CVE team • Affected: Linux kernels beginning with version 4.4 • Fixed: 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10 and 7.3 • Attack requirements: Network access, no credentials and no user interaction • Exploitation status: No known attacks in the wild ⠀ Ubuntu and Red Hat Enterprise Linux had not released corrected kernel packages as of October 29. Debian, Oracle Linux, Amazon Linux and SUSE have released fixes for at least some affected branches. Distribution severity ratings differ substantially. Red Hat rates the flaw 5.9 because it considers the race difficult to win and describes denial of service as the most likely practical impact.
59
13
3
235
18,219
Door #3 is getting busy. ⚡ 9B tokens served by QuickSilver since launch, with weekly volume more than tripling week over week. Connect intelligence, at scale!
~9B tokens served on QuickSilver Pro since launch in August. Growth is accelerating: weekly volume more than tripled week over week, with 2.2B tokens in just the past 8 days. Every frontier model, one OpenAI-compatible API, with the cost returned on every call.
25
13
1
148
11,738
Standing with @binance, @cz_binance and @heyibinance tonight. Attacks like this hurt everyone in crypto. Whoever did this: the whole industry is watching those addresses. Huge respect to @tether and @circle for freezing funds within minutes. This is what a resilient ecosystem looks like. 🤝 The IoTeX network is unaffected and operating normally.
User funds are safe! It does look like a hack on Binance. Appreciate the quick freeze from Tether (~$971m) and Circle (~$823m). I don't manage Binance (.com) anymore, but as a shareholder, I expect all user funds will be fully covered.
40
8
1
198
15,337
Machines that see and decide in real time. 👀⚡ Trio-Spark v1.4 from @machinefilab now reads photos, video frames and text through one API: spotting hazmat placards and inspecting truck equipment, zero-shot. This is how machines get smarter. One more door into the open intelligence network. 🗝️
Trio-Spark v1.4 is officially here. 🔥 We’ve unified text, images, and short video behind one powerful API. On 13 public benchmarks against top models like Jev 1.14 and Clef-Flash, Trio-Spark consistently ranks best or tied for best. Read the full breakdown: machinefi.com/blog/trio-spar…
31
7
1
136
8,160