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 13 of 14.
One chain's developments, A to Z
-
Juno votes to unwind community pool stJUNO liquidity
Governance proposal 371 passed and handed the community pool's stJUNO/JUNO liquidity tokens to Juno co-founder Dimi to withdraw the pool on Osmosis, return the JUNO and redeem the stJUNO through Stride. The proposal said most stJUNO stake sat with jailed validators earning nothing and that stJUNO had lost most of its venues.
- Proposal:proposal 371 passed
- Implementation:transfer to the named executor authorised; execution not verified
- Release:no software release needed
- Activation:not verified in this review
-
Boba released op-node v1.16.3 to prevent derivation stalls
Boba published op-node v1.16.3 on 5 December 2025. Its release note says the version carries important fixes for avoiding chain derivation stalls and asks operators to upgrade promptly. The upstream OP Stack notes describe two fixes: blob fetching when a block holds several blobs with the same content, and an overlapping span batch case that could stall the pipeline instead of dropping the batch.
- Implementation:op-node v1.16.3, following upstream op-node v1.16.3
- Release:released on GitHub 2025-12-05; later superseded by v1.16.5
- Activation:no network-wide activation; takes effect on each node when its operator installs it
Sources: Boba Network on GitHub — op-node/v1.16.3 (external site) · Optimism (ethereum-optimism/optimism) — op-node/v1.16.3 (external site) · Boba Network on GitHub — Release notes from boba (Atom feed) (external site)
-
FIP.14 accepted: Web2Json attestations for the Flare Data Connector, with no mainnet source at review
Flare holders accepted FIP.14 with 94.66% of votes cast in favour. It adds Web2Json, an FDC attestation type that fetches JSON from approved web APIs and returns processed values to contracts, and a process in which users propose API sources, the Flare Foundation vets them and the Management Group votes on each source and on fee changes. At review, Flare's docs said Web2Json had no configured source on Flare Mainnet or Songbird, so requests for it revert; it remains available on the Coston and Coston2 testnets.
- Proposal:accepted on 5 December 2025
- Implementation:attestation type implemented; no Flare Mainnet source configured at review
- Release:available on the Coston and Coston2 testnets
- Activation:not usable on Flare Mainnet at review: requests revert
Sources: Flare Governance Proposals — FIP.14: Add Support for FDC Web2 Attestations (external site) · Flare Developer Hub — Web2 FDC Setup (external site) · Flare Developer Hub — Flare Data Connector (FDC) (external site)
-
Zashi 2.4.9 changed wallet privacy and performance controls
Electric Coin Company described Zashi 2.4.9 as a wallet UI and performance release. It removed a Coinbase integration because ECC judged recent changes to create unacceptable privacy risk, added an option to enable Tor before restore synchronization, and simplified exchange-rate retrieval to one provider.
- Stage:Release
Source: Electric Coin Company — Zashi 2.4.9 Is Faster! (external site)
-
Boba asked node operators to upgrade for Ethereum's Fusaka fork
Boba told node operators to move to newer op-node and execution-client versions before Ethereum's Fusaka upgrade, which went live on Ethereum on 3 December 2025, so their nodes would keep following Ethereum after the fork.
- Implementation:op-node v1.16.2 required by the notice
- Release:Released
- Activation:Fusaka active on Ethereum since 2025-12-03
Sources: Boba Network Docs — Preparing for Fusaka breaking changes (external site) · ethereum.org — Fusaka (external site) · Boba Network on GitHub — op-node/v1.16.2-boba (external site)
-
Hardware-attested fast finality for RollApps announced and enabled
Dymension described a path where a RollApp node running inside Google Cloud Confidential Space produces signed attestations that let the Hub finalize RollApp state without waiting out the dispute window. Proposal 34 switched the feature on network-wide on 2025-12-08; each RollApp still opts in.
- Proposal:passed (proposal 34)
- Implementation:shipped in v4.0.0
- Release:released with the Beyond upgrade
- Activation:enabled by parameter; per-RollApp opt-in
Sources: Dymension blog — TEE-Backed Fast Cross-Chain Transfers (external site) · Dymension Hub governance via NodeStake public API — Proposal 34: Enable TEE-Based Fast Finality for RollApps (external site) · Dymension Hub via NodeStake public API — Rollapp module parameters (live Hub query) (external site) · Dymension Hub via NodeStake public API — Registered RollApps (live Hub query) (external site) · Dymension Hub via NodeStake public API — Latest state update of RollApp upordowngame_689603-1 (live Hub query) (external site)
-
LayerZero and Stargate connected to the IOTA layer 1
The IOTA Foundation announced that the Move-based IOTA layer 1 had been integrated with LayerZero's messaging protocol and the Stargate bridge, extending a connection that IOTA EVM had since 2024. LayerZero's documentation lists a separate Move implementation for IOTA layer 1. The same post said a major stablecoin would soon launch on IOTA; USDT0's docs now list an IOTA layer 1 route that connects only to Ethereum.
- Implementation:LayerZero endpoint deployed on IOTA layer 1
- Release:announced 2025-12-03
- Activation:live according to the Foundation; LayerZero documentation lists IOTA layer 1 mainnet endpoints
Sources: IOTA Foundation blog — IOTA Mainnet Integrates LayerZero and Stargate (external site) · LayerZero documentation — IOTA L1 deployment (external site) · USDT0 Docs — Developer Guide (external site)
-
Blast mainnet v1.4.0 kept Blast compatible with Ethereum's Fusaka upgrade
Blast published node software v1.4.0 for mainnet to stay compatible with Ethereum's Fusaka hard fork, after a matching testnet release in October 2025. Because Blast reads its data from Ethereum, its nodes must follow Ethereum's upgrades.
- Implementation:released as v1.4.0
- Release:mainnet release published 2025-12-02
- Activation:tied to Ethereum's Fusaka activation; the release note gives no activation time of its own
Sources: Blast contributors — Release v1.4.0: Fusaka Hardfork (MAINNET) (external site) · Blast contributors — Releases: blast-io/blast (external site)
-
Jovian hard fork (OP Stack Upgrade 17) activated on Mode
Mode was among the chains named for the Jovian upgrade, which lets chain operators set a minimum base fee, adds a block limit on estimated Ethereum data use, and changes how the operator fee is calculated.
- Proposal:Optimism governance upgrade proposal
- Implementation:shipped in OP Stack releases
- Release:released before activation
- Activation:active on Mode since 2025-12-02
Sources: Optimism Docs — Upgrade 17: Jovian hard fork (external site) · Optimism (ethereum-optimism/superchain-registry) — Superchain Registry: mainnet/mode.toml (external site)
-
Jovian hard fork (OP Stack Upgrade 17) activated on Unichain
Unichain was among the chains named for Jovian, which lets chain operators set a minimum base fee, adds a block limit on estimated Ethereum data use to curb spam during fee spikes, and updated the fault-proof virtual machine.
- Proposal:Optimism governance upgrade proposal
- Implementation:shipped in OP Stack releases
- Release:released before activation
- Activation:active on Unichain since 2025-12-02
Sources: Optimism Docs — Upgrade 17: Jovian hard fork (external site) · Optimism (ethereum-optimism/superchain-registry) — Superchain Registry: mainnet/unichain.toml (external site) · Uniswap Labs (Unichain public RPC) — Unichain Mainnet public RPC: latest block header (external site)
-
Jovian hard fork (OP Stack Upgrade 17) activated on Zora Network
Zora was among the chains named for the Jovian upgrade. Jovian let operators set a minimum base fee, added a default in-protocol limit on each block's estimated Ethereum data use, and changed how the operator fee is calculated.
- Proposal:Optimism governance upgrade proposal
- Implementation:shipped in OP Stack releases
- Release:OP Stack node releases
- Activation:active on Zora Network since 2025-12-02
Sources: Optimism Docs — Upgrade 17: Jovian hard fork (external site) · Optimism (ethereum-optimism/superchain-registry) — Superchain Registry: mainnet/zora.toml (external site)
-
Second QTUM subsidy halving
The block subsidy fell from 0.5 to 0.25 QTUM at block 5,369,004 on 30 November 2025, as scheduled in the consensus code. The foundation puts new issuance at roughly 0.25% a year afterwards and expects the next halving around December 2029.
- Implementation:built into consensus rules
- Release:not applicable
- Activation:took effect at block 5,369,004
Sources: qtum.info — qtum.info block 5,369,004 (external site) · Qtum project — Qtum Core block validation (src/validation.cpp) (external site) · Qtum Blog — Qtum Development Updates for 2026 (external site)
-
Lelantus v1 redemption window announced to close at block 1,223,500
Firo announced that unredeemed Lelantus coins minted before Spark's launch had to be moved into Spark before block 1,223,500, after which they would become inaccessible. The reference code rejects Lelantus transactions from that height, and the block was mined on 21 December 2025.
- Implementation:cut-off in reference code (Lelantus rejected from block 1,223,500)
- Release:in released node software
- Activation:cut-off height passed on 2025-12-21
Sources: Firo — Lelantus v1 redemption closing (external site) · Firo developers (firoorg) — Firo reference node: src/firo_params.h (master) (external site) · Firo developers (firoorg) — Firo reference node: src/validation.cpp (master) (external site)
-
dcrd 2.1.0 opens a ticket-holder vote on a new treasury spending cap (DCP-0013)
dcrd 2.1.0 added a consensus vote on DCP-0013, which caps treasury spending in each roughly 24-day window at 4% of the treasury balance, with a floor of about 10,781 DCR, replacing a rule tied to recent treasury income. The release also cut mixing bandwidth and added timeouts for disruptive mixing peers. DCP-0013 is now listed as active: it locked in at block 1,044,352 and took effect at block 1,052,416.
- Proposal:DCP-0013 created 2025-11-20; approved by ticket-holder vote
- Implementation:shipped in dcrd 2.1.0
- Release:stable release published 2025-11-26
- Activation:active from block 1,052,416 (block time 2026-02-08)
Sources: Decred developers — dcrd v2.1.0 release notes (external site) · Decred developers — DCP-0013: New Max Treasury Expenditure Policy (external site) · Decred project (dcrdata) — dcrdata API: block 1,052,416 (external site)
-
Rosen Bridge support for Bitcoin Runes announced live
Ergo Platform announced that Rosen Bridge launched Bitcoin Runes support on mainnet, letting Runes tokens issued on Bitcoin move to Ergo and on to other chains Rosen connects, such as Cardano.
- Implementation:Runes support included in Rosen service releases
- Release:announced live on mainnet 2025-11-26
- Activation:reported by Ergo Platform; not independently tested
Sources: Ergo Platform — Ergo Platform news (external site) · ErgoDocs (Ergo Platform) — Rosen Bridge (external site)
-
Fourier hard fork set for 7 January 2026 to cut opBNB's block interval to 250 ms
BNB Chain released opBNB node v0.5.5 and op-geth v0.5.9, which set the Fourier hard fork's mainnet time to 03:00 UTC on 7 January 2026; the fork halves the block interval from 500 ms to 250 ms. The fork was first released in v0.5.4 in October 2025 with testnet activation set for 6 November 2025. v0.5.5 also made the sequencer and derivation follow BNB Smart Chain's finalized block.
- Implementation:shipped in opbnb v0.5.4 and v0.5.5 and op-geth v0.5.8 and v0.5.9
- Release:mandatory node upgrade before the fork time
- Activation:mainnet 2026-01-07 03:00 UTC per BNB Chain's announcement, which marks the upgrade passed
Sources: BNB Chain (GitHub) — opBNB v0.5.5 release notes (Fourier mainnet time) (external site) · BNB Chain (GitHub) — opBNB v0.5.4 release notes (Fourier hard fork implementation) (external site) · BNB Chain Docs (Announcements) — Fourier Upgrade of opBNB (external site) · BNB Chain (GitHub) — op-geth v0.5.10 release notes (external site) · BNB Chain (GitHub, bnb-chain/opbnb) — feat: replace l1 head with l1 finalized block as sequencer and derivation head (pull request #319) (external site)
-
Foundation reported a handover and a low-cost hibernation mode for Aleph Zero mainnet
The Aleph Zero Foundation said everything needed to keep mainnet running, including the main websites and the aleph-node repository, had been handed over; websites had moved from Digital Ocean to dedicated servers, its AWS infrastructure had been dismantled, and nearly all cost-saving steps were done to keep the chain in as much of a hibernation mode as possible. It said the move to a DAO was far from complete, and that after a board member resigned and negotiations with Cardinal Cryptography failed, it had filed a claim against Cardinal, of which Cardinal had recently been notified, and on which it would not comment until a Swiss court or a settlement resolves it.
- Implementation:handover and cost cutting reported as done
- Release:announced in a Foundation blog post
- Activation:mainnet still produced blocks on 2026-09-29 (one public RPC read)
Sources: Aleph Zero Foundation (via Internet Archive) — Q4 Update (external site) · Aleph Zero Foundation (via Internet Archive) — The New Aleph Zero Roadmap (external site) · Aleph Zero Foundation (via Internet Archive) — Aleph Zero Blog index (Internet Archive snapshot of 2026-07-22) (external site) · Aleph Zero Foundation — Aleph Zero mainnet public RPC: chain_getHeader read (external site)
-
Foundation proposed updating aleph-node to the latest Polkadot SDK and adding RISC-V contracts
The Foundation said several firms and individuals had been identified to update the aleph-node repository to the latest Polkadot SDK and then add the pallet-revive module so the chain can run RISC-V contracts written in ink! 6. It called the first cost and time estimates reasonable, roughly a month of work not counting testnet deployment and stabilisation, and said it was waiting to proceed. The July 2025 roadmap first set out the RISC-V plan after the EVM layer sunset.
- Proposal:proposed by the Foundation; developers identified, awaiting cost and time decisions
- Implementation:not started as of the November 2025 update
- Release:no release
- Activation:not activated; newest node release 15.2.0 (2025-03-21)
Sources: Aleph Zero Foundation (via Internet Archive) — Q4 Update (external site) · Aleph Zero Foundation (via Internet Archive) — The New Aleph Zero Roadmap (external site) · Cardinal Cryptography (GitHub) — aleph-node releases (external site)
-
KinetFlow replaced Zero Gravity Portal as Conflux's legacy bridge and closed old routes
KinetFlow launched as the successor to Zero Gravity Portal, itself the successor to the foundation-run ShuttleFlow. The same day it announced the end of bridge routes to Heco (a network that itself stopped running in January 2025) and OK Chain, manual recovery of stranded CFX for a fee, and the planned closure of Zero Gravity Portal's route between eSpace and Ethereum, for which both notices left the date blank, pointing USDT and USDC holders to cBridge and Meson.
- Implementation:Launched
- Release:announced 2025-11-25
- Activation:project-reported; KinetFlow's own site could not be read
Sources: Conflux Forum — KinetFlow Is Now Live (external site) · Conflux Forum (KinetFlow notice) — Announcement on the Shutdown of Certain Cross-Chain Bridge Services (external site) · Conflux Forum (KinetFlow notice) — 关于部分跨链桥功能关闭的公告 (Chinese notice on the shutdown of certain cross-chain bridge functions) (external site) · Conflux Forum (Conflux Foundation notice) — Announcement: ShuttleFlow is closing its services on 2023.11.08 (external site)
-
Kaspa bridge module bootstrapped by governance
Proposal 32 passed on 2025-11-25 and initialized the Hub's Kaspa bridge, which locks KAS in a validator-held multisig on Kaspa and mints a representation on the Hub. A later proposal (38, February 2026) enrolled a Solana route for that token.
- Proposal:passed (proposal 32)
- Implementation:module shipped in v4.0.0
- Release:released with the Beyond upgrade
- Activation:bootstrapped on mainnet by proposal 32
Sources: Dymension Hub governance via NodeStake public API — Proposal 32: Bootstrap KAS Module (external site) · Dymension forum (Dymension team) — Dymension Kaspa Bridge Design Details (external site) · Dymension blog — Kaspa Meets Dymension (external site) · Dymension Hub governance via NodeStake public API — Proposal 38: Enroll KAS Solana remote router (external site) · Dymension Hub via NodeStake public API — Hyperlane security modules and signer thresholds (live Hub query) (external site)
-
WAX published a Spring-based node release; the chain still used the older finality rule at review
WAX published 'WAX Spring Community Edition release 1.3.0wax01' in its wax-blockchain repository, which describes itself as a WAX port of Antelope Spring with support for Savanna consensus; a further WAX tag, ce-v1.3.1wax01, followed on 15 September 2026 without notes. A release is not an activation: on 29 September 2026 a public WAX API node reported version v5.0.3wax01 and a last irreversible block about 55 seconds behind the head, which fits the pre-Savanna rule.
- Implementation:node software released
- Release:GitHub release published; adoption by guilds not verified
- Activation:not activated at review (inference from a 2026-09-29 API read)
Sources: WAX (GitHub) — WAX Spring Community Edition release 1.3.0wax01 (external site) · WAX (GitHub) — wax-blockchain repository (external site) · WAX (GitHub) — wax-blockchain releases Atom feed (external site) · Greymass (public WAX API node) — WAX Chain API get_info via wax.greymass.com (external site)
-
Matcha (v6) upgrade activated on Celestia Mainnet Beta
The Matcha upgrade activated at height 8,662,012. It bundled six changes: issuance cut to about 2.5% with a higher minimum validator commission, unbonding shortened to about 14 days, a 7-day light-client trusting period, higher block, square and transaction size limits, removal of the TIA-only token filter on IBC and Hyperlane, and an extension to the validator signing interface.
- Proposal:CIP-042 Final
- Implementation:released in celestia-app v6
- Release:activated on Mainnet Beta
- Activation:active from height 8,662,012
Sources: Celestia Docs — Network upgrades (external site) · Celestia Improvement Proposals — CIP-042: Matcha Network Upgrade (external site) · Celestia Improvement Proposals — CIP-038: Increase maximum block, square and transaction size (external site) · Celestia Improvement Proposals — CIP-039: Remove token filter for Hyperlane and IBC (external site) · Celestia Docs — Staking, governance, & supply (external site)
-
dymd v4.0.1 released with a fix for the eth_gasPrice query
Dymension contributors published dymd v4.0.1 on 2025-11-24, a week after v4.0.0. The release notes list one change: a fix for the eth_gasPrice query in the Hub's Ethereum-style JSON-RPC interface, which they describe as malformed (pull request 2114). The notes say the release does not break consensus and can be installed without coordination.
- Implementation:fix merged as pull request 2114
- Release:released 2025-11-24 as v4.0.1
- Activation:no network activation; each operator installs it, and the notes say no coordination is needed
Sources: Dymension contributors — Dymension v4.0.1 release notes (external site) · Dymension contributors — Dymension Hub releases Atom feed (external site)
-
USE dollar stablecoin launch event announced
Ergo Platform announced a community liquidity event starting 25 November 2025 for USE, a dollar stablecoin built on the Dexy design. Contributors' ERG was to seed a USE/ERG pool whose LP tokens are locked for two years, and parameters start under a 3-of-5 multisig committee.
- Proposal:design documented in Ergo's docs
- Implementation:contracts deployed per later docs notes (not independently checked)
- Release:liquidity event scheduled 2025-11-25 to 2025-12-01
- Activation:later docs record minting activity; launch date not confirmed
Sources: Ergo Platform — Ecosystem Spotlight: USE, a Universal Stablecoin for Ergo (external site) · ErgoDocs (Ergo Platform) — USE (USD stablecoin) (external site) · ErgoDocs (Ergo Platform) — Dexy: A Seigniorage-Based Stablecoin (external site)
-
Monad public mainnet launched
The Monad Foundation announced that Monad Mainnet was live on 24 November 2025, and Monad's documentation records the same public launch date for chain ID 143. The Foundation's tokenomics post two weeks earlier set an initial supply of 100 billion MON, a fixed inflationary reward for each block and burning of the base fee.
- Implementation:public mainnet running Category Labs' monad-bft and monad clients
- Release:announced live by the Monad Foundation
- Activation:live since 24 November 2025
Sources: Monad Foundation blog — Get Started on Monad Mainnet (external site) · Monad Documentation (Monad Foundation) — Introduction (external site) · Monad Foundation blog — MON Tokenomics Overview (external site) · Monad Documentation (Monad Foundation) — Current Facts for AI Agents (external site)
-
EGLD moved from a supply cap to tail inflation
Release v1.11.1, Staking V5 and New Emissions Model Phase 1, implemented the economic change approved by governance in October 2025. From epoch 1951 (about 2 December 2025) issuance is calculated from the current total supply, starting at 8.757% a year, falling by 0.25 percentage points each economics year, with a 2% floor, and is split among staking rewards (50%), an ecosystem growth fund (20%), a growth dividend (20%) and protocol sustainability (10%).
- Proposal:approved by on-chain vote in October 2025 according to MultiversX's glossary
- Implementation:implemented in node v1.11.1
- Release:v1.11.1 released 2025-11-24
- Activation:active from epoch 1951 per the mainnet economics file
Sources: MultiversX — Release: Staking V5 and New Emissions Model - Phase 1 - v1.11.1 (external site) · multiversx/mx-chain-mainnet-config — Mainnet economics.toml (v2.1.5.0) (external site) · MultiversX Docs — Terminology (external site)
-
Governance approved and applied the Beyond upgrade (dymd v4.0.0)
Proposal 31 passed on 2025-11-22 and the upgrade plan it scheduled is recorded on chain as applied at height 10,192,266. The release adds Hyperlane routes, a Kaspa bridge module, hardware-attested fast finality for RollApps, IBC rate limits, non-DYM base assets for pools and several launchpad and incentive changes.
- Proposal:passed (proposal 31)
- Implementation:released as v4.0.0; later patches v4.0.1 and v4.0.2
- Release:released 2025-11-17
- Activation:applied on mainnet at height 10,192,266
Sources: Dymension Hub governance via NodeStake public API — Proposal 31: Beyond software upgrade (external site) · Dymension Hub via NodeStake public API — Applied upgrade plan v5 (live Hub query) (external site) · Dymension forum — [PROP# 31] [APPROVED] The RENEWED Beyond Upgrade (external site) · Dymension contributors — Dymension v4.0.0 release notes (external site) · Dymension Hub via NodeStake public API — Node and application version (live Hub query) (external site) · Dymension Hub via NodeStake public API — Latest Hub block (live Hub query) (external site)
-
Final company release records that its Kadena mainnet stopped
chainweb-node 2.32.0, the last company release, states that the company-run Kadena mainnet stopped producing blocks at 23:26:15 UTC on 15 November 2025. It publishes the final cut, removes the bootstrap nodes and the node expiry date, and precedes archiving of the repository.
- Implementation:final release
- Release:released 2025-11-22; repository archived 2025-11-24
- Activation:block production stopped 2025-11-15
Sources: Kadena LLC — chainweb-node 2.32.0 (external site) · Kadena LLC — chainweb-node repository (archived) (external site) · Kadena LLC — chainweb-node changelog (Kadena LLC) (external site)
-
Granite activated on Avalanche Mainnet
Avalanche's incident review records Granite v1.14.0 as active on Mainnet and as the permanent resolution for a disclosed stateful-precompile delegatecall issue; the review says it was not exploited on Mainnet or a public Avalanche L1.
- Implementation:Released
- Release:Stable release
- Activation:Mainnet active
Source: Avalanche Builder Hub — Delegatecall Incident Overview (external site)
-
Validators told to publish a daily reference rate for aligned stablecoins
Hyperliquid's node guide added instructions for active validators to run a rate publisher and post a daily rate vote at 22:00 UTC, using a reference publisher from a Native Markets repository. The chain takes the stake-weighted median of these votes as the rate used to work out how much reserve yield aligned stablecoin issuers share with the protocol.
- Implementation:reference publisher documented in the node guide
- Release:Documented
- Activation:mainnet activation date not confirmed
Sources: hyperliquid-dex (GitHub) — node commit 2dcb347: publish risk free rate (external site) · Hyperliquid Docs — Aligned quote assets (external site)
-
Casper 2.1 released: 8-second minimum block time and burning of all transaction fees
Casper node release 2.1.0, a configuration update, halved the minimum block time to 8 seconds and switched transaction fees from payment to the block proposer to burning, which validators had approved in vote CVV005. Release 2.1.1 followed on 2025-12-01 with a fix to delegation minimums and settings that halve block capacity while doubling time windows. The Casper Association says Casper 2.1 is live on mainnet.
- Proposal:fee burning approved by validator vote CVV005 (proposal posted 2025-09-17)
- Implementation:configured in casper-node v2.1.0, with binary fixes in v2.1.1
- Release:released 2025-11-18 (v2.1.0) and 2025-12-01 (v2.1.1)
- Activation:live on mainnet per Casper Association posts; activation era not confirmed; the 2.2.2 mainnet chainspec carries both settings
Sources: Casper Network (GitHub) — casper-node v2.1.0 release notes (external site) · Casper Network (GitHub) — casper-node v2.1.1 release notes (external site) · Casper Association — Casper 2.1: Faster and More Efficient for the Real World (external site) · Casper Network forum — [CVV005] Proposal: Enable Burning Mechanism (external site) · Casper Association — Casper End-of-Year X Space Recap: 2025 in Review, New DEX Announced Live, and the Path Forward (external site) · Casper Network (casper-node repository, GitHub) — Casper mainnet chainspec, protocol version 2.2.2 (external site)
-
Polygon zkEVM switched from full execution proofs to pessimistic proofs
Polygon announced it would migrate Polygon zkEVM mainnet from full execution proofs to pessimistic proofs on 3 December 2025, with the bridge paused for about six hours. After the change, Ethereum checked only the chain's bridge accounting, not its state. L2BEAT records the change between 3 and 5 December 2025 and now lists the chain as neither a rollup nor a validium.
- Proposal:announced by Polygon; no governance vote described
- Implementation:contract changes recorded by L2BEAT on 3 to 5 December 2025
- Release:pessimistic proof system from Polygon's shared bridge stack
- Activation:active from December 2025 until the July 2026 shutdown
Sources: Polygon Community Forum — Announcement - zkEVM Migration Update (external site) · L2BEAT — Polygon zkEVM (external site) · Polygon Developer Docs — Pessimistic Proof: Architecture (external site)
-
Sonic proposed veSONIC staking and boosts for node holders
Sonic's first numbered proposal would let node holders stake any amount of veSONIC, unstake at any time, and use a boost that raises a node's effective production weight, shifting its share of a fixed daily reward pool.
- Proposal:proposal published
- Implementation:not independently observed
- Release:not stated
- Activation:not verified as active
Source: Sonic SVM — Proposal #01: Activation of veSONIC Staking and Boost Mechanism (external site)
-
Required Fraxtal node upgrade before Ethereum's Fusaka hard fork
Frax published a required mainnet node release updating its op-geth and op-node forks so Fraxtal nodes would keep following Ethereum through the Fusaka hard fork on 3 December 2025. The release warned that nodes left un-upgraded would see a chain split.
- Implementation:Released
- Release:mainnet-20251117 node release
- Activation:needed before Ethereum's Fusaka activation on 2025-12-03
Source: Frax Finance on GitHub — fraxtal-node releases (external site)
-
Hyperlane Warp routes connect LUNC and USTC to BNB Smart Chain, Ethereum and Solana
Governance backed integrating Hyperlane in proposal 12200 (voting ended 17 November 2025) and funded the Solana deployment in proposal 12222 (July 2026). The Hyperlane Registry lists Warp routes that lock native LUNC and USTC in Terra Classic contracts and mint synthetic tokens on BNB Smart Chain, Ethereum and Solana; the Solana deployment was paid for from the community pool. The docs said ownership transfers were still being completed; proposal 12229, in voting until 6 October 2026, would have governance claim ownership of 12 Hyperlane contracts.
- Proposal:integration passed as proposal 12200; Solana funding passed as proposal 12222; ownership claim (proposal 12229) in voting
- Implementation:route contracts deployed and listed in the Hyperlane Registry
- Release:bridge interface live at terraclassic-bridge.xyz
- Activation:routes listed in the Hyperlane Registry and described as current in the Terra Classic docs; governance ownership pending at review
Sources: Terra Classic on-chain state via PublicNode REST endpoint — Terra Classic proposal 12200: Hyperlane Integration on Terra Classic (external site) · Terra Classic on-chain state via PublicNode REST endpoint — Terra Classic proposal 12222: Hyperlane Warp Routes, Solana mainnet deployment funding (external site) · Hyperlane Registry (hyperlane-xyz/hyperlane-registry) — Hyperlane Registry: LUNC Warp route configuration (external site) · Terra Classic community documentation (terra-classic-io/website repository) — Terra Classic docs: Hyperlane contracts and Warp routes (external site) · Terra Classic on-chain state via PublicNode REST endpoint — Terra Classic proposal 12229: Claim Hyperlane infrastructure ownership for governance (external site) · Terra Classic community (Hyperlane Warp route interface) — Terra Classic Bridge (external site)
-
Governance cut Initia's active validator cap from 50 to 20
Proposal 60 passed on 2025-11-14 and changed the multi-staking parameter for the maximum number of active validators from 50 to 20. The Initia Foundation's forum post argued that rewards spread over 50 validators did not cover secure operation. The live parameter read on 2026-09-27 was 20, with only 10 validators in the consensus set.
- Proposal:passed (proposal 60)
- Implementation:parameter change executed on chain
- Release:no software release needed
- Activation:active; cap of 20 observed 2026-09-27
Sources: Initia L1 governance (on-chain record) — Proposal 60: Active Validator Set Reduction (external site) · Initia Forum (Initia Foundation) — Active Validator Set Reduction Proposal (external site) · Initia Labs public REST endpoint — Live multi-staking parameters (external site) · Initia Labs public RPC endpoint — Live consensus validator set (external site)
-
v4 upgrade added BTC-BABY co-staking and cut BABY inflation to 5.5%
After a signalling vote passed on 6 October 2025, the v4 software upgrade (governance proposal 18) went live at height 1,893,601 on 13 November 2025. It added co-staking rewards for users who stake both BTC and BABY, reduced BABY inflation from 8% to 5.5% a year, and let bitcoin stakers extend a stake's timelock without unbonding.
- Proposal:passed (proposals 15 and 18)
- Implementation:released as v4.0.0
- Release:Released
- Activation:active since height 1,893,601
Sources: Babylon on-chain governance (via Polkachu REST endpoint) — Governance proposal 18: v4 Software Upgrade (external site) · Babylon on-chain governance (via Polkachu REST endpoint) — Governance proposal 15: Signalling Proposal: Inflation reduction and the introduction of co-staking (external site) · Polkachu public REST endpoint for bbn-1 — Applied upgrade plan v4 (on-chain query) (external site) · Babylon Labs — Babylon node CHANGELOG (external site) · Babylon Labs docs — BABY tokenomics (external site)
-
USDT0 launched on Conflux eSpace
The Conflux team announced USDT0 on eSpace, a dollar stablecoin minted against USDT locked on Ethereum and moved with LayerZero messaging, and began a gradual migration from the older bridged cUSDT. USDT0's own deployment list includes the Conflux eSpace contracts.
- Implementation:token and OFT contracts listed for eSpace in USDT0's deployment table
- Release:launch announced 2025-11-12
- Activation:listed in USDT0's deployment table at review
Sources: Conflux Forum (Conflux team) — Tether USDT0 Officially Launches on Conflux (external site) · USDT0 — USDT0 deployments (external site) · USDT0 — The USDT0 Network (external site) · Tether — Supported protocols (external site)
-
Hermes hard fork brought two-block finality votes to Core mainnet
Core scheduled the Hermes hard fork for mainnet at 08:00 UTC on 25 November 2025 with client v1.0.22. It adds BLS finality votes adapted from BNB Smart Chain's BEP-126, under which a block is final after about two blocks (around 6 seconds) once two-thirds of validators vote, plus validator maintenance mode, BLS12-381 operations, historical block-hash access and code on externally owned accounts.
- Proposal:BNB Smart Chain proposals adopted by Core (BEP-126 and others)
- Implementation:shipped in client v1.0.22
- Release:mandatory mainnet release
- Activation:scheduled 2025-11-25 08:00 UTC; Core's December 2025 post says it was delivered
Sources: Core DAO — Hermes hardfork on mainnet (external site) · Core DAO (GitHub) — core-chain v1.0.22 (Hermes mainnet) (external site) · Core DAO (GitHub) — Chain configuration source (params/config.go) (external site) · Core DAO — Hermes upgrade guidelines for validators and full node operators (external site) · Core DAO — The Core revenue roadmap (external site)
-
Spring node software moved from a chain-bound Business Source License to MIT
A commit to the Spring repository's main branch replaced its Business Source License, which granted free use only in service of this chain, with the MIT License. The new license file names the Vaulta Foundation and the EOS Network Foundation as copyright holders and credits the EOSIO code the software is based on.
- Implementation:license file changed on the main branch
- Release:no tagged Spring release includes it
- Activation:not a protocol change
Sources: AntelopeIO (GitHub) — Spring commit e6a99f6: Update LICENSE (Move to MIT License) (external site) · AntelopeIO (GitHub) — Spring v1.0.0 release notes (external site) · AntelopeIO (GitHub) — Spring v1.2.2 release notes (external site)
-
Native EVM went live on Injective mainnet with the v1.17.0 upgrade
Injective's embedded EVM (chain ID 1776) launched on mainnet on 11 November 2025. The v1.17.0 upgrade, approved as IIP 583, was scheduled for block 141,150,000 at 14:00 UTC that day. EVM contracts run in the same blocks as CosmWasm and the native modules and share token balances through the MultiVM Token Standard.
- Proposal:approved as IIP 583
- Implementation:shipped in injective-core v1.17.0
- Release:Released
- Activation:active on mainnet since 11 November 2025
Sources: Injective — Welcome to the Injective Era: Native EVM Mainnet Launch (external site) · Injective Docs — Upgrade to v1.17.0 (external site) · InjectiveFoundation/injective-core on GitHub — injective-core CHANGELOG (tag v1.20.3-safeharbor.2) (external site)
-
Clarity 4 activated on Stacks mainnet
SIP-033 and SIP-034 activated at Bitcoin block 923,222, bringing Clarity 4 with functions for checking another contract's code hash, restricting a contract's own asset movements, reading block time and verifying secp256r1 signatures, plus finer-grained tenure budget extensions.
- Proposal:SIP-033 and SIP-034 approved
- Implementation:Released
- Release:Activated
- Activation:active from Bitcoin block 923,222
Sources: Stacks Labs — Clarity 4 is Now LIVE (external site) · Stacks Documentation — Latest Updates (external site)
-
Dash Core 23.0.0 released, rebuilding compact filters for light wallets
Dash Core 23.0.0, the first 23.x release, migrated masternode data to a new internal format, rebuilt the compact block filter index to include Dash special transactions such as masternode registrations and asset locks, randomized wallet change amounts and raised the minimum peer protocol version. It was required for masternodes and evonodes but was not a hard fork.
- Implementation:shipped in Dash Core 23.0.0
- Release:stable release published 2025-11-10
- Activation:no consensus change; took effect as nodes upgraded
Sources: Dash Core developers (dashpay) — Dash Core 23.0.0 release announcement (external site) · Dash Core developers (dashpay) — Dash Core v23.0.0 release notes (external site)
-
Fraxtal testnet replaced by a new testnet on Ethereum's Hoodi network
Frax replaced its Fraxtal testnet with a new one that settles to Ethereum's Hoodi test network and runs current node versions. Frax's network page now lists the Fraxtal testnet as chain ID 2523 with its own RPC endpoint and explorer.
- Implementation:Released
- Release:testnet-20251010 node release
- Activation:new testnet live per Frax's network page
Sources: Frax Finance on GitHub — fraxtal-node releases (external site) · Frax Docs — Fraxtal Network Information (external site)
-
UNIfication proposal to route Unichain sequencer fees to the UNI burn (executed 27 December 2025)
Uniswap Labs and the Uniswap Foundation posted the UNIfication proposal, which turns on Uniswap protocol fees and directs all Unichain sequencer fees, after Ethereum data costs and the 15% share paid to Optimism, into a collector contract on Unichain whose assets can be withdrawn only by burning UNI. Tally records the proposal as executed; its execution block dates to 27 December 2025.
- Proposal:passed onchain vote
- Implementation:executed on Ethereum
- Release:fee collector contracts deployed on Unichain
- Activation:executed 2025-12-27
Sources: Uniswap Labs Blog — UNIfication (external site) · Uniswap governance forum — UNIfication Proposal (external site) · Tally — UNIfication (Uniswap proposal 93) (external site) · Uniswap Labs (developer docs) — Uniswap Protocol Fees (external site) · Uniswap Labs (developer docs) — Protocol Fee Deployments (external site)
-
Fusaka was scheduled with client releases and later confirmed active on Mainnet
The November announcement scheduled activation for December 3, 2025 and listed client releases. A later ethereum.org upgrade page directly reports that Fusaka went live that day. Scheduling, implementation releases and observed activation remain separate evidence.
- Type:Upgrade
- Proposal:Included
- Release:Mainnet client releases listed
- Activation:Activated mainnet
Sources: Ethereum Foundation — Fusaka Mainnet Announcement (external site) · ethereum.org community — Fulu-Osaka (Fusaka) (external site) · Ethereum Foundation — Protocol Priorities Update for 2026 (external site) · Ethereum contributors — Ethereum consensus specifications (external site) · Ethereum Foundation STEEL team — Ethereum execution-layer specifications (external site)
-
Community Edition node released, forking Kadena on 8 November 2025
A community group published chainweb-node 3.0 Community Edition. It forked from the company-run chain at 04:00 UTC on 8 November 2025, moved the platform-share and namespace keysets to a community keyset, and added community bootstrap nodes. Release 3.0.1 made nodes that had followed the other chain rewind to the fork point.
- Proposal:community decision announced
- Implementation:implemented in releases 3.0 and 3.0.1
- Release:released 2025-11-06
- Activation:fork at 04:00 UTC on 2025-11-08; blocks still being produced on 2026-09-27
Sources: Kadena Community Edition — chainweb-node Community Edition 3.0 (external site) · Kadena Community Edition — chainweb-node Community Edition changelog (external site) · Kadena Community Edition — KDA Community Edition posts (Medium feed) (external site) · Kadena Community Edition — Community node current cut (mainnet01) (external site)
-
Mysticeti v2 and the Transaction Driver became Sui's default transaction path
Sui announced Mysticeti v2, which folds transaction validation into consensus, together with a Transaction Driver that submits each transaction to one validator chosen from latency history instead of to all of them; validators now sign transaction validity in batches as part of signing their consensus blocks. Node release mainnet-v1.60.1 (protocol version 101), published on 10 November 2025, made both the default. Sui reported lower latency from its own full nodes afterwards.
- Implementation:implemented in node v1.60
- Release:mainnet-v1.60.1 released 2025-11-10
- Activation:default transaction path from v1.60 according to the release notes; rollout across individual validators not independently observed
Sources: Sui Foundation blog — Mysticeti v2 (external site) · MystenLabs/sui repository — mainnet-v1.60.1 (external site)
-
Governance proposal to double Dual Staking CORE-to-BTC ratios
Core published a governance proposal to double the CORE-to-BTC ratios that set Dual Staking reward tiers, from 34,000, 12,750 and 4,250 CORE per BTC to 68,000, 25,500 and 8,500, with a three-day vote from 5 to 8 November 2025 and implementation right after if approved.
- Proposal:governance proposal with a vote from 2025-11-05 to 2025-11-08
- Implementation:Core's docs show thresholds matching the proposed ratios; vote result not seen
- Release:parameter change; no client release involved
- Activation:not confirmed from a primary result notice
Sources: Core DAO — Governance proposal to adjust the Dual Staking CORE to BTC ratios (external site) · Core DAO Docs — Dual Staking overview (external site)