IoTeX中文社区

IIP-59 is live, so we visualized it. Every dot in this video is a real staking reward payment on the IoTeX L1, replayed block by block from on-chain data. Nothing is simulated. Since the Zanzibar upgrade, the protocol has paid 432,542 IOTX to 13,846 voters across 46 delegates, in 34,485 payments. No claims. No manual payouts.

Critical PHP vulnerabilities (CVE-2026-109618 / 109619) are a reminder that infrastructure is only as strong as its weakest dependency. IoTeX L1, @iopaywallet, iotexscan.io, hub.iotex.io and our core products don't run on PHP and are not affected. We keep our stack minimal, audited, and monitored, because verifiable systems start with secure foundations. Builders: if you run PHP anywhere, patch now. 🔒

Security has been core to the IoTeX L1 since mainnet launched in 2019. Now we're bringing the security research community in. The IoTeX L1 now has a formal vulnerability disclosure policy: private reporting, clear scope, safe harbor, and public credit for researchers. Come break things (on devnet). 🛡️ github.com/iotexproject/iote…

⏰ 6 days to Zanzibar. The Zanzibar hard fork activates on IoTeX mainnet at block 53,533,081 (est. Oct 19, 02:00 UTC). Delegates & node operators: upgrade to iotex-core v2.5.1 now. → Just swap the image: iotex/iotex-core:v2.5.1 → No config changes. No resync. → Nodes still on v2.4.x will fall out of consensus at activation. Most of the network has already upgraded. Let's get to 100% before the fork. Release notes 👇 github.com/iotexproject/iote…

We showed our multimodal fast-decision model Trio-Spark random photos of US trucks and asked one question: "What is it hauling?" • Zero training. Zero examples. • 83% accuracy across 7 trailer types. • 100% hazmat placards caught. • Cost: Just $14 per MILLION photos. 🤯 Extracting equipment, hazmat, or load status on every highway frame used to be cost-prohibitive. Now, Spark delivers calibrated probabilities in a single pass, letting your pipeline automate the confident calls and only route edge cases to humans. Run a camera network? Send us 10k labeled images and we'll prove the accuracy and cost on your own data. Try it out: platform.machinefi.com/spark

The Zanzibar Hard Fork is getting full ecosystem backing. 🏗️ @binance has officially announced their support for the IoTeX network upgrade on Oct 19. A brief pause on $IOTX deposits/withdrawals will occur at 01:00 UTC for a safe and smooth upgrade. Details below: binance.com/en/support/annou…

IIP-64: how IoTeX stays secure as it decentralizes, in a post-quantum, post-AI world. This is an open proposal, not a done deal. It will go through public review, revisions, and a governance vote. We're sharing it early because this is not just an IoTeX problem. Every blockchain has to solve it. Today, nearly every chain signs with ECDSA. It can fall two ways: • Quantum: Shor's algorithm on a large enough quantum computer • AI-accelerated math: a classical breakthrough that shows up as a paper, with no hardware warning The second scenario is no longer far-fetched as AI may compress decades of math progress into a few years, and the structured math behind some "post-quantum" schemes could be the first to give. The design: two locks, not one • IIP-64 uses two NIST-standardized post-quantum signature families. Each is strong where the other is exposed: • Hash-based (SLH-DSA, FIPS 205 / XMSS): security rests only on hash functions. No algebraic structure, so there is very little for an AI-discovered shortcut to grab onto. Very conservative, but large (~16 KB per signature). • Lattice-based (ML-DSA, FIPS 204): compact and fast, the mainstream post-quantum standard. But it has algebraic structure, the kind of thing a mathematical breakthrough could weaken. Why this matters more as we decentralize More delegates means more signatures per block, and post-quantum signatures are 10–100x larger than ECDSA. So IIP-64 also specifies STARK-based signature aggregation, so the chain can grow its validator set without drowning in signature data. A different philosophy from Ethereum Ethereum's execution layer leans on account abstraction: every account can bring its own signature scheme. That's flexible, but it pushes a hard cryptographic choice onto every user and wallet. IIP-64 makes the choice at the protocol level: a small, vetted menu, with a hybrid required where the stakes are highest. Plus a defined crypto-agility process, so if cryptanalysis moves, the protocol can rotate parameters or entire families without another address migration. Also in the proposal • Phased migration: bind PQ keys → require both → retire legacy • Acceleration triggers for both quantum milestones and AI/classical breaks • Recovery staged before a break: prove ownership now, use it later We'd love cryptographers, researchers and other chains to review it, challenge it, and break it. Comments on the PR are open 👇 github.com/iotexproject/iips…

$IOTX is coming home. IOTX launched in 2018 as an ERC-20 on Ethereum. A year later IoTeX mainnet went live, and native IOTX took over the real work: paying for gas, securing the network through staking, and settling everything on IoTeX L1. But the 2018 contract never fully went away, leaving IOTX split across two forms. Today we start consolidating it. Introducing the IOTX Redemption Portal: → hub.iotex.io/redeem → Legacy ERC-20 IOTX in, native IOTX out → 1:1, zero fees → Connect, send, sign. Native IOTX lands at the same address. The world's biggest platforms are already there. @Revolut, Europe's largest fintech with 70M+ customers worldwide, now supports native IOTX. So does @BitkubOfficial, Thailand's largest licensed exchange. They join Binance, Upbit, Bithumb, Kraken, Crypto.com and more, which already support native IOTX. Why now? The internet connected computers. We're connecting intelligence: the models, Macs, machines and agents now running everywhere, on an open, verifiable network. IOTX is at the core of that network. And it starts with one clean supply.

We just ordered an M5 Ultra to make Rapid even faster, but we're looking at a 16-week wait. 😅 Does anyone in the community have one we could briefly access remotely for some experiments? DM us! 🙏

The IoTeX team is in San Francisco for #SFTechWeek 🌉 We're here to talk about one idea: intelligence is leaving the data center, and it needs an open, verifiable network to work together. If you're building with local AI, agents, inference or intelligent machines, let's meet. DMs open. 👇

IoTeX Network ♥️ SF

Any open model, from anywhere, running on your own Mac, plugged straight into your agents. Rapid-MLX 0.15.6: • Point it at any Hugging Face checkpoint and it serves it • One command to wire local models into Codex, Claude Code and more • Typed, on-device decisions (routing, triage, scoring) instead of generated chat This is what an open intelligence network looks like from the edge: anyone's model, on anyone's machine, working with anyone's agent. 👇

An early glimpse of something we've been working toward. Local AI on a Mac has always served one person, its owner. With Share Compute, @rapidmlx and @qspro_ai are testing whether that same Mac can serve real API traffic for others. First numbers look promising: a Mac mini (M4 Pro) runs Qwen3.8-27B at 40+ tokens/s, versus 50+ in the cloud. It's very early, just internal testing for now. But it points at the open, verifiable intelligence network we want to build: intelligence served from wherever it runs, by anyone who has something to bring. Got a Mac with 48GB+? DM @qspro_ai if you'd like to help test. 👇

Following our drone deployment, Trio-Spark v1.0 now generalizes to robotic manipulation. By continuously evaluating the physical state, the model executes a strict sequence of 8 manipulation skills to complete the task in 13.68 seconds with zero collision violations. Entirely token-free. One model inference per action boundary. Live API: platform.machinefi.com/spark Code & Demo: github.com/machinefi/trio-sp…

IoTeX v2.5.0 (Zanzibar Hardfork) is officially out! 🌐 MainNet activation: Block 53,533,081 (est. Oct 19, 02:00 UTC). This is a massive protocol upgrade that moves staking rewards fully on-chain, tightens EVM precision, and lays the security groundwork for our next phase of scalability. Here is how it impacts the network: 🗳️ 1. Fully Decentralized Staking Rewards (IIP-59) - The Tech: Voter rewards are now natively computed and distributed by the protocol itself at era boundaries (24 epochs). - The Impact: Zero reliance on off-chain services (like Hermes). Staking yields are now 100% trustless and automated. We’ve designed this for a seamless transition—most Hermes-vault delegates with complete reward portions will be migrated automatically at the fork block. ⚡️ 2. EVM Precision & Gas Savings - The Tech: Corrected GetCommittedState for absent prestates and fixed SELFDESTRUCT transfer-log amounts. - The Impact: Strict compliance with EIP-2200 dynamic gas rules. For developers and users, this prevents massive gas overcharging on certain in-place writes (saving 2,800 gas per hit). For indexers and wallets, token balance histories reconstructed from tx logs are now perfectly accurate. 🛡️ 3. Proactive Security (BLS PoP) - The Tech: BLS proof-of-possession is now enforced on candidate register/update operations. - The Impact: This completely closes the rogue-key forgery window today, safely paving the runway for IIP-52 signature aggregation (massive network scalability) tomorrow. (Note: Providing a BLS key is now optional until IIP-52 is live). 🖥️ 4. Zero-Friction Upgrades for Node Operators - The Tech: The hardfork heights and new contract addresses are baked directly into the binary. - The Impact: No genesis replacements. No config changes. Just a pure, clean binary roll. 👉 docker pull iotex/iotex-core:v2.5.0 and restart. Dive into the full technical details here: github.com/iotexproject/iote…

Activation of IoTeX (IOTX) Deposit and Withdrawal Systems on the IoTeX Network on 23/09/2026 from 05:00 PM (GMT+7) onwards . Referring to the token migration of IoTeX (IOTX) from the Ethereum network (ERC-20) to the IoTeX network, we are pleased to announce that the deposit and withdrawal of IOTX on the IoTeX network are activated according to the schedule below. . Schedule Issue: Activation of IOTX Deposit and Withdrawal on the IoTeX Network Date: 23 September 2026 Time: 05:00 PM (GMT+7) onwards . For more information, please click here: support.bitkub.com/en/soluti… . Remarks - Please use wallets that support the IOTX token on the IoTeX network only. - To prevent asset loss and for the continuity of transactions, please create a new IOTX wallet address on the IOTX deposit page after the IOTX deposit is activated on Bitkub Exchange, and use the new wallet address for your future IOTX deposits. Click here to learn how to create a new wallet address >support.bitkub.com/en/suppor… - If your IOTX transactions do not follow the service criteria, your digital assets may be lost or not appear in the destination wallet. In this case, you can contact our Customer Happiness for assistance with asset recovery. However, Bitkub Exchange does not guarantee that asset recovery will be achievable. - Digital assets involve risks; investors should study information carefully and make investments according to own risk profile. - Bitkub Exchange reserves the right in its sole discretion to amend or change these announcement details, and we will notify you further if there is any change. . Thank you for your continued support.

3 updates from our quicksilverpro.io team 👇 1/ Grok 4.7 is live @spacexai flagship model for coding & long-running agents: • 500K context, vision, tool calling & structured outputs • 20% cheaper than Grok 4.6 • Same key, same OpenAI-compatible endpoint 👉 quicksilverpro.io/models/gro… 2/ System One Jev is live jev-1.13 is on quicksilverpro.io. It returns decisions, not text. Send a state + up to 64 typed questions (choice, score, or probability) and get calibrated probabilities back from a single forward pass. 👉 quicksilverpro.io/models/gro… 📹 See demo here: teapaw.org/Raullen/status/2102096… 3/ Next: Verifiable Private Inference We’re prototyping confidential inference: • Hardware TEEs keep prompts & weights encrypted and invisible to host • Remote attestation lets you verify every session yourself • End-to-end encryption (ECDH + AES-256-GCM) means plaintext is decrypted only inside the enclave Private by construction, not by policy. 🛡️ Intelligence you can access anywhere. Verifiable end to end. That's the IoTeX stack. 🌐