News
Follow what has changed.
Reviewed news adds a checked explanation of a development and the stage the evidence supports. Automatic headlines are for discovery and are labelled as not yet reviewed. Publication dates and review dates are shown separately, and older items stay as history.
Reviewed news
707 reviewed developments across 151 chains. Each chain's developments were reviewed on the date shown with it; after 10 days its label reads Review overdue until the next review.
A weekly reviewed news run is planned and not yet running, so many chains will show Review overdue until it starts. The items stay available as history.
Sorted by publication date · newest first; equal dates follow the alphabetical chain order. Page 11 of 14.
One chain's developments, A to Z
-
Manta retires its Polkadot chain and consolidates MANTA on Manta Pacific
Manta announced that it would not renew Manta Atlantic's Polkadot slot, which was due to expire around 1 August 2026, and would focus all development on Manta Pacific. The FAQ scheduled the end of Atlantic staking and the closing of inbound transfers for March 2026 and offered a migration app to move MANTA and other assets out; MANTA left on Atlantic is to be credited one-to-one to Manta Pacific addresses from a chain snapshot. In September 2026 Manta's site says Atlantic has sunset and sets 16 November 2026 as the deadline to migrate remaining MANTA. The FAQ says Manta Pacific itself is unaffected.
- Proposal:announced on 11 March 2026
- Implementation:migration app linked from Manta's site; the FAQ scheduled Atlantic staking and inbound transfers to close in March 2026
- Release:not a Manta Pacific software release
- Activation:site banner says Atlantic has sunset; final MANTA migration deadline 16 November 2026
Sources: Manta Network — Manta Atlantic Migration FAQ (external site) · Manta Network — Manta Network home page (external site) · Manta Network (GitHub, Manta-Network/docs) — Remove atlantic docs (#346) (external site) · Manta Network Documentation — Your Guide to MANTA: Understanding the Token and its Value (external site)
-
Ethereum to Rootstock Token Bridge sunset announced
Rootstock announced that the Token Bridge between Ethereum and Rootstock would stop supporting bridging after the end of March 2026, with shutdown expected by the end of April, and pointed users to Stargate and to current tokens such as USDT0 in place of legacy bridged dollars like rUSDT.
- Implementation:sunset announced
- Release:bridging support ending after March 2026
- Activation:shutdown expected mid to late April 2026; completion not verified
Sources: Rootstock — Token Bridge Sunset: How to Move Your Assets and Bridge to Rootstock via Stargate (external site) · Rootstock Developers Portal — Cross-chain bridges (external site)
-
Babylon announced Ledger clear signing for Bitcoin vaults, with BABY support to follow
Babylon Labs announced a Ledger integration centred on clear signing for Trustless Bitcoin Vault transactions, so users can read what they approve on the device. The post says BABY will be supported as part of the broader integration and that support for Babylon bitcoin staking is planned.
- Implementation:vault clear signing announced; BABY and BTC staking support planned
- Release:not confirmed from a Ledger product page
- Activation:Unverified
Sources: Babylon Labs — Babylon and Ledger Integration Expands Access to Trustless Bitcoin Vaults (external site) · Ledger (LedgerHQ/ledger-live) — Ledger Live Cosmos coin module: Babylon chain definition (source code) (external site)
-
Osaka hard fork scheduled for mainnet block 213,333,000, adding blob transactions
Kaia v2.2.2 set the mainnet Osaka hard fork for block 213,333,000, estimated for 7 April 2026. The fork adds blob transactions (KIP-279), which carry data that nodes are expected to keep for 21 days against commitments recorded in blocks, a secp256r1 signature precompile for the signatures passkeys use, the eth_config method and other execution changes, and it turns address(0) into an ordinary account without code. It followed v2.2.0 (28 January 2026), which scheduled the Kairos testnet fork.
- Proposal:specified in KIP-279 and KIP-276, among others
- Implementation:shipped in Kaia v2.2.0 and v2.2.2
- Release:mandatory mainnet upgrade in v2.2.2
- Activation:active on mainnet by 2026-09-29: the public endpoint's configuration listed the blob schedule and the secp256r1 verification precompile that the fork adds; the exact activation time was not checked
Sources: Kaia (GitHub) — Kaia v2.2.2 Release Notice (external site) · Kaia (GitHub) — Kaia v2.2.0 Release Notice (external site) · Kaia Blog — Kaia v2.2 Overview (external site) · Kaia Blog — [Breaking Change] v2.2.2 Hardfork Upgrade: Removal of Bytecode at address(0) (external site) · Kaia Improvement Proposals — KIP-279: BlobTx for Kaia (external site) · Kaia Docs and Kaia Foundation endpoint — eth_config method; read of the Kaia Foundation public endpoint on 2026-09-29 (external site)
-
Grin node 5.4.0 released, the first node release since 2024
Grin v5.4.0 was the first new reference-node version since v5.3.3 in September 2024 (a rebuild of 5.3.3 followed in November 2024). Its commits make long-overdue upgrades to the networking libraries (Tokio 1.x and Hyper 0.14), fix a case where fast state sync could stall, add a chain-type field to node status, allow running without the terminal interface, and publish Docker images for x86 and ARM.
- Implementation:shipped in v5.4.0
- Release:stable release published 2026-03-09
- Activation:no consensus change; takes effect as nodes upgrade
Sources: Grin developers (mimblewimble/grin) — Grin v5.4.0 (external site) · GitHub API (mimblewimble/grin) — Grin commits between v5.3.3 and v5.4.0 (external site)
-
Sonic Labs launched USSD, a dollar stablecoin built on Frax's frxUSD
Sonic Labs announced USSD (US Sonic Dollar) as the network's own dollar stablecoin, built on Frax's frxUSD infrastructure. Sonic says it is backed one for one by short-dated US dollar assets including tokenized Treasury funds, can be minted without fees against assets such as USDC, USDT and PYUSD, and can be redeemed one for one on a chosen chain. Yield from the backing assets is meant to fund buybacks and ecosystem incentives.
- Implementation:contracts deployed; Sonic docs list the USSD contract address
- Release:Launched
- Activation:live per Sonic docs on 27 September 2026
Sources: Sonic Labs blog — USSD: Sonic's Native, Permissionless USD Stablecoin Built With Frax (external site) · Sonic Labs docs — USSD (external site) · Sonic Labs blog — Day 100 - Where We Are, And Where We're Headed. (external site)
-
Evmos approves v20.2.0 so governance can force IBC withdrawals
Proposal 326 approved the Evmos Mainnet v20.2.0 software upgrade, which lets only the governance module force IBC transfers that withdraw tokens from remote chains. Proposal 327 then tested the path with a 0.1 USDC transfer to Axelar. This followed February proposals restoring expired IBC light clients.
- Proposal:Passed
- Implementation:upgrade approved; code location not verified
- Release:not listed among evmos/evmos releases
- Activation:upgrade height not verified; the governance transfer in proposal 327 passed by 11 March 2026
Sources: Stakeflow — Evmos Proposal #326: Evmos Mainnet v20.2.0 (external site) · Stakeflow — Evmos Proposal #327: Gov IBC Transfer (evmos->axelar) (external site) · Stakeflow — Evmos Proposal #325: Update IBC light client for Cosmos, Axelar and Gravity (external site) · Evmos core maintainers — evmos/evmos releases (external site)
-
Orca disabled trading on Eclipse and moved to withdrawals only
Orca wound down its services on Eclipse: trading and adding liquidity were disabled, its main Eclipse interface shut down, and a permanent withdrawal-only tool was made available for closing positions. Orca says assets remain on-chain and there is no withdrawal deadline.
- Implementation:trading and new liquidity disabled
- Release:withdrawal-only tool published
- Activation:in effect on review day
Sources: Orca — Eclipse Sunset (external site) · Orca — Whirlpool Position Closer (external site)
-
Report on the 23 February 2026 emergency prover upgrade
A bug bounty report found that Scroll's zkVM prover skipped a subgroup check on one kind of curve point in the ecPairing precompile, so some inputs gave different results in the sequencer and the prover and could have stopped batches from finalizing. The Security Council deployed a patched prover as an emergency upgrade on 23 February 2026 and published the fix and this report afterward.
- Implementation:patched prover release v0.7.2
- Release:patch published in the public repository after deployment
- Activation:deployed on mainnet 2026-02-23
Source: Scroll Governance Forum — Report: Scroll Mainnet Emergency Upgrade on 2026-02-23 (external site)
-
ar.io handed operation of the arweave.net gateway back to Forward Research
ar.io wrote that on 1 March 2026 it transitioned operation of the arweave.net gateway, the default access point many apps hardcode, back to the Forward Research team. It said the handover brought temporary instability, with slower loads and occasional timeouts, while the underlying Arweave data was unaffected, and it urged apps to route requests across several gateways with its Wayfinder protocol.
- Implementation:operator change completed on 1 March 2026 according to ar.io
- Release:not a software release
- Activation:in effect from 1 March 2026; no statement from Forward Research itself was found
Sources: ar.io — The Dock Isn't the Lake (external site) · Arweave Docs — HTTP API (external site)
-
Besu removes Ethereum Classic support in version 26.2.0
The Besu client, which the community timeline records as supporting Ethereum Classic since 2019, marked Ethereum Classic and Mordor support as deprecated in versions 25.12.0 and 26.1.0 and removed it, including all Ethereum Classic hard-fork settings, in version 26.2.0.
- Implementation:support removed in Besu 26.2.0
- Release:Released
- Activation:applies to anyone who upgrades Besu to 26.2.0 or later
Sources: Besu maintainers (GitHub) — Besu 26.2.0 release notes (external site) · Besu maintainers (GitHub) — Besu CHANGELOG (main branch) (external site) · ethereumclassic.org (community site) — Classic History (roadmap timeline) (external site)
-
Legacy Fantom Opera node client v1.2.1-j released as an optional peer-connection fix
Version 1.2.1-j of the legacy Fantom Opera node client was published in the Fantom-foundation/Sonic repository. The notes list two fixes: a check for a no-archive error when a node sends new-block notifications, and explicit name lookup for bootstrap nodes. They say operators need it only if their node cannot find a peer to connect to. The repository states this client runs Fantom Opera only and will not work with the Sonic network, whose client lives in the 0xsoniclabs/sonic repository.
- Implementation:two fixes merged: no-archive error check for block notifications and bootstrap-node name lookup
- Release:released 2026-03-05 as GitHub release v1.2.1-j
- Activation:no network upgrade or activation; optional install for Opera node operators, per the release notes
Sources: Fantom-foundation (GitHub) — v1.2.1-j (external site) · Fantom-foundation (GitHub) — Release notes from Sonic (Fantom-foundation/Sonic) (external site) · Sonic Labs blog — Sonic's Successful Network Migration: What This Means for Fantom Opera (external site)
-
zUSDC via XBridge introduced; deBridge support on Zilliqa set to end 31 March 2026
Zilliqa introduced zUSDC, a USDC representation minted by its own XBridge, after unwinding bridged USDC through Ethereum and re-bridging the liquidity. It asked holders of the older bridged USDC to bridge out through deBridge before 31 March 2026, the date it set for deBridge support on Zilliqa to end.
- Implementation:zUSDC deployed and trading pair launched
- Release:announced as completed phases 1 to 3
- Activation:deBridge sunset set for 2026-03-31; not independently checked
Sources: Zilliqa blog — Strengthening Stablecoin Infrastructure on Zilliqa: Introducing zUSDC via XBridge (external site) · Zilliqa — Zilliqa Bridge (XBridge) (external site) · Circle — USDC contract addresses (external site)
-
Harmony v2026.0.0 adds Stream Sync and sets shard constants to two
Harmony published node release v2026.0.0, a mandatory upgrade without a hard fork. It added Stream Sync, a peer-to-peer way to sync that removes reliance on DNS-based syncing but stayed optional, and changed configuration and consensus constants from four shards to two to match the network running since November 2023.
- Implementation:Released
- Release:v2026.0.0 published 2026-03-04
- Activation:no hard fork; took effect as nodes upgraded
Sources: Harmony (GitHub) — Mainnet Release 2026.0.0 (external site) · Harmony (GitHub) — Harmony releases (external site)
-
Monero v0.18.4.6 released
The reference-client bugfix release fixed daemon peer-list filtering, P2P connection issues and a trusted-multisig key-exchange failure. It is software-release evidence and does not establish a new consensus-rule activation.
- Stage:Stable release
- Activation:Not claimed
Sources: Monero community — Monero 0.18.4.6 'Fluorine Fermi' released (external site) · The Monero Project contributors — Monero v0.18.4.6 release (external site)
-
CIP-0105 ties Super Validator reward weight to locked Canton Coin
CIP-0105, approved on 2 March 2026, says a Super Validator earns its full reward weight only while it keeps a set share of its lifetime Super Validator rewards locked, starting at 70% and stepping down over the following years; lower tiers earn part of the weight, and unlocking vests over a year. The Foundation's MainNet configuration shows weight adjustments made under it, the latest on 28 September 2026.
- Proposal:CIP-0105 approved on 2026-03-02
- Implementation:enforced through reward-weight entries in the Foundation's MainNet configuration
- Release:policy applied by configuration; no software release identified
- Activation:active; the MainNet configuration records enforcement and reversals, the latest on 2026-09-28
Sources: Canton Foundation (CIPs repository) — CIP-0105: Super Validator (SV) Locking & Long-Term Commitment Framework (external site) · Canton Foundation (configs repository) — MainNet approved-sv-id-values.yaml (external site) · Canton Foundation (configs repository) — Commit history of the MainNet approved-sv-id-values.yaml file (external site)
-
OM became MANTRA in a 1:4 redenomination at block 13,000,000
The v7.0.0 upgrade carried out the governance-approved change of the native coin from OM to MANTRA. Balances and staking positions were multiplied by four, the base unit moved from uom (6 decimals) to amantra (18 decimals), and the supply cap became 10 billion MANTRA.
- Proposal:approved as proposals 26 and 29
- Implementation:shipped in mantrachain v7.0.0
- Release:Released
- Activation:active since block 13,000,000 on 2 March 2026
Sources: MANTRA Chain Docs — MANTRA Token Background (external site) · MANTRA (on-chain governance record) — Governance proposal 29: v7.0.0 upgrade (OM to MANTRA redenomination) (external site) · Polkachu (governance proposal mirror) — Mantra proposal 29: v7.0.0 mainnet upgrade (external site) · MANTRA (on-chain governance record) — Governance proposal 26: Redenominating OM to MANTRA (external site) · MANTRA — MANTRA Chain Coin Upgrade: Timeline and Key Details (external site)
-
hostd v2.7.0 added optional consensus pruning
hostd v2.7.0 added an experimental, off-by-default option that limits how many blocks a host stores, since the v2 state design no longer needs every past block to validate new ones. The release advises keeping at least one day of blocks (144 on mainnet) for protection against deep reorganizations. It also fixed contracts wrongly shown as active when a revision and resolution landed in the same block.
- Implementation:shipped in hostd v2.7.0
- Release:released as an experimental option, off by default
- Activation:opt-in per host
Sources: Sia Foundation (GitHub) — hostd v2.7.0 release notes (external site) · Sia Foundation blog — The State of Sia, February 2026 (external site)
-
Juno cuts its active validator set to 25
Governance proposal 372 passed and set the maximum number of active validators to 25, down from the 80 set in April 2025. The proposal said falling network activity and fee income left rewards spread too thinly, and that operators were already leaving. Validators outside the top 25 became inactive, and their delegators had to redelegate to keep earning rewards.
- Proposal:proposal 372 passed
- Implementation:parameter change executed by the proposal
- Release:no software release needed
- Activation:active: staking parameters showed a cap of 25 and 25 bonded validators on 2026-09-27
Sources: Juno on-chain state via PublicNode REST endpoint — Juno proposal 372: Reduce Maximum Validator Set to 25 (external site) · Juno on-chain state via Polkachu REST endpoint — Juno proposal 362: Reduction of the Validator Set (external site) · Juno on-chain state via PublicNode REST endpoint — Juno staking parameters (external site) · Juno on-chain state via PublicNode REST endpoint — Juno bonded validators (external site) · Juno on-chain state via Polkachu REST endpoint — Juno latest validator set (external site)
-
SKALE Labs' chief executive proposed shrinking the Ethereum deployment and focusing on SKALE on Base
In a forum post, SKALE Labs' chief executive described SKALE on Base, the first SKALE Expand deployment, as moving beyond a trial, said SKL could now move between Ethereum, Base and SKALE on Base, and put the SKALE on Ethereum network at about 800 nodes and 16 chains. He proposed contracting that network: a rising minimum stake per extra supernode and consolidating apps onto about five main chains while retiring underused ones.
- Proposal:strategy post; the minimum-stake part was proposed separately as SIP-5
- Implementation:not verified
- Release:no software release involved
- Activation:not verified; which chains were retired was not checked
Sources: SKALE Network Forum — Expand. Contract. Grow: The Next Evolution of the SKALE Network (external site) · SKALE Network Forum — SIP-5: Progressive MSR for Network Efficiency (external site)
-
Batch amendment signature flaw disclosed before activation
A disclosure report described a loop error in the proposed Batch amendment's signature checks that would have let an attacker run inner transactions from other accounts without their keys. The amendment was still in voting and had not activated, so no funds were at risk. Server version 3.1.1 marked Batch as unsupported, and a corrected replacement amendment was prepared.
- Proposal:Batch amendment withdrawn; replacement BatchV1_1 in voting
- Implementation:fix and replacement implemented in later server releases
- Release:3.1.1 released 2026-02-23 marking Batch unsupported
- Activation:original Batch never activated; replacement not active as of this review
Sources: XRP Ledger blog (xrpl.org) — Vulnerability Disclosure Report: XRPL Batch Amendment - Unauthorized Inner Transaction Execution (external site) · XRPScan — XRPScan amendments API (external site)
-
Tenfold block reward boost activated at height 5,110,000
Feature 23 (Boost Block Reward), shipped in node 1.5.6 in July 2024, activated on mainnet at height 5,110,000, whose block is timestamped 24 February 2026. For the next 300,000 blocks the total block reward was multiplied by ten, from 6 to 60 WAVES, split equally between the block producer, the Waves DAO treasury and the XTN buy-back contract.
- Proposal:shipped for mainnet voting in node 1.5.6 (July 2024)
- Implementation:implemented in the reference node
- Release:mandatory release 1.5.6
- Activation:activated at height 5,110,000; boost period ended at height 5,410,000
Sources: Waves public node pool (nodes.wavesnodes.com) — Waves mainnet feature activation status (node REST API, read at height 5,419,632) (external site) · Waves public node pool (nodes.wavesnodes.com) — Waves mainnet block header at height 5,110,000 (node REST API) (external site) · Waves documentation (docs.waves.tech) — Features (external site) · wavesplatform on GitHub — Waves node v1.5.6 release notes (external site) · Waves documentation (docs.waves.tech) — Community-Driven Monetary Policy (external site)
-
Delegates halted IoTeX after the ioTube bridge exploit and restarted it with an address blacklist
On 21 February 2026 an attacker upgraded ioTube's Ethereum-side validator contract with a stolen owner key, minted 410 million CIOTX and drained about $4.4 million of bridge reserves. IoTeX says its delegates suspended the chain the same day. They restarted it on 24 February at 06:06 UTC on node release v2.3.4, which blacklists 29 attacker addresses; v2.3.5 enforces the list from block 45,404,174. IIP-56 later deprecated CIOTX on every network, and the IoTeX Foundation opened a claims portal to compensate affected holders.
- Implementation:blacklist shipped in iotex-core v2.3.4; height-gated enforcement added in v2.3.5
- Release:v2.3.4 published 2026-02-23 (its release note labels it recommended) and run by delegates to restart the chain
- Activation:chain resumed 2026-02-24 06:06 UTC per IoTeX; enforcement from block 45,404,174
Sources: IoTeX blog — Security Incident Update: ioTube Bridge Exploit and Recovery Roadmap (external site) · IoTeX blog — ioTube Bridge Incident Update No.2: Chain Resumed, Recovery Underway (external site) · IoTeX (iotex-bootstrap, GitHub) — v2.3.4 release note (external site) · IoTeX (iotex-bootstrap, GitHub) — v2.3.5 release note (external site) · IoTeX blog — How IoTeX Responded to the ioTube Bridge Incident: A Full Month in Review (external site) · IoTeX Improvement Proposals (GitHub) — IIP-56: Deprecation of CIOTX Across All Networks (external site)
-
Foundation closed its interim Hyperscale research phase after a public test
The interim Hyperscale lead reported that a public test on 31 January 2026 sustained the throughput target set for it, using swap transactions across 128 shards with cross-shard atomic transactions, on commodity cloud machines plus community nodes; a private test showed per-shard throughput holding when the shard count doubled. The closing post hands the work to the community and says the Foundation intends to open-source the remaining code and publish the test setup and network configuration, with no date because parties outside the Foundation must agree. Hyperscale is a research network, not Radix mainnet.
- Implementation:research network tested; not integrated into mainnet software
- Release:no release; open-sourcing of remaining code pending
- Activation:not activated on mainnet
Sources: Radix Blog — Interim Hyperscale: Closing the Chapter (external site) · Radix Blog — Hyperscale Update: 500k+ Public Test Done (external site) · RadixTalk (community-run) — [RFC] Xi'an: Delivering Hyperscale for Radix (external site)
-
Protocol work reorganized around scaling, UX and L1 hardening
The 2026 priorities described Scale, Improve UX and Harden the L1 tracks while summarizing Pectra and Fusaka as 2025 upgrades. Roadmap ideas are not activation promises.
- Type:Roadmap
- Proposal:Mixed
- Release:Mixed
- Activation:Mixed
Source: Ethereum Foundation — Protocol Priorities Update for 2026 (external site)
-
PowPeg signer set changed and maximum signer count raised
Rootstock announced a PowPeg composition change in which Collider left the signer set and a new signer run by RootstockLabs, using an Intel SGX-based hardware module audited by Quarkslab, joined. The set stayed at nine signers with the same threshold, and the maximum supported signer count had been raised from 9 to 20.
- Proposal:on-chain vote by the signers completed
- Implementation:composition change scheduled
- Release:not a software release
- Activation:scheduled for Rootstock block 8,558,281; the current PowPeg page lists nine members without Collider
Sources: Rootstock — PowPeg Composition Change: Signer Set Update (external site) · Blockscout — Rootstock block 8,558,281 (API record) (external site) · Rootstock — PowPeg (external site)
-
Token escrow, permissioned domains and permissioned DEX enabled on mainnet
Three amendments took effect in February 2026: PermissionedDomains, TokenEscrow, which lets opted-in trust-line tokens and Multi-Purpose Tokens be held in escrow, and PermissionedDEX, which adds order books open only to accounts holding credentials accepted by a domain.
- Proposal:TokenEscrow and PermissionedDEX introduced in server version 2.5.0; PermissionedDomains in 2.4.0
- Implementation:implemented in the reference server
- Release:Released
- Activation:enabled on mainnet in February 2026 per explorer amendment data
Sources: XRPScan — XRPScan amendments API (external site) · XRP Ledger documentation (xrpl.org) — Escrow (external site) · XRP Ledger documentation (xrpl.org) — Permissioned DEXes (external site)
-
Dash Core 23.1.0 speeds up InstantSend processing and adds experimental hardware signing
Dash Core 23.1.0 changed how nodes prioritise and relay quorum messages and process signature shares to speed up InstantSend, added a dust-attack protection option, declared descriptor wallets no longer experimental and added experimental support for handing signing to an external hardware device. It had no breaking changes but was required for masternodes.
- Implementation:shipped in Dash Core 23.1.0
- Release:stable release published 2026-02-14; later 23.1.x patch releases followed
- Activation:no consensus change; took effect as nodes upgraded
Sources: Dash Core developers (dashpay) — Dash Core 23.1.0 release announcement (external site) · Dash Core developers (dashpay) — Dash Core v23.1.0 release notes (external site)
-
Beam described Beam Warp as a staked sidechain
Beam described Beam Warp as a delegated proof-of-stake sidechain. Staking, rewards, slashing and jailing run in a contract, BEAMX holders stake through validators to earn sidechain fees, and a two-way bridge locks funds on the main chain and releases them by validator multisignature.
- Implementation:delegated proof-of-stake contract completed on developer networks
- Release:no public release
- Activation:not on mainnet
Source: Beam blog — Beam Warp Development Update #1 (external site)
-
Blast mainnet v1.7.0 and v1.8.0 fixed the blob fee schedule
Blast released node software v1.7.0 for mainnet with fixes to the blob fee schedule; Blast's blog says it activated on 12 February 2026. A day later v1.8.0 supplied a missing default value from v1.7.0 and was scheduled to activate on 13 February 2026. Operators of the rollup node had to add new blob-schedule settings.
- Implementation:released as v1.7.0 and v1.8.0
- Release:mainnet releases published 2026-02-11 and 2026-02-12
- Activation:v1.7.0 activated 2026-02-12 by timestamp per the blog note; v1.8.0 scheduled by timestamp for 2026-02-13, with no separate confirmation found
Sources: Blast contributors — Release v1.7.0 (MAINNET) (external site) · Blast contributors — Release v1.8.0 (MAINNET) (external site) · Blast — Release v1.7.0 (MAINNET) (external site) · Blast contributors — Releases: blast-io/blast (external site)
-
Immutable X was shut down and remaining funds moved to Immutable zkEVM
Immutable sunset its older StarkEx-based network, Immutable X, with 11 February 2026 as the last day for manual withdrawals. Between 5 and 9 March 2026 an upgrade of the Immutable X bridge moved remaining user funds to Immutable zkEVM, where a contract pays them out only against proofs of ownership from the final Immutable X state.
- Implementation:migration and disbursement contracts deployed; Nethermind audit published
- Release:Immutable X sequencer no longer accepts transactions; marketplace removed
- Activation:complete: automated migration ran 5 to 9 March 2026
Sources: Immutable (GitHub) — Immutable X Asset Migration Contracts (external site) · Immutable Documentation — Immutable X Deprecation (external site)
-
Pakistan Digital Authority and DFINITY signed an MoU for a dedicated Pakistan subnet
DFINITY's media release says the Pakistan Digital Authority and the DFINITY Foundation signed a memorandum of understanding covering a dedicated Pakistan subnet described as a sovereign cloud, a national messenger app being piloted, 1,500 Caffeine licences and a local DFINITY presence.
- Proposal:memorandum of understanding
- Implementation:not verified
- Release:Planned
- Activation:no evidence of an active Pakistan subnet in this review
Sources: Internet Computer (internetcomputer.org) — Pakistan Digital Authority and DFINITY partner on sovereign cloud infrastructure (external site) · Internet Computer (internetcomputer.org) — Media releases (external site)
-
Robinhood announced the public testnet
Robinhood's February 10 newsroom post announced a live developer public testnet; Arbitrum cross-confirmed the live testnet in a February 11 post. This was a testnet milestone and does not by itself establish the later mainnet launch.
- Type:Testnet
- Proposal:Completed announcement
- Release:Public testnet announced live
- Activation:Testnet only at publication superseded for mainnet status
Sources: Robinhood — Robinhood Chain Launches Public Testnet (external site) · Arbitrum — Robinhood Chain Launches Testnet on Arbitrum, Commits $1M to Jumpstart Developer Ecosystem (external site)
-
Token holders elected a five-member Radix Accountability Council
A consultation weighted by XRD, run from 30 January to 6 February 2026, chose a five-member council from 22 nominees to guide the move from the Foundation to a community structure; about 1.34 billion XRD from 1,151 accounts took part. The council's remit is to set up its operating framework, coordinate transition tasks and act as the interface between the community and the Foundation. A separate consultation, published on 13 February, approved tapering the Foundation's validator subsidy to zero by June 2026.
- Proposal:consultation opened 30 January 2026
- Implementation:council elected
- Release:results published 7 February 2026
- Activation:council setting up the DAO entity, per the Foundation's April 2026 update
Sources: Radix Blog — Consultation Results: Radix Accountability Council (external site) · Radix Blog — Consultation Results: The Future of the Validator Subsidy (external site) · Radix Blog — Foundation Update: Moving to Maintenance Mode (external site)
-
ICON Foundation announced a phased halt to ICX emissions and a seven-node validator set
The Foundation set out five phases: a governance vote to remove the 1% validator bond (16 February), four added Foundation nodes (2 March), moving Foundation delegations so seven core nodes hold ranks 1 to 7 (16 March), excluding nodes ranked eighth and below from consensus (23 March), and an economic shutdown ending new ICX emissions (26 March). It said the chain would stay live for transactions and migration to SODA.
- Proposal:bond-removal governance vote announced for 16 February 2026
- Implementation:phased plan announced
- Release:Announced
- Activation:the Foundation's 26 March 2026 post says emissions ended and seven core nodes run consensus
Sources: ICON Foundation — ICON Network Phased Halt to Emissions (external site) · ICON Foundation — ICON Network: Economic Shutdown (external site)
-
Stake holders approved the four Mesa proposals in an on-chain vote
o1Labs reported that the December 2025 on-chain vote on MIP6 to MIP9 (faster slots, larger zkApp state, higher event and action limits, more account updates) ended with 100% of votes cast in favour. The same update said testnet stress tests found memory spikes and that the planned per-block cap on zkApp transactions was halved to limit node memory use.
- Proposal:approved by on-chain memo vote
- Implementation:in testing at the time of the post
- Release:not yet released at the time of the post
- Activation:later activated on mainnet 2026-09-03
Sources: Mina Protocol blog (o1Labs) — Road to Mesa: Status Update (Feb 2026) (external site) · Mina Protocol blog — The Mesa Upgrade On-Chain Vote (external site)
-
Ronin's Saigon testnet completed its move to the OP Stack
Ronin announced that its Saigon testnet had migrated to an OP Stack Layer 2 with Optimism and Conduit, as a rehearsal for mainnet, and told node operators to switch to reth and op-node.
- Proposal:OP Stack adoption voted by governing validators in 2025
- Implementation:completed on testnet
- Release:testnet only
- Activation:active on Saigon testnet
Sources: Ronin blog — The Saigon Testnet Migration is Complete (external site) · Ronin blog — Powering Ronin's Homecoming to Ethereum (external site)
-
x402nano published open-source tools for paying web APIs in XNO
A community developer published x402nano, open-source packages for the x402 HTTP payment protocol on Nano: a payment scheme, helpers and a facilitator that verifies Nano blocks inside payment requests and settles them through a Nano RPC node. The earliest commits date from 5 February 2026 and the facilitator's from 6 March 2026. The Nano Foundation's May round-up groups it with other agent-payment tools and says the first autonomous agent payments on mainnet came in early 2026.
- Implementation:open-source packages published on GitHub
- Release:published; no audit found
- Activation:no protocol change; each service adopts it separately
Sources: x402nano (GitHub) — x402nano schemes commit feed (external site) · x402nano (GitHub) — x402nano facilitator (external site) · x402nano (GitHub) — x402nano (external site) · Nano Foundation (Nano Blog) — Nano Ecosystem Round Up of 2026 So Far (external site)
-
java-tron GreatVoyage-v4.8.1 (Democritus) released as a mandatory upgrade
The TRON developer community released GreatVoyage-v4.8.1 (Democritus) as a mandatory upgrade and asked nodes to upgrade by 23:59 Singapore time on 9 March 2026. It adds ARM64 support with JDK 17, changes SELFDESTRUCT to match Ethereum's EIP-6780 behaviour (TIP-6780), moves the proposal voting window into chain governance (TIP-767), adds peer-to-peer message rate limits and new APIs for live SR vote counts.
- Proposal:TIP-6780 and TIP-767 referenced in the release notes
- Implementation:shipped in java-tron v4.8.1
- Release:mandatory release; upgrade deadline 2026-03-09 23:59 SGT
- Activation:SELFDESTRUCT restriction shown enabled on mainnet in a 2026-09-27 parameter query; activation date not verified
Sources: tronprotocol (GitHub) — GreatVoyage-v4.8.1 (Democritus) release notes (external site) · TRON Developer Hub — Release Announcements (external site) · TRON Developer Hub — TVM vs EVM (external site) · TronGrid — Chain parameters (public API response) (external site)
-
B² announces B² Mind, an AI agent skill platform
B² announced B² Mind, a service in which AI agents turn a user's plain-language request into planned on-chain actions drawn from a library of skills, then ask the user to sign. B² says skills never hold private keys or send transactions themselves, and that each plan is simulated and risk-rated before the user confirms.
- Implementation:announced as launched
- Release:not a protocol release
- Activation:availability not independently verified
Source: B² Network — B² Network on Medium (RSS feed) (external site)
-
Sonic announced a mainnet move to runtime v2.3.0
Sonic said it would migrate mainnet to new hardware and upgrade the runtime from v1.18.23 to v2.3.0, with about three hours of planned downtime starting 4 February 2026 and no endpoint or code changes for developers.
- Implementation:migration scheduled by the operator
- Release:v2.3.0
- Activation:public RPC reported v2.3.0 on 2026-09-27
Source: Sonic SVM — Sonic Mainnet Infrastructure Upgrade Notice (external site)
-
Seven companies join the Liquid Federation, bringing membership to 87
The Liquid Federation added Cowbolt, Eulen, illuminodes, Mooze, OrderMoon, Sorted Wallet and SOUSTA, bringing total membership to 87.
- Implementation:membership change
- Release:Announced
- Activation:members admitted
-
Horace hard fork lowered issuance and cut the locked-stake reward weight
PIP Labs released story v1.5.2 (Horace), a mandatory hard fork at mainnet block 13,780,500 that implements SIP-00009: yearly issuance moves from about 25.3 million tokens, the result of the original per-block rate and a faster block rate, to 15,315,000, and the reward weight of locked-token delegations drops from 0.5 to 0.025. Locked and unlocked stake keep equal voting power.
- Proposal:SIP-00009 posted on the forum on 18 January 2026
- Implementation:shipped in story v1.5.2
- Release:mandatory hard-fork release
- Activation:took effect at mainnet block 13,780,500, which the official explorer dates to 5 February 2026; the live parameters were not read in this review
Sources: PIP Labs (GitHub) — Horace (Story v1.5.2) release notes (external site) · DATA Foundation forum — [Proposal] SIP-00009: Emissions Recalibration & Locked Staking Multiplier Adjustment (external site) · DATA Foundation Docs — Staking Design (external site) · Datanetscan — Block 13,780,500 (Horace upgrade height) in the Datanetscan API (external site)
-
Osmosis v31.0.1 moved to the CometBFT version that fixes the Tachyon block-time flaw
Osmosis v31.0.1 was released on 27 January 2026. Its only listed change moves the node software to CometBFT v0.38.21. Four days earlier CometBFT published advisory CSA-2026-001, known as Tachyon and rated critical. The advisory says a mismatch between how commit signatures are checked and how block time is calculated let faulty validators push block timestamps forward. It lists CometBFT v0.38.20 and earlier as affected, names v0.38.21 as the patched v0.38 version and says upgrading is the only fix.
- Implementation:CometBFT v0.38.21 included in Osmosis v31.0.1
- Release:released 2026-01-27
- Activation:takes effect on each node when its operator installs it; how many validators run it was not checked
Sources: Osmosis maintainers — Osmosis v31.0.1 release (external site) · CometBFT maintainers — CSA-2026-001: Tachyon (GHSA-c32p-wcqj-j677) (external site) · Osmosis maintainers — Osmosis v31.0.0 go.mod (external site) · Cosmos chain-registry maintainers — Osmosis chain registry record (external site)
-
Runtime 2.0.5 enacted: capped DOT issuance, Hub smart contracts and 2-second Hub blocks
Referendum 1828 enacted Fellowship runtime 2.0.5, which put Referendum 1710's capped, stepped issuance schedule on-chain, added smart contracts (pallet-revive) to Polkadot Hub and enabled elastic scaling for 2-second Hub blocks. The first issuance step took annual issuance from 120 million to about 55.8 million DOT on 2026-03-14.
- Proposal:Referendum 1710 (issuance) and Referendum 1828 (upgrade) executed
- Implementation:implemented in Fellowship runtimes 2.0.5
- Release:released 2026-01-13
- Activation:enacted 2026-01-27; first issuance step on 2026-03-14
Sources: Polkadot Forum — Polkadot Digest 26 January 2026 (external site) · Subsquare (Polkadot OpenGov) — Referendum 1828: Polkadot Upgrade 2.0.5 (external site) · Polkadot Fellowship (GitHub) — Runtimes 2.0.5 (external site) · Subsquare (Polkadot OpenGov) — Referendum 1710: Hard Pressure Capped & Stepped Supply Schedule (external site) · Polkadot Forum — Changes on Polkadot in March 2026 (external site) · Polkadot Forum — Polkadot Staking Changes: Progress & Timeline (external site)
-
FIP-441 fixed FRAX supply and set out a move of Frax governance to Fraxtal
The Frax Core Team proposed capping FRAX, Fraxtal's gas coin, at 143 million with yearly spending caps, dropping the planned long-term tail emission and providing a path to move vote-escrowed positions from Ethereum to Fraxtal. In the thread, a Frax Core Team reply says Fraxtal gas-fee flows will be recycled rather than burned. The appendix reports the North Star hard fork, which made FRAX the gas coin, as complete.
- Proposal:approved in a Snapshot vote closing 2026-02-05
- Implementation:partly implemented; the veFRAX migration was listed as not yet built in the proposal
- Release:not a software release
- Activation:policy in effect; implementation status not verified
Source: Frax governance forum — [FIP-441] $FRAX: 1 Token, 1 Mission, 1 Vision (external site)
-
Governance restores Archway's IBC client to Injective, which later lapses again
Proposal 60 passed with no votes against and replaced the expired light client for injective-1 with the state of a fresh client, reopening the existing Injective channels. When checked on 2026-09-27, the same client was listed as expired again.
- Proposal:proposal 60 passed
- Implementation:client substitution executed by the proposal
- Release:no software release needed
- Activation:expired again as of 2026-09-27
Sources: Archway on-chain state via Archway Foundation REST endpoint — Archway proposal 60: Recover IBC light client for Injective (external site) · Archway on-chain state via Archway Foundation REST endpoint — Archway IBC client 07-tendermint-67 status (Injective) (external site) · Archway on-chain state via Archway Foundation REST endpoint — Archway governance proposals (latest 30) (external site)
-
Tallinn upgrade activated: six-second blocks on Tezos layer 1
Tezos activated its 20th protocol upgrade, Tallinn, on 24 January 2026 at block 11,640,289. It cut the minimum block time from 8 to 6 seconds, bringing two-block finality to about 12 seconds, added a mode in which all bakers attest every block once half of active bakers use BLS consensus keys, and added an address-indexing registry to shrink contract storage.
- Proposal:adopted by on-chain vote
- Implementation:implemented in Octez
- Release:released with supporting Octez versions
- Activation:active on mainnet since 2026-01-24; all-bakers-attest feature awaiting its adoption threshold
Sources: Nomadic Labs on Tezos Spotlight — Faster Blocks, Stronger Security, Improved Storage: Tallinn is Live! (external site) · Tezos documentation (docs.tezos.com) — History of amendments (external site) · Tezos Commons on Tezos Spotlight — Month At A Glance: August 2026 (external site)
-
Aurora Engine 3.10.1 released; mainnet engine reports 3.10.1
Aurora Labs published engine 3.10.0 on 2026-01-14 and 3.10.1 on 2026-01-23. The releases include Osaka-era precompile changes (including secp256r1), updated gas rules for newer Ethereum transaction types and the removal of legacy ETH-connector code from the engine. On 2026-09-27 the deployed mainnet contract reported version 3.10.1.
- Implementation:Released
- Release:3.10.0 on 2026-01-14; 3.10.1 on 2026-01-23
- Activation:mainnet engine reported 3.10.1 on 2026-09-27
Sources: Aurora Labs — Aurora Engine Release 3.10.0 (external site) · Aurora Labs — Aurora Engine Release 3.10.1 (external site)
-
Kava node software v0.28.2 updates its CometBFT consensus engine
Kava Labs published node software v0.28.2. Its release notes list one change: the bundled CometBFT consensus engine moves to v0.37.18. The notes give no upgrade height, do not say whether the update is required and describe no change for wallet or app users. It was the newest release on Kava's release page on 27 September 2026, and Kava Labs' public API node reported running it that day.
- Implementation:CometBFT dependency updated to v0.37.18
- Release:released 23 January 2026; newest release on 27 September 2026
- Activation:no network-wide activation height given; Kava Labs' API node reported v0.28.2 on 27 September 2026
Sources: Kava-Labs/kava on GitHub — Kava v0.28.2 release notes (external site) · Kava-Labs/kava on GitHub — Kava node software releases (Atom feed) (external site) · Kava Labs public REST endpoint — Kava node and application version (REST endpoint) (external site)