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 14 of 14.
One chain's developments, A to Z
-
Berachain halted, then used hard forks to freeze and unfreeze accounts after a BEX exploit
After the Balancer V2 exploit of 3 November 2025 reached liquidity pools on BEX, which Berachain's docs say shares Balancer V2's vault vulnerabilities, validators coordinated to halt the chain while the core team prepared a hard fork. Bera-Reth v1.2.0, released on 4 November, carried the Prague3 fork, which its notes say prevents the exploiter from stealing user funds and freezes use of BEX vaults. Bera-Reth v1.3.0, released on 7 November, carried Prague4, scheduled for 12 November 2025 at 16:00 UTC, which undid the account and transfer freezes.
- Implementation:Bera-Reth v1.2.0 (Prague3) and v1.3.0 (Prague4)
- Release:Released
- Activation:Prague3 activation time not stated in its release notes; Prague4 scheduled for 2025-11-12 16:00 UTC
Sources: Berachain (GitHub) — bera-reth v1.2.0 (Prague3 emergency hard fork) (external site) · Berachain (GitHub) — bera-reth v1.3.0 (Prague4 hard fork) (external site) · The Block — Berachain halts network to conduct emergency hard fork amid $128 million Balancer exploit (external site)
-
Polkadot balances, staking and governance moved to Asset Hub
The Asset Hub migration moved balances, staking, governance, proxies, multisig and vesting from the Polkadot relay chain to Asset Hub (Polkadot Hub). The existential deposit fell from 1 DOT to 0.01 DOT, and supported assets can now pay fees.
- Implementation:implemented in Fellowship runtimes 2.0.0
- Release:released 2025-10-28
- Activation:completed on Polkadot on 2025-11-04, per the wiki
Sources: Polkadot Wiki — Asset Hub Migration (external site) · Polkadot Fellowship (GitHub) — Runtimes 2.0.0 (external site) · Subscan — Polkadot relay chain explorer (external site)
-
Qtum Core v29.1 hard fork released
Qtum released Qtum Core v29.1, a mandatory hard fork that rebased the node on Bitcoin Core 29.1 and added Pectra-era contract features, including a BLS12-381 precompile and a contract for looking up older block hashes. It activated at block 5,483,000, which the explorer dates to 12 January 2026.
- Implementation:Released
- Release:released 2025-11-04
- Activation:activated at block 5,483,000 on 2026-01-12
Sources: Qtum project — Qtum Core v29.1 - Hard Fork - Upgrade to bitcoin core 29.1 - EVM Pectra (external site) · Qtum Blog — What's Included in the Qtum v29.1 Hard Fork? (external site) · qtum.info — qtum.info block 5,483,000 (external site) · Qtum Blog — Qtum Development Updates for 2026 (external site)
-
BounceBit Prime added Standard Chartered custody with OKX collateral mirroring
BounceBit announced that Prime's tokenised Treasury strategies would pair custody at Standard Chartered with trading on OKX, where collateral is mirrored to the exchange instead of being deposited there.
- Implementation:described as live by BounceBit
- Release:announced 3 November 2025
- Activation:not independently verified
Sources: BounceBit — BounceBit, OKX and Standard Chartered Expand Institutional Access to Tokenized U.S. Treasury Yield Strategies via Collateral Mirroring Program (external site) · BounceBit — Architecture (external site) · BounceBit — BounceBit Prime introduction (external site)
-
Osmosis v31 approved: automatic OSMO burns and a higher minimum gas price
Governance proposal 990 passed and scheduled the v31 upgrade at height 47,626,000. The release automates burning of the burn share of taker-fee OSMO, applies the same burn and staker split to OSMO bought back with other tokens, spreads staker payouts from taker fees over several epochs, adds an inflation endpoint and triples the consensus minimum gas price to 0.03 uosmo per unit of gas.
- Proposal:proposal 990 passed
- Implementation:released as v31.0.0, with patch releases through v31.0.3
- Release:released 2025-10-27
- Activation:applied at height 47,626,000 per on-chain upgrade record
Sources: Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 990: Osmosis v31 Software Upgrade (on-chain record) (external site) · Osmosis maintainers — Osmosis v31.0.0 release (external site) · Osmosis maintainers — Osmosis changelog (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Applied upgrade plan v31 (on-chain query) (external site)
-
Manta launches Manta Labs, an application program not tied to Manta Pacific
Manta announced Manta Labs to build and incubate consumer applications and to support developers on whichever chain suits each app, including chains other than Manta's own. The post named two apps it had incubated, SUPERFORTUNE and Junk.fun, and promised support for developers regardless of platform. By September 2026 Manta's home page leads with Incognitive, an on-device AI assistant, alongside Manta Pacific.
- Implementation:program announced; incubated apps named
- Release:not a software release
- Activation:no protocol activation
Sources: Manta Network (Medium) — Manta Network blog (RSS feed) (external site) · Manta Network — Manta Network home page (external site)
-
Runtime 1900 made new collators subject to governance approval
Referendum 44 enacted runtime 1900, which replaced open collator registration with an application flow: a candidate posts an application on the Astar forum for at least 7 days, then reserves the 3,200,000 ASTR bond on chain and is approved by two thirds of the Main Council or a referendum. The same runtime added the Tokenomics 3.0 decay factor and preparations for Polkadot's Asset Hub migration.
- Proposal:passed as referendum 44
- Implementation:shipped in runtime 1900
- Release:runtime-only release; no client upgrade required
- Activation:enacted on Astar mainnet on 2025-10-29
Sources: Subsquare (Astar democracy) — Referendum 44: Astar Runtime 1900 Upgrade (Asset Hub migration prep, tokenomics decay, collator governance) (external site) · Astar Forum — Astar Collator System Update: Transitioning to Governance-Approved Collator Selection (external site) · Astar Docs — Collator Requirements (external site)
-
Neo X opened its core repositories
Neo made eight Neo X repositories public on GitHub: its geth-based node, documentation, the EVM and NeoVM sides of the Neo X and Neo N3 bridge, threshold-encryption libraries and examples, the MPC ceremony and a zero-knowledge key-generation library. The post says Neo X had been developed out of public view until then.
- Implementation:repositories published
- Release:source published; not a protocol release
- Activation:no network change
Source: Neo — Opening the Neo X Core Repositories to the Community (external site)
-
Beta v4.0 replaced Clique with the Maru consensus client and brought Linea up to Ethereum's Pectra rules
Linea's Beta v4.0 release, rolled out on mainnet in phases between 22 and 28 October 2025, introduced Maru, a consensus client using the QBFT algorithm, in place of the Clique proof-of-authority mechanism, and applied about four years of Ethereum upgrades up to the Pectra hard fork. Maru's mainnet configuration starts QBFT at the first (Paris) phase with a single validator. Since then every Linea node runs Maru beside its execution client.
- Implementation:Maru consensus client released and required for nodes
- Release:Beta v4.0
- Activation:Maru QBFT block production from the Paris phase on 22 October 2025; release complete with the Prague phase on 28 October 2025
Sources: Linea Documentation — Release notes (external site) · Linea Documentation — Maru (external site) · Linea Documentation — Run a Linea node (external site) · Linea Documentation — Besu (external site) · Lineth (GitHub) — Maru Linea Mainnet genesis configuration (linea-mainnet-genesis.json) (external site)
-
Hayabusa upgrade moved VeChainThor from authority nodes to delegated proof of stake
Thor v2.4.0 was released as a mandatory upgrade activating the Hayabusa hard fork at mainnet block 23,414,400. It implements VIP-253, which opens validation to anyone locking 25 million VET in a leader group capped at 101 and routes delegation through StarGate, and VIP-254, which ends passive VTHO generation for VET holders and pays VTHO rewards only to staked VET. Finality became stake-weighted.
- Proposal:VIP-253 and VIP-254, both still marked Draft in the VIP repository
- Implementation:shipped in Thor v2.4.0
- Release:mandatory release published 2025-10-28
- Activation:fork block produced 2025-12-02; the transition window ended at block 23,474,880 on 2025-12-09, and the foundation reports the move to delegated proof of stake completed in December 2025
Sources: vechain/thor maintainers — Thor v2.4.0 release notes (Hayabusa hardfork) (external site) · VeChain VIPs repository — VIP-253: Upgrade consensus to Delegated Proof of Stake (DPoS) (external site) · VeChain VIPs repository — VIP-254: Upgrade tokenomics of VeChain DPoS (external site) · VeChain (public node, Thorest API) — Mainnet block 25,902,540 (Interstellar fork height) (external site) · VeChain — VeChain Roadmap 2026: Agentic Foundations for Tomorrow & Beyond (external site) · VeChain — Institutional Validators: Building The New Backbone of VeChain (external site)
-
Forte network upgrade went live on Flow mainnet
Flow announced that the Forte upgrade was live, adding protocol-scheduled transactions, passkey (WebAuthn) signing, 128-bit fixed-point types in Cadence, and a node database move from BadgerDB to PebbleDB that Flow says cut memory and CPU use.
- Implementation:Deployed
- Release:released with spork 27 (v0.43.3)
- Activation:live on mainnet per Flow
Sources: Flow Foundation — The Forte Network Upgrade: Now Live on Flow (external site) · Flow Documentation — Past Network Upgrades (external site)
-
iotex-core v2.3.0 scheduled the Xingu hard fork, which penalizes delegates that miss blocks
IoTeX released node version 2.3.0, a mandatory upgrade that enables IIP-50: a delegate whose block production falls below 85% in an epoch loses self-stake equal to the block reward times the blocks it missed, and is dropped from the delegate list if its self-stake falls below 1 million IOTX. The release also lets delegates register BLS public keys, preparing for aggregated block signatures (IIP-52). Activation was set for block 41,648,761, estimated for 4 November 2025.
- Proposal:IIP-50, created 2025-07-02; the file's status field still reads draft
- Implementation:shipped in iotex-core v2.3.0
- Release:mandatory release published 2025-10-22
- Activation:scheduled for block 41,648,761 (estimated 2025-11-04); mainnet was past that height on 2026-09-29
Sources: IoTeX (GitHub) — iotex-core v2.3.0 release (Xingu hard fork) (external site) · IoTeX Improvement Proposals (GitHub) — IIP-50: Slash Underperforming Delegates (external site) · IoTeX (iotex-core, GitHub) — blockchain/genesis/genesis.go (external site) · IoTeX Foundation — IoTeX mainnet Ethereum JSON-RPC endpoint (read 2026-09-29) (external site)
-
Nanswap published a run example for its separate NanUSD network built from Nano's node software
Nanswap offers NanUSD, a coin it says is backed 1:1 by USDC reserves, and later NanBTC, which it says is backed by BTC reserves. Both run on separate networks: Nanswap's nan-node repository is a modified Nano node with a customisable genesis block, and its NanUSD example starts a network with its own genesis account, address prefix and peering host. The NanUSD run example was added to the repository on 22 October 2025, and the Nano Foundation's round-up dates NanBTC to February 2026.
- Implementation:networks running according to the issuer's sites
- Release:launched by Nanswap
- Activation:live according to the issuer's sites; not independently checked
Sources: Nanswap — NANUSD: Zero Fee Stablecoin (external site) · Nanswap — NANBTC: Zero Fee Bitcoin (external site) · yxse (Nanswap) on GitHub — nan-node: Nano-node with customisable genesis block (external site) · yxse (Nanswap) on GitHub — nan-node commit feed (external site) · Nano Foundation (Nano Blog) — Nano Ecosystem Round Up of 2026 So Far (external site)
-
Plasma said it acquired an Italian licensed entity and plans EU license applications
Plasma said it had acquired a VASP-licensed entity in Italy, opened an office in the Netherlands and hired compliance officers, and that it plans to apply for a crypto-asset service provider license under the EU's MiCA rules and an electronic money institution license for cards, accounts and fiat access.
- Proposal:CASP and EMI license applications planned
- Implementation:Italian licensed entity acquired, per Plasma
- Release:Announced
- Activation:license outcomes not verified
Source: Plasma blog — Licensing Our Payments Stack to Reach Global Scale (external site)
-
Protocol 24 corrected smart-contract entries damaged by a Protocol 23 archival bug
After the foundation found on 9 October 2025 that Protocol 23 had archived some contract entries with outdated values, validators voted to pause the eviction of unused entries into the archive and ran a patched build that blocked transactions touching the 478 affected entries. Protocol 24, put to a Mainnet validator vote on 22 October 2025, reset the 394 affected entries that had never been restored to their correct pre-archival values and adjusted the fee pool; the other cases were left to the affected organizations.
- Proposal:CAP-76 final
- Implementation:shipped in Protocol 24 builds of the node software
- Release:stable releases scheduled for 20 October 2025
- Activation:Mainnet upgrade listed for 22 October 2025
Sources: Stellar Development Foundation — Addressing state archival inconsistencies: protocol upgrade vote next week (external site) · Stellar Protocol (GitHub) — CAP-0076: P23 State Archival bug remediation (external site) · Stellar Docs (Stellar Development Foundation) — Software Versions (external site)
-
Kadena LLC ended business operations
The company that built and maintained Kadena announced on its website that it ended business operations on 21 October 2025. Its website now shows only that notice.
- Implementation:company operations ended
- Release:not applicable
- Activation:effective 2025-10-21
-
Relayed transactions versions 1 and 2 were switched off
MultiversX's Barnard Patch 3 release (v1.10.8) scheduled the removal of the two older relayed-transaction formats at epoch 1918, expected on 30 October 2025, leaving only version 3, in which the relayer's address and signature are fields of the transaction itself. The mainnet configuration sets the same epoch.
- Implementation:implemented in node v1.10.7 and v1.10.8
- Release:v1.10.8 released 2025-10-21
- Activation:in effect from epoch 1918 (about 30 October 2025), as set in the mainnet configuration
Sources: MultiversX — Release: Barnard Patch 3 - v1.10.8 (external site) · multiversx/mx-chain-mainnet-config — Mainnet enableEpochs.toml (v2.1.5.0) (external site) · MultiversX Docs — Relayed Transactions (external site)
-
Noble v11 (Flux) adds the Orbiter cross-chain routing module
Release v11.0.0 added Orbiter, which accepts an incoming IBC transfer carrying instructions, can take a fee on Noble and forwards the funds over CCTP in one user transaction. Noble's launch post said Hyperlane forwarding and swap actions were not yet enabled; the current docs list Hyperlane forwarding as supported and swaps as not supported. It also allowed anyone to create Hyperlane collateral tokens for assets other than USDN and recovered expired IBC clients for two chains.
- Implementation:released as v11.0.0, with v11.0.1 and v11.1.0 follow-ups
- Release:released 2025-10-21
- Activation:activated at height 37,480,000 per Noble's mainnet upgrade table
Sources: noble-assets/noble maintainers — Noble v11.0.0 (Flux) release notes (external site) · Noble documentation — Mainnet Chain Upgrades (external site) · Noble documentation — x/orbiter (external site) · Noble — Orbiter: One-Click Cross-Chain Orchestration (external site)
-
dYdX Chain halted for about eight hours after a liquidation edge case
During extreme volatility on 10 October 2025, an ordering error in isolated-market liquidation logic made a collateral pool show a negative balance, and the protocol's safety stop halted the chain from about 5:35 PM ET until 1:41 AM ET on 11 October. Validators installed a patch to restart. Governance later approved paying 462,097.79 USDC from the insurance fund to affected users.
- Proposal:compensation proposal passed 1 November 2025
- Implementation:patch developed and installed by validators
- Release:Released
- Activation:chain restarted 11 October 2025
Sources: dYdX — October 2025 dYdX Chain incident review and community update (external site) · Allnodes public REST endpoint for dydx-mainnet-1 — Governance proposal 301: Compensate impacted Oct 10 incident users from Insurance Fund (external site)
-
Post-mortem published for the aggregate transaction hash fix activated by hard fork
A post-mortem first posted on the Symbol Syndicate's Notion site and reprinted by Symbol Community Web explains a bug found in September 2025: when an aggregate held a number of inner transactions that was not a power of two, a copy with duplicated final transactions could share its hash, which could have let a recipient replay a signed transfer and split the network. Catapult client v1.0.3.9 fixed it with aggregate version 3, which adds the embedded transactions' total size to the hash; the fork activated at block 4,759,100 on 25 September 2025. The post-mortem says no exploitation or stolen funds were found.
- Implementation:shipped in catapult client v1.0.3.9 and REST gateway v2.5.1
- Release:breaking-fork release published 2025-09-23
- Activation:activated at block 4,759,100 on 2025-09-25 per the post-mortem; only version 3 aggregates accepted since
Sources: Symbol Community Web (reprint of the Symbol Syndicate's post) — Post-mortem: Aggregate Transaction Hash Collision Vulnerability (October 2025) (external site) · Symbol (GitHub) — Catapult Client v1.0.3.9 release notes (external site) · Symbol (GitHub) — Catapult client changelog (external site) · Symbol (GitHub) — symbol-bootstrap mainnet network preset (external site) · Symbol Community Web (community-run) — Symbol blockchain network upgrade (external site) · Symbol (GitHub) — Rest Gateway v2.5.1 release notes (external site)
-
DFINITY opened Caffeine, an AI app builder that deploys to ICP, as a public beta
The Internet Computer history page records that the beta of Caffeine, a platform for building apps by chatting with an AI, was made publicly available at caffeine.ai on 15 October 2025; the project's Caffeine page presents the launch as DFINITY's. Caffeine writes a Motoko backend and deploys it as canisters on the Internet Computer.
- Implementation:product launched by DFINITY
- Release:public beta
- Activation:not a protocol change
Sources: Internet Computer (internetcomputer.org) — Network history (external site) · Internet Computer (internetcomputer.org) — Caffeine ecosystem spotlight (external site) · Caffeine — Caffeine - The AIware Generator (external site)
-
BSV Association released Teranode's source code for public use
The BSV Association announced the first public, source-available release of Teranode, its microservices-based node software. It reported a throughput result from a two-week trial on a globally distributed test network, recorded as a test-network figure in the Compare Profile, and said a handful of transaction processors were already running Teranode alongside SV Node, with wider phasing-in planned. Stable releases have followed, reaching v0.15.9 on 17 September 2026.
- Implementation:source-available code and releases published
- Release:public release announced 14 October 2025; latest stable v0.15.9
- Activation:no consensus change; in October 2025 the Association said a handful of transaction processors ran it alongside SV Node
Sources: BSV Association via PR Newswire — BSV Association (BSVA) announces public release of Teranode software (external site) · BSV Association (GitHub) — teranode releases (external site) · BSV Association (GitHub) — Teranode v0.15.9 release notes (external site) · BSV Association (GitHub) — teranode-quickstart (external site)
-
Snake8 hard fork made block production stake-weighted
Chiliz activated the Snake8 hard fork on mainnet at 11:00 CEST on 14 October 2025. Before it, each main validator produced roughly the same number of blocks; now each block's producer is drawn at random with a probability proportional to the CHZ staked on it, and no validator's share may fall below 1/(2N) of blocks. Client v2.6.0, published on 30 September 2025, set the fork time.
- Proposal:specified on the docs' Snake8 page
- Implementation:shipped in client v2.6.0
- Release:mainnet release published 2025-09-30
- Activation:activated on mainnet 2025-10-14 at 11:00 CEST, per Chiliz
Sources: Chiliz blog — Chiliz announces Snake8 hard fork to enhance validator performance and ecosystem incentives (external site) · Chiliz Chain Docs — October 2025: Snake8 Hard Fork (external site) · Chiliz (GitHub) — Chiliz Chain client v2.6.0 release notes (Snake8 mainnet) (external site) · Chiliz Chain Docs — Run a Chiliz Chain Node (external site)
-
Arweave node 2.9.5 released as a stability and performance update
Arweave node 2.9.5, prepared by the Digital History Association, rolls up six alpha builds into a bug-fix, stability and performance release. It fixes a mining bug that counted hashes over unpacked entropy, so miners' reported hashrate drops after upgrading; adds an optional faster VDF implementation; supports repacking data out of the replica.2.9 format; and adds metrics for endowment pool flows and the Kryder+ rate multiplier.
- Implementation:shipped in N.2.9.5
- Release:stable release that includes all 2.9.5 alpha changes
- Activation:no activation height; takes effect when each node upgrades
Sources: ArweaveTeam (GitHub) — Arweave 2.9.5 release notes (external site) · ArweaveTeam (GitHub) — arweave releases (external site)
-
Final Cut hardfork scheduled for block 552,100 to fix v2 difficulty and remove deprecated fields
The Sia Foundation announced a network upgrade, codenamed V2: The Final Cut, for block 552,100, estimated for the first week of December 2025. It closes out the v1 era by removing deprecated fields, fixes the v2 difficulty adjustment and prepares for parallel and instant syncing. All active nodes had to run walletd v2.11.0, hostd v2.4.0, renterd v2.7.0, minerd v0.3.2 or later to stay in consensus.
- Proposal:scheduled by the Sia Foundation
- Implementation:shipped in walletd v2.11.0, hostd v2.4.0, renterd v2.7.0 and minerd v0.3.2
- Release:supported versions released before the fork
- Activation:activated at consensus height 552,100, whose block SiaScan shows timestamped 2 December 2025; Sia's hardfork history describes it as deployed
Sources: Sia Foundation blog — V2 - The Final Cut: Network Upgrade Scheduled for December (external site) · Sia Foundation (Sia Docs) — V2: The Final Cut - Network Upgrade (December 2025) (external site) · Sia Foundation (GitHub) — coreutils chain/network.go: mainnet parameters and hardfork heights (external site) · Sia Foundation — Learn / Consensus / Hardforks (external site) · Sia Foundation (SiaScan) — SiaScan explorer API: consensus state (external site) · Sia Foundation (SiaScan) — SiaScan: Block 552,100 (external site)
-
Rio hardfork moved Polygon PoS to elected block producers
The Rio hardfork, scheduled for mainnet block 77,414,656 on 8 October 2025, replaced rotating block production with one validator-elected producer per span and added stateless block validation. Polygon said the combination practically ends chain reorganizations.
- Proposal:PIP-64 referenced in the release notice
- Implementation:released in Bor v2.3.0 and Heimdall v0.4.0
- Release:mainnet release announced
- Activation:announced as live by Polygon; block-level activation not independently checked
Sources: Polygon Labs — Polygon Launches Major Payments Upgrade with Rio (external site) · Polygon Community Forum — Bor v2.3.0 and Heimdall v0.4.0 release (Rio Hard Fork for VEBloP upgrade) (external site) · Polygon Labs — Heimdall Bor module: spans and producer selection (external site)
-
Babylon Labs put Bitcoin vaults ahead of multi-network staking and an EVM
Babylon Labs said it would focus engineering on Trustless Bitcoin Vaults and launch the planned networks secured by staked bitcoin, and an EVM on Babylon Genesis, only after the vaults. It said vaults would first integrate with mature DeFi protocols on large chains, starting with Ethereum, and be deployed on Babylon Genesis and other networks later.
- Proposal:announced roadmap
- Implementation:multi-network staking and EVM postponed
- Release:vaults on public testnet at review
- Activation:not active
Sources: Babylon Labs — A Vault First Roadmap - Catalysing Bitcoin DeFi (external site) · Babylon Labs — Bitcoin Staking script specification (external site) · Babylon Labs docs — Babylon Labs documentation home (external site) · Babylon Labs — Bitcoin Borrowing, Repriced (external site)
-
Company node 2.31: Pact 5.4 and a 20,000-block limit on cross-chain proofs, followed by point release 2.31.1
Kadena LLC published chainweb-node 2.31 as a mandatory upgrade. It moved the node to Pact 5.4 and made SPV proof roots, which are used to finish cross-chain transfers, expire after 20,000 blocks. The notes said older versions would stop working at 00:00 UTC on 15 October 2025 and scheduled the 2.31 rules for block height 6,269,344, estimated for 16 October 2025. Point release 2.31.1 followed on 10 October 2025, marked strongly recommended. The commit it links changed the service date for mainnet and testnet from 15 October 2025 to 7 January 2026. 2.31.1 was the last company release before the community fork of 8 November 2025.
- Implementation:implemented in 2.31; 2.31.1 corrected the mainnet and testnet service date
- Release:released 2025-10-07 (2.31, mandatory) and 2025-10-10 (2.31.1, strongly recommended)
- Activation:scheduled at height 6,269,344 (est. 2025-10-16); no activation notice reviewed. Inference: applied, as the final company cut shows every chain past that height
Sources: Kadena LLC — chainweb-node 2.31 (external site) · Kadena LLC — chainweb-node 2.31.1 (external site) · Kadena LLC — chainweb-node changelog (Kadena LLC) (external site) · Kadena LLC — chainweb-node 2.32.0 (external site) · Kadena Community Edition — chainweb-node Community Edition 3.1 (external site) · Kadena Community Edition — chainweb-node Community Edition 3.2 (external site)
-
Sigma 6.0 scripting upgrade activates on mainnet
Sigma 6.0 (EIP-50), a soft fork that extends ErgoScript, activated after miner voting. The first block carrying the 6.0 header version was block 1,628,160 on 6 October 2025. It adds an unsigned 256-bit integer type, serialization for all types, more numeric and collection methods, and methods for checking proof of work for custom Autolykos variants.
- Proposal:EIP-50
- Implementation:shipped in the 6.0 line of the reference node
- Release:6.0 node releases; 6.0.6 is the current stable release
- Activation:active from block 1,628,160 (6 October 2025) per explorer data and node source
Sources: ErgoDocs (Ergo Platform) — Sigma 6.0 Documentation Summary (external site) · Ergo Platform (GitHub) — Ergo reference node Header.scala (block header versions) (external site) · Ergo Platform (explorer API) — Ergo Explorer API: blocks 1,628,159 to 1,628,161 (external site) · ErgoDocs (Ergo Platform) — Ergo Explorer (external site) · ErgoDocs (Ergo Platform) — Sigma Chains (external site)
-
Oasis said the 2025 memory-bus TEE attacks did not affect its SGX deployment
After researchers published the Battering RAM and WireTap physical attacks, which extracted secrets from enclaves used by other networks, Oasis stated that its key manager and Sapphire run on an SGX version with a different memory-encryption design that was not affected, and that user privacy was not compromised. It also pointed to governance-gated key-manager membership, per-epoch key rotation and an updatable CPU blocklist.
- Implementation:statement published; mitigations described as already in place
- Release:no software release tied to the statement
- Activation:no network change announced
Sources: Oasis blog — Oasis statement on the Battering RAM and WireTap TEE attacks (external site) · WireTap research team — WireTap: Breaking Server SGX via DRAM Bus Interposition (external site) · TEE.fail research team — TEE.fail: Breaking Trusted Execution Environments via DDR5 Memory Bus Interposition (external site)
-
TRON connected to THORChain with TRX and USDT pools
THORChain announced that its TRON integration was complete, with native TRX and USDT on TRON available for swaps and liquidity against RUNE, and whitelisted TRC-20 tokens supported. TRON was still among the chains with active vault addresses in a 2026-09-29 read.
- Implementation:TRON chain client shipped
- Release:announced as complete
- Activation:TRON listed with an active vault address and trading not paused in the 2026-09-29 read
Sources: THORChain blog (Nine Realms) — TRON Integration Complete: Native TRX & USDT Swaps Live on THORChain (external site) · THORNode API, public endpoint run by Liquify — THORNode /thorchain/inbound_addresses via Liquify (read 2026-09-29) (external site)
-
Vaulta Foundation told producers it would make no protocol-level changes for the foreseeable future
At the September 2025 producer meeting, recapped by Vaulta on 1 October 2025, the Foundation's founder and CEO said it would step away from protocol-level work: no hard forks and no system contract adjustments, with effort moving to an external business product. The same meeting heard a proposal for a minimum producer stake, which the Foundation said would need a hard fork and is not on its roadmap, and guidance to move off Vaulta EVM before its October shutdown.
- Implementation:policy statement at a producer meeting
- Release:announced in the meeting recap
- Activation:no protocol change involved
Sources: Vaulta — Vaulta BP Meeting Recap: September 2025 (external site) · AntelopeIO (GitHub) — Spring releases (external site)
-
Multi-Purpose Tokens enabled on XRP Ledger mainnet
The MPTokensV1 amendment took effect, adding Multi-Purpose Tokens: a second fungible token type with one issuance record per token, an optional maximum supply, issuer-set transfer fees and opt-in lock and clawback controls. They cannot yet be traded on the built-in exchange.
- Proposal:MPTokensV1 amendment, introduced in server version 2.3.0
- Implementation:implemented in the reference server
- Release:Released
- Activation:enabled on mainnet 2025-10-01 per explorer amendment data
Sources: XRPScan — XRPScan amendments API (external site) · XRP Ledger documentation (xrpl.org) — Multi-Purpose Tokens (external site) · XRP Ledger documentation (xrpl.org) — Known Amendments (external site)
-
Algorand Foundation announced an Allbridge stablecoin bridge; Allbridge's documentation now lists Algorand as unsupported
The Algorand Foundation announced in September 2025 that Allbridge would integrate Algorand for a stablecoin bridge, expected in Q4 2025. At the 2026-09-27 review, Allbridge Core's Algorand guide said Algorand is no longer supported. Separately, Allbridge Core says its liquidity pools were discontinued in July 2026 and that transfers now run over Circle's cross-chain transfer protocol (CCTP) and LayerZero's OFT token standard; Circle's CCTP list does not include Algorand. Allbridge gives no date for ending Algorand support.
- Proposal:announced partnership
- Implementation:an Algorand integration guide exists in Allbridge's SDK documentation
- Release:announced for Q4 2025; launch date not verified
- Activation:no longer supported according to Allbridge Core documentation at review
Sources: Algorand Foundation — Allbridge and Algorand Partner to Launch Cross-Chain Stablecoin Bridge (external site) · Allbridge — Allbridge Core SDK guide: Algorand (external site) · Allbridge — What is Allbridge Core? (external site) · Circle — Supported blockchains and domains (CCTP) (external site)
-
Metis added a proposer registry that controls who may post state roots to Ethereum
L2BEAT's contract-change log records that Metis upgraded its state commitment contract on Ethereum to read the allowed state-root proposer from a new proposer registry, with one address holding the proposer role. L2BEAT says the Security Council minority controls the registry and so decides the active proposer.
- Implementation:deployed on Ethereum
- Release:contract upgrade recorded by L2BEAT
- Activation:active per L2BEAT
Sources: L2BEAT — Metis Andromeda (external site) · Etherscan — MVM_ProposerRegistry contract on Ethereum (external site)
-
Go-Pulse v3.3.0 rebases the execution client; PulseChain stays on Shanghai and Capella
PulseChain released Go-Pulse v3.3.0, which rebases the client onto upstream Go-Ethereum v1.13.14 through v1.16.3. The notes say the client carries code for newer upgrades for other networks but PulseChain remains on the Shanghai and Capella upgrades. They list breaking changes for node operators, including a new log-index format and changed RPC limits, and say path-based state storage is now the default for new syncs.
- Implementation:shipped in go-pulse v3.3.0
- Release:released 2025-09-30 as a major client update
- Activation:no activation; takes effect when each node upgrades, with no change to network rules
Sources: PulseChain (GitLab, go-pulse) — Go-Pulse v3.3.0 release notes (external site) · PulseChain (GitLab, go-pulse) — Go-Pulse releases (external site) · PulseChain (GitLab, go-pulse) — go-pulse params/pulse.go (PulseChain chain configuration) (external site)
-
Governance restores Archway's IBC client to XPLA
Proposal 59 passed with no votes against and replaced the expired light client to the XPLA chain with a fresh client's state, restoring transfers over the existing channels. The client was active when checked on 2026-09-27.
- Proposal:proposal 59 passed
- Implementation:client substitution executed by the proposal
- Release:no software release needed
- Activation:active as of 2026-09-27
Sources: Archway on-chain state via Archway Foundation REST endpoint — Archway proposal 59: Recover Expired IBC Client to XPLA Chain (external site) · Archway on-chain state via Archway Foundation REST endpoint — Archway IBC client 07-tendermint-29 status (XPLA) (external site) · Archway on-chain state via Archway Foundation REST endpoint — Archway IBC client states (external site)
-
OKT Chain staking rewards ended and unbonding was cut to 20 minutes
On 17 September 2025 on-chain governance set OKT Chain's reward deflation rate to zero, brought the next reward recalculation forward to block 38,892,300 so the zero rate applied at once, and cut the unbonding period to 20 minutes, after an earlier cut from 14 days to one day on 5 September. OKX Web3 said staking rewards stopped at 12:00 (UTC+8) that day and that its OKT liquid staking service had stopped staking and redemptions.
- Proposal:passed on-chain (proposals 103 to 106)
- Implementation:parameter changes applied through governance
- Release:no software release required
- Activation:active; no block rewards and a 20-minute unbonding period observed on 2026-09-27
Sources: OKX Web3 — OKX Web3's announcement on the OKT staking rewards (discontinuation notice) (external site) · OKX Web3 — OKX Web3's announcement on the OKT staking rewards (external site) · OKX public node — OKT Chain governance proposals (external site) · OKX public node — OKT Chain staking parameters (external site) · OKX public node — OKT Chain block rewards (external site)
-
OKX said it would stop supporting OKT Chain and converted exchange-held OKT to OKB
On 13 August 2025 OKX said it would gradually stop maintaining and supporting OKT Chain because it overlaps heavily with X Layer. OKT trading on OKX stopped that day, and from 15 August 2025 OKT held on the exchange was converted to OKB at the average closing prices from 13 July to 12 August 2025. OKX said the chain would remain operational until 1 January 2026 and that on-chain OKT could be deposited for conversion until then. On 27 September 2026 a public OKX node was still producing blocks, and no later OKX notice about the chain was found.
- Implementation:OKT trading stopped on 13 August 2025; conversion of exchange-held OKT to OKB began on 15 August 2025
- Release:no shutdown software release or halt height observed
- Activation:OKX's stated operating period ended on 1 January 2026; a public node still reported new blocks on 2026-09-27
Sources: OKX — Announcement on the PP Upgrade of X Layer and Optimisation of the OKB Gas-Token Economic Model (external site) · OKX — X Layer upgrade and OKT/OKB asset handling FAQ (external site) · OKX public node — OKT Chain Tendermint RPC status (external site)
-
Osmosis switched off superfluid staking for all pools
Governance proposal 956 removed every liquidity pool from superfluid staking, the feature that let pool shares count toward chain security, and approved removing the module in a later upgrade. The proposal said only about 39,000 OSMO was staked this way. Positions using it were unbonded when the change took effect.
- Proposal:proposal 956 passed
- Implementation:all pools removed by parameter change; full removal of the module was left to a later upgrade and was not confirmed
- Release:no software release needed for the pool removal
- Activation:active; no eligible pools on 2026-09-27
Sources: Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 956: Remove Superfluid Staking and Deprecate the x/superfluid Module (on-chain record) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis superfluid-eligible assets (on-chain query) (external site) · Osmosis documentation — Superfluid module (external site)
-
Metis released the Andromeda node upgrade that posts batch data as Ethereum blobs and adds fraud-proof support
Metis published node release v0.3.7, titled Andromeda Blob & Fraud prove, for the blob and fraud-proof upgrade on the Andromeda mainnet. It ships new l2geth and data transport layer (dtl) images and adds two settings: a fraud-proof start block of 22,482,000 and an Ethereum beacon-chain endpoint that each operator supplies so the node can read blob data. The dtl update is required for nodes that sync batches from Ethereum. The same upgrade went to the Metis Sepolia testnet first, as pre-release v0.3.6 in February 2025. L2BEAT dates Metis's switch to posting data as Ethereum blobs to 13 May 2025. It remains the latest Metis node release that changes how the network runs; the later v0.3.9 fixes network and tracing bugs, and its notes let operators update at their convenience.
- Implementation:tested first on the Metis Sepolia testnet through pre-release v0.3.6, published 12 February 2025
- Release:mainnet node release v0.3.7 published 13 May 2025; not marked pre-release
- Activation:release sets fraud-proof start block 22,482,000 without naming a date; L2BEAT dates the mainnet switch to blobs to 13 May 2025
Sources: Metis (GitHub) — v0.3.7 - Andromeda Blob & Fraud prove (external site) · Metis (GitHub) — v0.3.6 (external site) · Metis (GitHub) — mvm releases (external site) · L2BEAT — Metis Andromeda (external site) · Metis (GitHub) — metis-ansible: Deploy RPC with Ansible (external site)
-
Pectra was scheduled with client releases and later confirmed active on Mainnet
The April announcement scheduled Pectra for May 7, 2025 and listed execution and consensus client releases. The later ethereum.org upgrade page reports successful activation at epoch 364032. A release list was readiness evidence; the later network record is activation evidence.
- Type:Upgrade
- Proposal:Included
- Release:Mainnet client releases listed
- Activation:Activated mainnet
Sources: Ethereum Foundation — Pectra Mainnet Announcement (external site) · ethereum.org community — Prague-Electra (Pectra) (external site) · Ethereum contributors — Ethereum consensus specifications (external site) · Ethereum Foundation STEEL team — Ethereum execution-layer specifications (external site)
-
Archway v10.0.0: node release, governance vote and mainnet upgrade
The Archway team published node release v10.0.0 on 19 February 2025. Its notes list two changes: a fix to how Archway's IBC hooks connect to the contract (CosmWasm) module, and a CometBFT version bump. The forum draft of the upgrade, posted on 2 February 2025, described it as fixing IBC methods used by cross-chain contracts, including the IBC VerifyMembership query, and a later forum post named CometBFT 0.38.17. On-chain proposal 58 closed its vote on 28 February 2025, and the chain's upgrade record shows the plan applied at height 8,919,000. It is the most recent software upgrade put through Archway governance; the later v10.1.0 and v10.1.1 releases had no upgrade vote.
- Proposal:forum draft 2 February 2025; on-chain proposal 58 vote ended 28 February 2025 and its plan was applied
- Implementation:IBC hooks fix and CometBFT bump (0.38.17 per the forum) in the tagged v10.0.0 code
- Release:v10.0.0 published on GitHub 19 February 2025 after release candidates
- Activation:applied on mainnet at height 8,919,000 per the on-chain upgrade record; block date not checked here
Sources: archway-network — v10.0.0 (external site) · Archway governance forum — Network Upgrade Proposal: Archway v10.0.0 (external site) · Archway on-chain state via Archway Foundation REST endpoint — Archway proposal 58: v10.0.0 (external site) · Archway on-chain state via Archway Foundation REST endpoint — Archway applied upgrade plan v10.0.0 (external site) · Archway on-chain state via Archway Foundation REST endpoint — Archway node info (application and CometBFT versions) (external site)
-
Kava 18 (v0.28.0) released for a mainnet upgrade at block 14,136,737
Kava Labs released Kava 18 (v0.28.0), a mainnet upgrade scheduled for block 14,136,737, about 15:00 UTC on 25 February 2025. Its stated purpose is an update to the IBC packet-forwarding middleware to fix unreliable USDT transfers over IBC. It also moves node builds to Go 1.22, Cosmos SDK v0.47.15, CometBFT v0.37.13 and RocksDB v9.3.1. The upgrade guide says a software upgrade proposal activates it at that height and tells operators to keep their nodes running until then and switch to v0.28.0.
- Proposal:software upgrade proposal named in the upgrade guide; its on-chain record was not read in this review
- Implementation:code released as v0.28.0
- Release:released 16 February 2025
- Activation:scheduled for block 14,136,737 (about 25 February 2025); not confirmed from an on-chain record here. Kava Labs' API node ran the later v0.28.2 on 27 September 2026
Sources: Kava-Labs/kava on GitHub — Kava 18 Release (v0.28.0) (external site) · Kava-Labs/kava on GitHub — Kava 18 upgrade instructions (migrate/v0_28) (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)
-
Dogecoin Core 1.14.9 released with fixes for bugs inherited from Bitcoin and Namecoin code
Dogecoin Core 1.14.9 is a minor release of the reference node and wallet. Its notes say it fixes bugs that Dogecoin Core inherited from upstream Bitcoin Core and Namecoin Core, and they describe no consensus rule change. It predates this review's one-year news window but is kept because it was still the latest Dogecoin Core release at review; no release was published in 2025 or 2026.
- Implementation:shipped in the tagged v1.14.9 release
- Release:released 2024-12-01; marked Latest on the release page at review
- Activation:no activation needed; no consensus change described; applies to nodes that install it
Sources: Dogecoin Core developers — Dogecoin Core 1.14.9 (external site) · Dogecoin Core developers — Dogecoin Core 1.14.9 release notes (external site) · Dogecoin Core developers — Dogecoin Core releases (external site) · Dogecoin Core developers — Dogecoin Core releases (Atom feed) (external site)
Publication date unknown
These records have no declared publication date. They are listed apart, in alphabetical chain order, rather than given a collection or review date in its place.
-
Base release-awareness sources remain manually curated
The reviewed monitoring set is Base upgrade documentation, Base status notices and base/base GitHub releases. No scheduled intake, webhook or automated news feed is configured by this module.
- Type:Source
- Proposal:Not applicable
- Release:Not applicable
- Activation:Manual only
Sources: Base — Cobalt Overview (external site) · Base contributors — Base v1.4.2 (external site) · Base — Base Status (external site)
-
BIP 54 Consensus Cleanup is marked Complete
BIP 54 specifies proposed consensus cleanups addressing timewarp behavior, worst-case validation cost, Merkle-tree weaknesses, and duplicate-transaction handling. Complete is a proposal status under BIP 3; this record does not claim mainnet activation.
- Stage:Proposal
Sources: Bitcoin BIP contributors — BIP 54: Consensus Cleanup (external site) · Bitcoin BIP contributors — BIP 3: Updated BIP Process (external site)
-
Taproot activated on Bitcoin mainnet
BIP 341 records Taproot deployment on mainnet at block height 709632. This is retained as a historical example of the distinction between a proposal, implementation support, and a network activation.
- Stage:Activation
Source: Bitcoin BIP contributors — BIP 341: Taproot (external site)
-
Glamsterdam scope was scheduled and Sepolia activation set; Mainnet had a December target but no activation timestamp
The meta EIP listed proposals scheduled for inclusion and the roadmap called scope frozen but still changeable while the meta EIP remained in review. Sepolia was scheduled for October 6, 2026. A September EF Protocol planning post used December 2026 as its delivery target for Glamsterdam, but did not supply a Mainnet activation timestamp or activation evidence. Testing, specification prereleases and one execution-client release do not prove Mainnet readiness or activation.
- Type:Upgrade
- Proposal:Scheduled scope meta eip in review
- Release:Spec prerelease and one client release
- Activation:Sepolia scheduled mainnet target not activated
Sources: ethereum.org community — Glamsterdam (external site) · Ethereum Improvement Proposals — EIP-7773: Hardfork Meta - Glamsterdam (external site) · Go Ethereum contributors — Go Ethereum v1.17.6 (external site) · Ethereum contributors — Ethereum consensus specifications v1.7.0-beta.2 (external site) · Ethereum contributors — Ethereum project management records (external site) · Ethereum Foundation Protocol Cluster — EF Protocol: Current and Emerging Priorities (external site)
-
FCMP++ milestone remains implementation work
The FCMP++ hard-fork milestone was open, 71% complete, had no due date, and included draft or in-progress integration items when reviewed. This is implementation-progress evidence, not stable-release or mainnet-activation evidence.
- Stage:Implementation
- Activation:Not activated
Source: The Monero Project contributors — FCMP++ hard-fork milestone (external site)
-
Research Lab discussed FCMP++ and wallet dependencies
The August 19 Research Lab meeting recorded ongoing FCMP++/Carrot work, audit planning and wallet dependencies. Meeting discussion establishes current technical work, not merged code, release readiness or activation.
- Stage:Research
- Activation:Not activated
Source: Monero Research Lab participants — Monero Research Lab meeting, 19 August 2026 (external site)
-
OP Stack interop rollout required specialized node preparation
The official preparation notice describes a testnet dependency set and specialized client topology, but its late-July 2026 OP Mainnet target has passed without evidence of activation, and the Lagoon hardfork documentation reviewed on September 26 lists it as not scheduled. It does not establish OP Mainnet activation.
- Type:Roadmap
- Proposal:Documented rollout
- Release:Time sensitive notice
- Activation:Op mainnet not established
Source: Optimism — Prepare for interop on OP Sepolia and Unichain Sepolia (external site)
-
Lagoon remained in development with no default activation scheduled
Optimism documentation identifies Lagoon as the upcoming interop hardfork, marks it in development, and records no Superchain-wide mainnet or Sepolia activation defaults. The specification is subject to change and this record does not claim activation on OP Mainnet.
- Type:Roadmap
- Proposal:In development
- Release:Specification subject to change
- Activation:Mainnet not scheduled
Sources: Optimism — Lagoon network upgrade (external site) · Optimism — Prepare for interop on OP Sepolia and Unichain Sepolia (external site)
-
Mainnet connection parameters were manually reviewed
Robinhood's current connection page listed mainnet chain ID 4663, ETH gas, the public rate-limited RPC, and the Blockscout explorer. This is dated review evidence, not a publication or launch date.
- Type:Documentation
- Proposal:Not applicable
- Release:Documentation observed
- Activation:Network parameters documented at review
Source: Robinhood — Connecting to Robinhood Chain (external site)
-
Alpenglow migration specification remained in Review
SIMD-0384 described migration from TowerBFT to Alpenglow but carried Review status when checked. Review status is not implementation or Mainnet activation.
- Stage:Proposal
Sources: Solana Foundation and contributors — SIMD-0384: Alpenglow migration (external site) · Solana Foundation and contributors — SIMD-0001: Solana proposal process (external site)
-
NU6.3 activated Ironwood on mainnet
The official upgrade record says NU6.3 activated at mainnet height 3,428,143 on July 28, 2026. It introduced Ironwood and restricted new transfers into the original Orchard pool, with migration consequences for wallets.
- Stage:Activation
Sources: Zcash — Network Upgrade 6.3 (external site) · Zcash ZIP editors — ZIP 258: Deployment of NU6.3 (external site) · Zcash Foundation — Zebra 6.0.0 release (external site)
-
zcashd reached end of life before NU6.3
The deprecation notice says zcashd 6.20.0 halted at height 3,417,100 on July 18, 2026 and does not support NU6.3. Operators were directed to migrate node operation to Zebra.
- Stage:Deprecation