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 10 of 14.
One chain's developments, A to Z
-
Noble v11.4.0 ends USDN Vaults Season Two
Release v11.4.0 unlocked every staked USDN vault position through its upgrade handler and updated the USDN module so that vault yield handling is removed and locking is disabled. It also recovered expired IBC clients for two connected chains.
- Implementation:released as v11.4.0 (v11.3.0 was never applied)
- Release:released 2026-04-10
- Activation:applied on mainnet; height not verified
Sources: noble-assets/noble maintainers — Noble v11.4.0 release notes (external site) · noble-assets/dollar maintainers — Noble Dollar module v2.3.0 release notes (external site) · Noble public REST endpoint — Noble node software version (on-chain query) (external site) · Noble — NOBLE Token Airdrop: How to Start Your Claims Process (external site) · noble-assets/noble maintainers — Noble v11.3.0 release notes (external site)
-
Celo published an incident report on a chain ID validation bug
A bug introduced during the Layer 2 migration let access-list transactions with the wrong chain ID be accepted on Celo mainnet. It was reported on 15 December 2025 and blocked at the sequencer the same day, and the code fix shipped with Jovian. One such transaction was included; the report says no funds were at risk or taken.
- Implementation:sequencer filter deployed; fix included in Jovian
- Release:Resolved
- Activation:mitigated since 15 December 2025
Source: Celo Forum (core engineering team) — Incident Report: Chain ID Validation Bypass (external site)
-
NEP-639 documented dynamic resharding
NEP-639 described dynamic resharding. The individual proposal said Draft while the repository index showed Final; this record preserves the conflict and uses the proposal's narrower status. nearcore 2.13.0 states the feature was stabilized and mainnet protocol 86 was later observed, but this review did not independently observe a resharding event.
- Proposal:Draft at review with index conflict
- Implementation:stated-stabilized-in-nearcore-2.13.0
- Release:Released code
- Activation:protocol-86-observed-mainnet-2026-09-25; resharding event not independently observed
Sources: NEAR NEPs — NEP-639: Dynamic Resharding (external site) · NEAR — NEAR Enhancement Proposals (external site) · NEAR nearcore — nearcore 2.13.0 (external site)
-
Catchain 2.0 activated, bringing sub-second blocks to TON mainnet
Validators voted to fully activate Catchain 2.0, TON's new consensus protocol. TON's developer guide says the block interval fell from about 2.5 seconds to about 400 milliseconds and the lag to finality from about 10 seconds to about 1 second.
- Proposal:validator vote needing 75% of stake across two rounds, per the channel
- Implementation:implemented in TON node software
- Release:phased mainnet rollout: node upgrades from 2026-03-31, a basechain activation vote on 2026-04-02 and a final full-activation vote from 2026-04-08, per the channel
- Activation:active on mainnet by 2026-04-09
Sources: TON Docs — How to adopt sub-second finality (external site) · Gram of TON (Telegram channel) — Sub-Second Mainnet Activation Starts Now (external site) · Gram of TON (Telegram channel) — Catchain 2.0 activation is underway (external site) · Gram of TON (Telegram channel) — The TON blockchain just got upgraded (external site) · Gram of TON (Telegram channel) — Gram of TON (official channel, public web view) (external site)
-
Beam Warp sidechain testing continued on a developer network
Beam reported testing the Beam Warp sidechain on a developer network with three-second blocks, a working two-way bridge to a Beam development main chain, and a staking contract supporting up to 96 active validators. Minimum stake and validator count for the next network were still under discussion.
- Implementation:running on developer networks
- Release:no public release
- Activation:not on mainnet; no timeline published
Sources: Beam blog — Beam Warp Development Update #2: Testing and Benchmarking (external site) · BeamMW — core/block_crypt.cpp (consensus rules, fork heights, fees) (external site)
-
Mantle scheduled the Arsia mainnet upgrade: new fee model, OP Stack alignment and Ethereum-only data
Mantle's v1.5.4 release scheduled the Arsia upgrade for Mantle Mainnet on 22 April 2026 at 07:00 UTC. Arsia replaced the fee model with an execution fee, an Ethereum data fee and a new operator fee, made the base fee dynamic, and activated the equivalent of eight upstream Optimism upgrades at once, bringing in features such as span batches and Brotli compression. L2BEAT records that Mantle's transaction data has gone only to Ethereum since this period, with the EigenDA path removed.
- Implementation:released as v1.5.4 with a CertiK audit report
- Release:v1.5.4 Mainnet Arsia
- Activation:scheduled for 2026-04-22 07:00 UTC; Mantle's September 2026 release describes the chain as running on Arsia rules
Sources: Mantle (GitHub) — v1.5.4 Mainnet Arsia (external site) · Mantle Network Documentation — What's New in Mantle v2 Arsia (external site) · Mantle Network Documentation — Migration of Data Availability to Ethereum Blobs (external site) · L2BEAT — Mantle (external site) · Mantle (GitHub) — 1.6.3 Elysium (external site)
-
Giugliano hardfork shortened confirmations and published fee parameters on chain
Giugliano activated at mainnet block 85,268,500. Producers now announce blocks earlier, which Polygon said brought test-network confirmations about two seconds below the mainnet average of 6 to 7 seconds, and each block header now carries the gas target and base-fee change rate, readable through a new RPC method.
- Implementation:shipped in client releases
- Release:mainnet activation announced
- Activation:announced as live at block 85,268,500
-
Staking rewards again paid directly to SAGA stakers
Saga said rewards would flow directly to stakers on the security chain instead of being routed through the community pool toward SagaEVM, because rewards could not be distributed or claimed on SagaEVM while it was being repaired. Inflation stayed at 3%. On 2026-09-27 the chain's community tax was zero.
- Implementation:community tax of zero observed on chain
- Release:parameter change; no governance proposal was submitted after proposal 28 (March 2026), so how the change was made was not identified
- Activation:active on 2026-09-27
Sources: Saga — Staking Rewards Return to Saga Mainnet (feed item) (external site) · Polkachu public REST endpoint — ssc-1 distribution parameters (external site) · Polkachu public REST endpoint — ssc-1 mint parameters (external site) · Polkachu public REST endpoint — ssc-1 recent governance proposals (external site)
-
dcrd 2.1.4 patches several denial-of-service weaknesses
dcrd 2.1.4 fixed several ways a malicious peer could disrupt nodes, including stricter checks on network messages and mixing messages, and made the RPC server reject cross-origin requests arriving through reverse proxies. The release notes list no consensus change; 2.1.5 followed three days later to fix a possible node crash that affected only 2.1.4.
- Implementation:shipped in dcrd 2.1.4
- Release:stable release published 2026-04-07
- Activation:no consensus change; took effect as nodes upgraded
Sources: Decred developers — dcrd v2.1.4 release notes (external site) · Decred developers — dcrd v2.1.5 release notes (external site) · Decred developers — dcrd releases (external site)
-
Taiko released the Shasta redesign of its protocol contracts
Protocol release v3.0.0 introduced the Shasta fork, replacing Pacaya with a separate Inbox, proposal-based derivation, and finalization that advances in order and writes a checkpoint to the Signal Service. Taiko had said the redesign would cut proposing gas on Ethereum from up to about 1 million to about 45,000 per proposal, and a May 2026 Taiko post described Shasta as running.
- Implementation:protocol contracts released
- Release:taiko-alethia-protocol v3.0.0
- Activation:live by 2026-05-13 per Taiko; activation date not found
Sources: Taiko contributors (GitHub) — taiko-alethia-protocol v3.0.0 (external site) · Taiko Documentation — Shasta Fork (external site) · Taiko Labs — Taiko's first third of 2026 (external site) · Taiko Labs — Closing in on Stage 1: The Shasta Upgrade Is Almost Here! (external site)
-
VeChain 2026 roadmap plans JSON-RPC equivalence, committee-based finality and VeWorld bridges
VeChain's 2026 roadmap says Galactica (July 2025) and Hayabusa (December 2025) are complete and lays out further Interstellar work: step-by-step alignment with Ethereum's virtual machine, JSON-RPC equivalence, committee-based validation to strengthen finality, more validator delegation controls and verification infrastructure for tokenized real-world assets. It also plans bridges from VeWorld to Ethereum and other EVM chains and built-in swaps.
- Proposal:announced roadmap
- Implementation:virtual-machine alignment shipped in September 2026; other items not observed
- Release:no release for JSON-RPC equivalence, committee-based finality or bridges found
- Activation:not active as of this review
Sources: VeChain — VeChain Roadmap 2026: Agentic Foundations for Tomorrow & Beyond (external site) · vechain/thor maintainers — Thor v2.5.0 release notes (Interstellar hardfork) (external site) · VeChain VIPs repository — VIP-255: Interstellar EVM Upgrade Specification (external site)
-
Block reward reaches the 3 ERG floor
Ergo's miner reward fell from 6 to 3 ERG per block at block 1,756,800 on 4 April 2026, the last scheduled quarterly step. Under the EIP-27 soft fork, the reward is designed to stay at 3 ERG per block until the re-emission contract runs out, which the docs estimate at roughly 2045.
- Proposal:part of the original schedule as amended by EIP-27
- Implementation:built into consensus rules
- Release:no release needed
- Activation:active from block 1,756,800 (4 April 2026) per explorer data
Sources: Ergo Platform (explorer API) — Ergo Explorer API: blocks 1,756,799 to 1,756,801 (external site) · Ergo Platform — Ergo Platform news (external site) · ErgoDocs (Ergo Platform) — Ergo Emission Schedule (external site) · ErgoDocs (Ergo Platform) — EIP27: Emission Retargeting Soft-Fork (external site)
-
Arweave node 2.9.5.1 patches input-validation crashes
Arweave node 2.9.5.1 fixes several input-validation steps that could crash on invalid values and in some cases halt a node, adding graceful validation and defensive deserialization of local binaries. The notes recommend upgrading as soon as possible, state that no funds are at risk, and credit four outside researchers and security teams.
- Implementation:shipped in N.2.9.5.1
- Release:recommended patch release
- Activation:no activation height; takes effect when each node upgrades
Sources: ArweaveTeam (GitHub) — Arweave 2.9.5.1 patch release notes (external site) · ArweaveTeam (GitHub) — Arweave 2.9.7-alpha1 release notes (external site)
-
BSV Association announced Chronicle's mainnet activation height and expected date
The BSV Association announced that Chronicle, SV Node 1.2, would activate on mainnet at block 943,816, expected on 7 April 2026, and that all node operators and exchanges supporting BSV had to upgrade first or risk falling out of consensus.
- Implementation:shipped in SV Node 1.2.0 and 1.2.1
- Release:upgrade required before activation
- Activation:announced for block 943,816 on 7 April 2026; passed by the chain at review, not separately confirmed
Sources: BSV Association via Cision Newswire — BSV Association Announces Chronicle: A Mandatory Network Upgrade (external site) · BSV Association (GitHub) — Bitcoin SV Version 1.2.2 release notes (external site) · Allnodes (PublicNode), powered by the BSV Association — PublicNode BSV mainnet JSON-RPC (read 2026-09-29) (external site)
-
Fusaka hard fork scheduled for Gnosis Chain on 14 April 2026
The Gnosis Chain validator newsletter announced activation of the Fusaka upgrade at epoch 1714688 on 14 April 2026, headlined by PeerDAS, which lets nodes sample blob data instead of downloading all of it. The fork followed Ethereum's December 2025 activation and was delayed by the Balancer emergency fork.
- Implementation:client releases listed in the announcement
- Release:Released
- Activation:activated 2026-04-14; the mainnet config and Nethermind's chain configuration carry the same fork point, and the chain has kept finalizing since
Sources: Gnosis Chain Validator Newsletter (GC Comms Team) — Gnosis Chain - Fusaka Hard Fork Announcement (external site) · Gnosis Chain (GitHub) — gnosischain/configs mainnet config.yaml (external site) · Nethermind (GitHub) — Gnosis chain specification (gnosis.json) (external site) · Gnosis Chain (beaconchain.gnosischain.com) — Gnosis beacon chain explorer: latest finalized epoch (external site)
-
April 2026 release: staked HNT positions can move between wallets
The April 2026 Helium Release Proposal added a transfer instruction to the staking programs so a holder can move a locked veHNT position, represented by a frozen NFT, to another wallet without unlocking it. The position's amount, lock and rewards stay unchanged. The release note records it as released on 2 April 2026.
- Proposal:Helium Release Proposal 2026-04 approved by veHNT vote
- Implementation:transfer endpoint added to the staking programs
- Release:released 2026-04-02 per the release note
- Activation:live from release per the release note; not tested in this review
Sources: Helium Core Developers (helium-release-proposals repository) — Helium Release Proposal April 2026 (external site) · Helium Core Developers (GitHub) — Helium Release Proposals repository (external site)
-
Metis governance marked approved a proposal for Nansen to run a sequencer in the Metis pool
A forum proposal from Nansen, now titled as approved, asks to lock 20,000 METIS and launch a sequencer in Metis's decentralized sequencer pool in Q2 2026. Metis's sequencer registry added Nansen as a Sepolia testnet sequencer on 12 March 2026, but this review did not find Nansen in the mainnet list.
- Proposal:marked approved on the Metis governance forum
- Implementation:testnet sequencer entry added 12 March 2026
- Release:no software release involved
- Activation:launch targeted for Q2 2026; not found in the mainnet registry on 27 September 2026
Sources: Metis CEG forum — Sequencer Proposal: Nansen (Deployment) (external site) · Metis (GitHub) — metis-sequencer-resources commit history (external site) · Metis (GitHub) — Mainnet sequencer list (sequencers/1088/all.json) (external site)
-
Vetiver network upgrade released and activated
Rootstock released node version 9.0.0 for the Vetiver network upgrade, activating at mainnet block 8,804,200. It adds block header methods for contracts, improves the Bridge's peg-out fee estimate, rejects new contract code starting with byte 0xEF and tightens a precompile's input checks, and lowers default limits on the node's public API.
- Proposal:RSKIP553 adopted
- Implementation:released as node version 9.0.0, with patch releases through 9.0.4
- Release:mandatory release
- Activation:active from mainnet block 8,804,200
Sources: Rootstock — Introducing Vetiver 9.0.0: What You Need To Know About Rootstock's Upcoming Network Upgrade (external site) · Rootstock Improvement Proposals — Network Upgrade: Vetiver (external site) · Blockscout — Rootstock block 8,804,200 (API record) (external site) · Rootstock (GitHub) — rskj releases (external site) · Rootstock Improvement Proposals — Rootstock Improvement Proposals (external site) · Rootstock (GitHub) — RSK Vetiver Release 9.0.0 (external site)
-
Aztec announced its Alpha network with private smart contracts live on Ethereum
Aztec said the Alpha network, its first deployment with a full environment for private smart contracts and user transactions, was live after a community governance vote. It builds on the consensus-only Ignition Chain that started in November 2025. Aztec described Alpha as experimental software with known vulnerabilities and a Layer 1 escape hatch.
- Proposal:approved by community vote
- Implementation:Deployed
- Release:Alpha network announced
- Activation:live on Ethereum mainnet
Sources: Aztec — Announcing the Alpha Network (external site) · Aztec — Critical Vulnerability in Alpha v4 (external site) · Aztec — Aztec Ignition Chain Update (external site) · Aztec Documentation — Alpha Network (external site)
-
Jovian hardfork activated on Celo mainnet
Jovian activated on 31 March 2026 at 12:06:28 UTC. It moved Celo from its own gas price floor to the OP Stack's configurable minimum base fee, adjusted gas accounting for the transfer precompile, prepared for Ethereum's Fusaka upgrade and upgraded the EigenDA proxy.
- Implementation:client releases published
- Release:Released
- Activation:active on mainnet since 31 March 2026
Sources: Celo Forum (core engineering team) — Jovian Hardfork Live on Celo Mainnet (external site) · Celo Documentation — Jovian Hardfork notice (external site)
-
Lighthouse-Pulse v2.5.1 security patch release
PulseChain released Lighthouse-Pulse v2.5.1, a patch release fixing two published security advisories in the yamux networking library. The notes advise all node operators running Lighthouse-Pulse to update and say there are no functional changes to the client.
- Implementation:shipped in lighthouse-pulse v2.5.1
- Release:released 2026-03-31; update advised for all Lighthouse-Pulse operators
- Activation:no activation height; takes effect when each node upgrades
Sources: PulseChain (GitLab, lighthouse-pulse) — Lighthouse-Pulse v2.5.1 release notes (external site) · PulseChain (GitLab, lighthouse-pulse) — Lighthouse-Pulse releases (external site)
-
Two approaches to a base-fee market set out for review
A post co-written by Cody Burns, Diego López León and Istora Mandiri set out two ways to add a base-fee market: the Olympia set (ECIP-1111 to 1119), which would send base fees to an on-chain treasury governed by contracts, with optional miner shares, and ECIP-1120, which would pay base fees to miners, smoothed over past blocks, with no governance layer. The post endorses neither. ECIP-1111 and ECIP-1121 still list no activation block, and OlympiaDAO targets 2027.
- Proposal:Draft ECIPs: the Olympia set from July 2025 to March 2026, ECIP-1120 from December 2025
- Implementation:OlympiaDAO says Fukuii and Core-Geth carry Olympia parameters; the Core-Geth v1.13.0 notes reviewed here do not mention Olympia
- Release:no mainnet release sets an activation block
- Activation:not scheduled; OlympiaDAO targets 2027
Sources: ethereumclassic.org blog (Cody Burns, Diego López León, Istora Mandiri) — The ETC Fee Market Debate: Navigating the Path Forward (external site) · Ethereum Classic Improvement Proposals — ECIP-1111: Base Fee Market and Redirection (external site) · Ethereum Classic Improvement Proposals — ECIP-1120: Basefee Market with Miner Rewards (external site) · Ethereum Classic Improvement Proposals — ECIP-1121: Execution Client Specification Alignment (Olympia Hardfork) (external site) · OlympiaDAO — Upgrade Your Node for Olympia (external site) · Core-Geth maintainers (GitHub) — Core-Geth v1.13.0 release notes (external site)
-
Yield Boost activated: part of the ETH held by Linea's bridge can now be staked
Linea announced Yield Boost as activated with Beta v5.1 on 30 March 2026. It lets ETH held by the rollup's bridge contract above a withdrawal reserve be staked on Ethereum through a Lido V3 vault, with net rewards directed to Linea ecosystem incentive programs. Linea's post planned a 96 ETH test first; the Security Council record shows the Lido vault was created on 17 April 2026, and the staking allowance was later raised to up to 10% of funds on 14 July 2026 and up to 60% on 1 September 2026.
- Implementation:Lido V3 staking vault and yield manager deployed
- Release:Beta v5.1
- Activation:Lido vault created 17 April 2026; allowance raised to up to 60% of funds on 1 September 2026
Sources: Linea — Yield Boost is Activated (external site) · Linea Documentation — Release notes (external site) · Linea Documentation — Yield Boost (external site) · Linea Documentation — Yield Boost risk disclosures (external site) · Linea Documentation — Linea Security Council transaction record (external site)
-
Release 1.24.1 blocked end-of-life machines and removed the MRSIGNER requirement
SCRT Labs published node software 1.24.1 with mainnet install steps. Its notes list four changes: machines with Intel Xeon E-22xx and other end-of-life processors may no longer join the network; Cron is enabled; one governance proposal can add several machines; and the MRSIGNER requirement is removed. The next day the team said on-chain proposal 346 had been submitted to upgrade mainnet to this version. The same change list first appeared in 1.24.0, a pre-release with test-network steps, on 2 February 2026.
- Proposal:proposal 346 submitted (forum notice 2026-03-31); outcome not read in this pass
- Implementation:changes shipped in node release 1.24.1 after the 1.24.0 test-network pre-release
- Release:published 2026-03-30 in the scrtlabs repository
- Activation:not confirmed in this pass; no chain endpoint was read
Sources: scrtlabs/SecretNetwork maintainers — SecretNetwork v1.24.1 release notes (external site) · Secret Network Forum (SCRT Labs post) — Mainnet Upgrade to 1.24.1 (external site) · scrtlabs/SecretNetwork maintainers — SecretNetwork v1.24.0 pre-release notes (external site) · Secret Network Forum (SCRT Labs post) — CPUs blocked in upcoming 1.24 release of Secret Network (external site) · Secret Network Forum (SCRT Labs post) — Upcoming Network Upgrades: EOL Machine Retirement and Easing Permissions to Join (external site)
-
Terra Classic Core v4.0.0 moved the chain to Cosmos SDK 0.53, applied at height 28,214,400
Community developers released terrad v4.0.0 under upgrade plan v14_1, targeting Cosmos SDK 0.53.6, CometBFT 0.38.21 and wasmd 0.61.8. Governance approved the upgrade in proposal 12218, whose voting ended on 15 April 2026, and the chain's upgrade record shows the plan applied at height 28,214,400. The work followed a September 2025 signal to go directly to Cosmos SDK 0.53 with IBC v2 support (proposal 12194).
- Proposal:passed as proposal 12218 (voting ended 2026-04-15)
- Implementation:shipped in classic-terra/core v4.0.0
- Release:released 2026-03-29; followed by v4.0.1 under proposal 12221
- Activation:applied at height 28,214,400 per the chain's upgrade record
Sources: Terra Classic core developers (GitHub) — Terra Classic Core v4.0.0 release notes (external site) · Terra Classic core developers (classic-terra/documents repository) — v14_1 proposal: Software upgrade (Cosmos SDK 0.53.x) (external site) · Terra Classic on-chain state via PublicNode REST endpoint — Terra Classic proposal 12218: Software Upgrade to v4.0.0 (Cosmos SDK v0.53.x) (external site) · Terra Classic on-chain state via PublicNode REST endpoint — Terra Classic applied upgrade plan v14_1 (external site) · Terra Classic on-chain state via PublicNode REST endpoint — Terra Classic proposal 12194: upgrade directly to Cosmos SDK v0.53.x with IBC v2 (external site) · Terra Classic on-chain state via PublicNode REST endpoint — Terra Classic governance proposals (latest 40) (external site)
-
Distributed key generation and Confidential Data Rails reached the Aeneid testnet
PIP Labs released story v1.6.1, a mandatory binary swap for the Aeneid testnet at block 16,332,000, adding distributed key generation, in which a validator committee creates a shared encryption key inside secure enclaves, and Confidential Data Rails, which lets users keep encrypted data in on-chain vaults and have committee members return partial decryptions only to authorized requesters. A consensus bug for DKG-enabled nodes was fixed in v1.6.2, and the Foundation's blog announced the testnet on 10 April 2026.
- Implementation:shipped in story v1.6.1 for Aeneid
- Release:testnet release
- Activation:active on the Aeneid testnet; the docs still described the public release as testnet only on 29 September 2026
Sources: PIP Labs (GitHub) — Story v1.6.1 (Aeneid Testnet only) release notes (external site) · The Data Foundation blog — CDR on Testnet: A New Way to Use Sensitive Data Without Exposing It (external site) · DATA Foundation Docs — CDR Overview (external site) · The Data Foundation blog — We're becoming The DATA Foundation (external site)
-
Telos Privacy opened to the public with zkWallet
Telos released zkWallet, the reference interface for its privacy layer, giving public access to shielded pools on Telos EVM for wrapped TLOS and bridged USDC (USDC.e). The pools are adapted from the zkBob protocol; transfers inside a pool hide sender, receiver and amount, while deposits and withdrawals remain visible. Telos set starting fees of 5 TLOS minimum plus 0.2% for the TLOS pool and $0.20 minimum plus 0.2% for the USDC pool and announced a mobile privacy wallet in development.
- Implementation:pool contracts deployed on Telos EVM
- Release:public release of zkWallet announced 2026-03-27
- Activation:live per Telos; zkWallet returned HTTP 503 when checked on 2026-09-29
Sources: Telos blog — A New Dawn for Telos: Privacy is Live (external site) · Telos Docs — Telos Privacy (external site) · Telos Docs — Telos Privacy: Security (external site) · Telos Docs — Telos Privacy: Deployed Contracts (external site) · Telos blog — Inside the Telos Privacy Layer: Roadmap, Infrastructure and Scaling Path (external site)
-
Chia 2.7.0 security and soft-fork client released
Protocol/reference-client release: Chia 2.7.0 shipped security hardening and soft-fork code that the publisher targeted for block 8,655,000 around April 29–30, 2026. A release and scheduled height do not prove observed activation; this record makes no activation claim.
- Claim:Released
Sources: Chia Network Inc. — Chia 2.7.0: Combatting the AI Siege (external site) · Chia Network Inc. — chia-blockchain 2.7.0 release (external site)
-
Filecoin Onchain Cloud went live on mainnet
The Filecoin blog announced that Filecoin Onchain Cloud, a storage and payments stack using Proof of Data Possession and Filecoin Pay, is live on mainnet after a testnet launch the previous November. The post describes default two-copy replication, approval thresholds for providers and a public proof explorer.
- Implementation:deployed as smart contracts and services on mainnet
- Release:mainnet launch announced 2026-03-26
- Activation:live according to the official announcement; usage not independently observed
Sources: Filecoin (filecoin.io) — Filecoin Onchain Cloud Is Live on Mainnet (external site) · Filecoin Docs — Filecoin Onchain Cloud (external site) · Filecoin Onchain Cloud Documentation — Quick Start with Synapse SDK (external site)
-
ICON entered economic shutdown: emissions and staking rewards ended
The Foundation said all staking rewards and ICX emissions had ended and that the network was in maintenance mode, with consensus handled by a reduced set of seven core nodes. It said the chain would stay live so holders could migrate ICX to SODA on Sonic, and that the bond removal lets validators unbond without penalty.
- Proposal:set out in the 6 February 2026 phased plan
- Implementation:emissions and rewards ended; validator set reduced to seven core nodes
- Release:announced by the Foundation
- Activation:in effect from 26 March 2026; seven main P-Reps observed on 29 September 2026
Sources: ICON Foundation — ICON Network: Economic Shutdown (external site) · ICON Foundation — ICON Network: Migration Roadmap and SODAX Reward Schedule (external site) · ICON community API endpoint (api.icon.community) — ICON mainnet JSON-RPC: getMainPReps on the system contract (read 29 September 2026) (external site)
-
Kava says Lend, Mint and Swap are moving into maintenance mode
Kava said it is concentrating on its EVM side: stablecoin settlement with native USDt, tokenised real-world assets and AI-assisted tooling. Its original protocol modules, Kava Lend, Kava Mint and Kava Swap, will move into maintenance mode. The post said incentive emissions for them would end, users would be asked to withdraw over a reasonable timeframe, and a governance proposal would set out the details.
- Proposal:announced; followed by governance proposals 215 and 221
- Implementation:partly carried out through governance parameter changes
- Release:no software release involved
- Activation:debt caps in force since May 2026; final wind-down terms not settled
Sources: Kava Chain (Medium) — Kava Is Focusing on EVM and Real-World Assets: Here's What That Looks Like (external site) · Kava Labs public REST endpoint — Proposal 215: Phase 1, Cap Kava CDP and Lend Debt, Extend Incentive Claims (external site) · Kava Labs public REST endpoint — Proposal 221: Phase 2, Finalize Kava CDP and Lend Debt Parameters, Extend Incentive Claims (external site)
-
Movement launched USDCx, a USDC-backed stablecoin through Circle xReserve
Movement announced USDCx, a stablecoin issued on its mainnet and backed 1:1 by USDC held in Circle's xReserve, with minting and redemption verified through xReserve attestations.
- Implementation:deployed per Movement's announcement
- Release:announced live 2026-03-25
- Activation:active per the announcement; supply and contract not reviewed
Sources: Movement Network — Introducing USDCx: Movement's Native USDC-Backed Stablecoin (external site) · Circle — How xReserve works (external site) · Circle — USDC Contract Addresses (external site)
-
Dynamic deployment pricing replaced processor-set prices after an on-chain vote
Acurast replaced prices set by processor managers with prices derived from each processor's share of benchmark rewards, times a governance-set multiplier and above a governance-set minimum. Matchers are now paid only when a processor acknowledges an assignment. The change shipped in Mainnet runtime 12 (release v0.25.1, 20 March 2026), and Acurast says it passed an on-chain vote and is live.
- Proposal:approved by an on-chain vote according to Acurast; the referendum number was not found
- Implementation:shipped in acurast-substrate v0.25.1 (Mainnet runtime 12)
- Release:released 2026-03-20
- Activation:live on Mainnet according to Acurast's 2026-03-24 post
Sources: Acurast blog — Dynamic Pricing: A New Era for Compute Value (external site) · Acurast (GitHub) — acurast-v0.25.1 release notes (Mainnet Runtime 12) (external site) · Acurast Docs — Deployment Pricing (external site)
-
Sui is retiring its JSON-RPC interface in favour of gRPC and GraphQL RPC
On 24 March 2026 Sui announced that its newer data interfaces (gRPC, GraphQL RPC and an archival store) were ready for production use and that JSON-RPC would be switched off on 31 July 2026. Sui's migration guide says JSON-RPC was disabled on the Sui Foundation's mainnet full nodes in the week of 27 July 2026. It gives target dates for the later steps: the Foundation stops publishing JSON-RPC snapshots at the end of August, the automatic fallback to the archival service is cut at the end of September, and JSON-RPC is removed from full nodes, code included, in mid-October 2026. A change removing the JSON-RPC service from the full node was merged on 25 September 2026.
- Proposal:deprecation announced on the Sui blog on 2026-03-24
- Implementation:JSON-RPC service removal merged into the main branch on 2026-09-25
- Release:removal not in a mainnet release as of 2026-09-27; the latest was mainnet-v1.80.1 (2026-09-23)
- Activation:disabled on Sui Foundation mainnet full nodes from the week of 27 July 2026; full decommission planned for mid-October 2026
Sources: Sui Documentation — JSON-RPC Migration Guide (external site) · Sui Foundation blog — GraphQL and Archival Store Complete the Sui Data Stack (external site) · MystenLabs/sui repository — fullnode: remove jsonrpc (external site) · MystenLabs/sui repository — MystenLabs/sui releases (external site)
-
Casper 2.2.0 activated with a one-time issuance and a 2% ecosystem share of yearly issuance
Casper mainnet upgraded to 2.2.0 at era 21742 on 23 March 2026, applying validator votes CVV006 and CVV008. The upgrade minted 4,763,091,158 CSPR once, held in a treasury wallet and released over two years; sent a quarter of new issuance, 2% of supply a year, to an ecosystem sustainability purse; added a minimum delegation rate setting, set to zero for now; cut the minimum validator bid to 500 CSPR; and fixed checks on delegation limits.
- Proposal:CVV008 posted 2026-02-22; vote held 23 to 25 February 2026 and passed
- Implementation:casper-node v2.2.0
- Release:released 2026-03-10
- Activation:activated 2026-03-23 at era 21742 per the Casper Association
Sources: Casper Association — Casper 2.2.0 Goes Live on Mainnet (external site) · Casper Network (GitHub) — casper-node v2.2.0 release notes (external site) · Casper Network forum — [CVV008] Proposal: Securing Validator Economics and Network Sustainability (external site) · Casper Association — Governance Vote #008 Passes: Securing Validator Economics and Network Sustainability (external site) · Casper Network (casper-node repository, GitHub) — Casper mainnet chainspec, protocol version 2.2.2 (external site)
-
SKALE DAO approved SIP-5, a minimum stake that rises with each extra supernode
SIP-5, posted by the SKALE Foundation with SKALE Labs and Blockdaemon, replaces the flat 20 million SKL minimum stake per supernode with a progressive one: 20 million for a validator's first supernode, 40 million for the second and 60 million for the third, rising further after that. The post expected the network to shrink from 98 supernodes to about 45 with the same total stake. Snapshot records the vote from 16 to 23 March 2026 as closed with every vote in favour and above its recorded quorum.
- Proposal:approved by SKALE DAO Snapshot vote (closed 2026-03-23)
- Implementation:not verified in SKALE Manager
- Release:not verified
- Activation:not verified
Sources: SKALE Network Forum — SIP-5: Progressive MSR for Network Efficiency (external site) · Snapshot — Snapshot hub: skale.eth proposals, states, scores and quorum (read 2026-09-29) (external site)
-
Bitlayer says its public RPC will stop serving historical state
Bitlayer announced maintenance on its mainnet and testnet public RPC nodes and said that afterwards the public service would answer balance and contract-call queries only for the latest state, not for past block heights. Applications that need history were told to run their own archive node or use third-party providers.
- Implementation:Announced
- Release:not a software release
- Activation:after the maintenance window; exact date not stated in the post
Sources: Bitlayer Blog — Bitlayer Public RPC Service Maintenance Announcement (external site) · Bitlayer Documentation — Compile, Run and Deploy (external site)
-
Tenfold gas schedule increase (AIP-141) executed on mainnet
Governance executed AIP-141, which multiplies every gas cost and storage fee parameter by ten while scaling per-transaction gas limits by the same factor. Fees in APT rose about tenfold for the same work; the amount of computation allowed per transaction did not change.
- Proposal:AIP-141 marked Accepted
- Implementation:new on-chain gas schedule
- Release:delivered by governance proposal 185
- Activation:executed on mainnet 2026-03-19 per the governance page
Sources: Aptos Governance (Aptos Foundation) — AIP 141: Update gas schedule, increase gas fee 10x (external site) · Aptos Foundation AIPs — AIP-141: 10x Gas Fee Increase (external site)
-
Igra Labs announced public mainnet for its EVM layer on Kaspa
Igra Labs announced that Igra Network, an EVM layer that uses Kaspa to order its transactions, opened public mainnet access, with KAS bridged as iKAS for gas and Hyperlane links to other chains.
- Implementation:mainnet announced by the project
- Release:public mainnet announced 2026-03-19
- Activation:project-reported; not independently verified
Sources: Igra Labs via Chainwire — Igra Network Launches Public Mainnet as Decentralized EVM Layer on Kaspa's Proof-of-Work BlockDAG (external site) · Igra Labs via Chainwire — Igra Network Announces IGRA Public Token Sale (external site)
-
Burn-mint equilibrium scheduled for Akash Mainnet 17
Akash announced that burn-mint equilibrium (AEP-76) would activate with the Mainnet 17 upgrade, approved as proposal 318, at block 26,063,777 around 23 March 2026. Tenants burn AKT to mint ACT for leases, and providers redeem earned ACT for AKT at the current price. Akash's Q1 report says the upgrade went live on 23 March 2026.
- Proposal:on-chain proposal 318 passed
- Implementation:implemented in the Mainnet 17 upgrade
- Release:Released
- Activation:activated 2026-03-23 per Akash's Q1 2026 report; applied on chain at height 26,063,777
Sources: Akash Network — What Burn-Mint Equilibrium Means for Akash (external site) · Akash Network — Akash Network: Q1 2026 Report (external site) · Akash Network — AEP-76: Burn Mint Equilibrium on Akash (external site) · Polkachu public Akash REST node — Applied upgrade plan v2.0.0 (akashnet-2 chain state) (external site)
-
Emergency Core-Geth releases after an attack on Ethereum Classic bootnodes
Core-Geth v1.12.21 was an emergency patch for an active attack in which malicious peer traffic made nodes crash-loop through missing checks in the handshake code. v1.12.22 (28 March) moved peer discovery to a new domain and backported further cryptographic fixes, and v1.12.23 (14 August) adopted upstream delayed decoding of peer messages. None of the three changed consensus.
- Implementation:shipped in etclabscore/core-geth v1.12.21 to v1.12.23
- Release:released; strongly recommended for internet-facing nodes
- Activation:no activation block; takes effect when each node upgrades
Sources: Core-Geth maintainers (etclabscore, GitHub) — Core-Geth v1.12.21 (Aegis) release notes (external site) · Core-Geth maintainers (etclabscore, GitHub) — Core-Geth v1.12.22 (Hermes) release notes (external site) · Core-Geth maintainers (etclabscore, GitHub) — Core-Geth v1.12.23 (Argos) release notes (external site) · Core-Geth maintainers (GitHub) — Core-Geth v1.13.0 release notes (external site)
-
Helium World rebuilt with email sign-up and built-in reward splitting
Helium announced a rebuilt Helium World for deployers: new accounts are created with an email address and passkeys through Privy, with no seed phrase; Hotspots can be onboarded and managed from a web dashboard; rewards can be split with venue hosts; and a migration tool moves Hotspots from the older app.
- Implementation:Released
- Release:announced as live by Helium
- Activation:available per Helium; not tested because the site refused automated reads
Source: Helium blog — Deployers, Rejoice! Helium World Is Getting a Major Upgrade. (external site)
-
Governance approved the v4 upgrade that switches on liquid-staking settings for every validator
Proposal 28 passed on 2026-03-17 with no recorded opposition and scheduled the upgrade named 3-to-4 at height 10,852,141, after an earlier attempt (proposal 26) failed. The v4.0.0 release sets up liquid-staking records for every validator with an 80% overall cap and a 100% per-validator cap. Public nodes reported version 4.0.0 on 2026-09-27.
- Proposal:passed (proposal 28)
- Implementation:released as v4.0.0
- Release:tagged 2026-03-06; release published 2026-03-12
- Activation:scheduled at height 10,852,141; nodes reported 4.0.0 on 2026-09-27
Sources: Polkachu public REST endpoint — ssc-1 governance proposal 28: Upgrade SSC to v4 (external site) · Polkachu public REST endpoint — ssc-1 recent governance proposals (external site) · Saga (GitHub) — ssc v4.0.0 release notes (external site) · Saga (GitHub) — sagaxyz/ssc tags (external site) · Polkachu public REST endpoint — ssc-1 node info (live query) (external site) · Saga (GitHub) — sagaxyz/ssc releases (Atom feed) (external site)
-
Tokenomics 3.0 lowered the issuance ceiling and capped rewarded projects at 16
Two referenda activated Tokenomics 3.0: new inflation parameters (a 5.5% yearly ceiling, down from 7%, with per-block emission decay) and runtime 2101, which reworked dApp staking into a yearly cycle with at most 16 rewarded projects in two tiers and no bonus rewards. Astar says supply now converges toward about 10 billion ASTR.
- Proposal:passed as referenda 50 and 51
- Implementation:decay factor shipped in runtime 1900; dApp staking changes in runtime 2101
- Release:runtime 1900 and runtime 2101 releases; the new inflation parameters were set by a governance call in referendum 50, not by a release
- Activation:active on Astar mainnet since 2026-03-16
Sources: Astar blog — Astar Tokenomics 3.0: Transitioning to a Fixed-Supply Economic Model (external site) · Subsquare (Astar democracy) — Referendum 50: Update Tokenomics 3.0 Inflation Parameters (external site) · Subsquare (Astar democracy) — Referendum 51: Astar Runtime 2101 Upgrade (dApp Staking Revamp for Tokenomics 3.0) (external site) · Astar blog — dApp Staking Simplified: One Stake, 16 Projects (external site) · Astar Docs — Tokenomics 3.0 FAQs (external site) · Subsquare (Astar democracy) — Referendum 44: Astar Runtime 1900 Upgrade (Asset Hub migration prep, tokenomics decay, collator governance) (external site)
-
Horizen Labs opened Vela confidential compute to developers
Horizen Labs named its confidential-compute environment Vela and released it as a local development kit, with dedicated testnet instances on request. Vela's docs now describe version 0.2.0 on Base Sepolia and Horizen testnet, and its roadmap names Base mainnet as the next milestone.
- Implementation:version 0.2.0 released
- Release:local development and testnets
- Activation:not on mainnet as of this review
Sources: Horizen Blog — Introducing Vela: The Confidential Compute Layer on Horizen (external site) · Horizen Documentation — Vela introduction (external site) · Horizen Documentation — Vela roadmap (external site)
-
GP-20 sets a policy for opening Kaia validation to qualified candidates
The Kaia Foundation posted GP-20, a policy for moving from an approved Governance Council to open validator participation, and the governance forum now marks it as passed. Anyone could become a candidate; one that passes the VRank performance evaluation and has 5 million KAIA staked would become a validator, and the 50 largest stakes would take part in consensus. Council membership would become a separate role gained automatically after a seven-day challenge window. The policy applies only once the permissionless transition is complete, which Kaia's roadmap targeted for late September 2026.
- Proposal:policy proposal published 2026-03-12; marked passed on the governance forum
- Implementation:draft KIPs (KIP-277, KIP-286, KIP-287); v3.0.0 release candidates tagged in July and August 2026
- Release:no final release found at review
- Activation:not active on mainnet; the public endpoint listed no next fork on 2026-09-29
Sources: Kaia Governance Forum — [GP-20] Kaia Permissionless Network Policy (English) (external site) · Kaia Blog — PGT Part 1: Kaia's Structural Transition to a Permissionless & Performance-Based Network (external site) · Kaia Improvement Proposals — KIP-286: Permissionless Validator Lifecycle (external site) · Kaia Governance Forum — Permissionless Implementation Overview (external site) · Kaia (GitHub) — kaiachain/kaia releases (external site) · Kaia Docs and Kaia Foundation endpoint — eth_config method; read of the Kaia Foundation public endpoint on 2026-09-29 (external site)
-
MONAD_NINE hard fork: linear memory, reserve-balance precompile and a new CLZ opcode
Client release v0.13.0 reached mainnet operators on 12 March 2026 and activated the MONAD_NINE revision at 14:30 UTC on 19 March 2026. It brought MIP-3 (linear memory pricing), MIP-4 (a precompile for reserve-balance checks) and MIP-5 (the CLZ opcode and changed modexp bounds and gas). The same release made the RPC tag "latest" return the latest Proposed block and sped up receipts and websocket notices.
- Proposal:MIP-3, MIP-4 and MIP-5 adopted into the MONAD_NINE revision
- Implementation:shipped in monad-bft v0.13.0 and monad v0.13.0+1
- Release:mainnet release 12 March 2026
- Activation:activated on mainnet 19 March 2026 at 14:30 UTC
Sources: Monad Documentation (Monad Foundation) — Releases (external site) · Monad Documentation (Monad Foundation) — v0.13.0 (MONAD_NINE) upgrade instructions (external site) · Monad Documentation (Monad Foundation) — Changelog (revisions and chain configs) (external site) · Category Labs (GitHub) — monad-bft v0.13.0 (MONAD_NINE) (external site)
-
Oasis Core 26.0 released with an SGX quote-policy change and storage fixes
Oasis Core 26.0 is a node software release that keeps the consensus (7.0.0), runtime host (5.1.0) and runtime committee (5.0.0) protocol versions of 25.9. Its one listed breaking change adds an FMSPC whitelist field to the SGX quote policy used when checking enclave attestations. It adds a storage inspect command for offline maintenance, fixes a pruning edge case that could remove runtime light history too early, stops a node with pruning turned off from deleting data left from an earlier pruning run, corrects a PCE SVN check in SGX TCB validation and makes the scheduler skip key manager runtimes. The release notes thank Bluethroat Labs for responsibly disclosing several problems but do not say which changes address them.
- Implementation:Released
- Release:26.0 published 2026-03-12; superseded by 26.1 on 2026-06-08
- Activation:no network upgrade tied to the release; FMSPC whitelist entries accepted only once feature version 24.2 is enabled, not confirmed for Mainnet
Sources: oasisprotocol on GitHub — Oasis Core 26.0 (external site) · oasisprotocol/oasis-core maintainers — Oasis Core change log (v26.1) (external site) · oasisprotocol on GitHub — oasis-core pull request #6331: FMSPC whitelist in the SGX quote policy (external site) · oasisprotocol/oasis-core maintainers — go/common/sgx/quote/quote.go at v26.0 (external site) · oasisprotocol on GitHub — go/v0.2600.0 (Version 26.0) (external site) · Oasis documentation — Mainnet network parameters (external site)
-
Telos removed most standing TLOS issuance
Telos said the majority of its zero-inflation proposal had been implemented: monthly issuance for staking rewards, grants, core development and the Foundation was cut to zero, removing 19.8 million TLOS a year by its count and leaving producer pay as the only issuance. Telos put yearly issuance at about 0.84% of supply, down from about 5.26%, and said the Foundation offsets the rest from reserves. A cut to producer pay tied to a smaller producer set was still being prepared for a vote.
- Proposal:zero-inflation proposal published 2026-02-12 with an on-chain ballot
- Implementation:most allocation cuts implemented by 2026-03-12
- Release:producer-pay adjustment pending an amendment vote as of 2026-03-12
- Activation:allocation cuts active per Telos; not verified on chain
Sources: Telos blog — Telos Begins the Zero-Inflation Era (external site) · Telos blog — Telos: The Zero Inflation Era (proposal) (external site) · Telos (validators.telos.net) — Telos validator dashboard: machine-readable validation data (external site) · Telos Docs — How To Stake TLOS (external site)
-
WAX Cloud Wallet adds a Vault signing session and phrase-based passkey recovery
WAX released a beta of its new Cloud Wallet (My Cloud Wallet) with a Vault window that keeps a signing session open, so repeated dApp requests do not each need a passkey confirmation, and with the ability to import the wallet's 12-word phrase to create a new passkey, either to recover after losing a device or to add a second device. The legacy wallet stayed live, and users could migrate when ready; a step-by-step migration guide followed on 23 March 2026.
- Implementation:released as a beta of the new wallet
- Release:live per WAX; legacy wallet kept
- Activation:WAX's current docs describe the passkey wallet as the latest version and cover migration; not tested here
Sources: WAX (wax-io.medium.com) — WAX.io blog feed (external site) · WAX Blockchain Documentation — My Cloud Wallet (external site) · WAX Blockchain Documentation — Migrate to the New My Cloud Wallet (external site)