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 8 of 14.
One chain's developments, A to Z
-
v3.19.0 carried the fixes to reopen the network after the exploit
THORNode v3.19.0 shipped the TSS patches behind the restart, walled off the compromised vault from new deposits and added a temporary key check before trading resumed. It also merged Monero chain support, which still needed testing and a node vote to activate, and an affiliate revenue share.
- Implementation:shipped in THORNode v3.19.0 (private binary)
- Release:v3.19.0 tagged 2026-06-05
- Activation:upgrade at block 26,518,000; trading resumed around 22 June 2026; Monero not yet activated
Sources: THORChain blog — THORChain Protocol Upgrade v3.19.0 (external site) · THORChain (GitLab) — THORNode v3.19.0 release (external site) · THORChain blog — State of the Network - June 2026 (external site) · THORNode API, public endpoint run by Liquify — THORNode /thorchain/inbound_addresses via Liquify (read 2026-09-29) (external site)
-
Akash node v2.1.0 released for Mainnet 18
Akash released node v2.1.0 for the Mainnet 18 upgrade (proposal 328), scheduled at block 27,230,465 around 11 June 2026. It redesigned the oracle module, which reset stored price history, and added provider-initiated resource reclamation (AEP-82) with a tenant grace period whose default bounds are 1 hour to 30 days.
- Proposal:on-chain proposal 328 passed (voting ended 2026-06-10)
- Implementation:v2.1.0 released; later patches v2.1.1 and v2.1.2 published
- Release:released 2026-06-08
- Activation:applied on chain at height 27,230,465 (estimated 2026-06-11 in Akash's guide; the roadmap marks AEP-82 complete that day)
Sources: akash-network/node maintainers — Akash node v2.1.0 release (external site) · Akash Network — Mainnet 18 upgrade guide (v2.1.0) (external site) · Akash Network — Akash 2026 roadmap (external site) · akash-network/node maintainers — akash-network/node releases (external site) · Polkachu public Akash REST node — Applied upgrade plan v2.1.0 (akashnet-2 chain state) (external site)
-
Oasis Core 26.1 released and listed as the Mainnet node version
Oasis Core 26.1 added an explicit observer mode, a setting that lets a client node use remote state checked by its light client instead of local storage (replacing the earlier stateless-client mode), and released offline storage pruning and compaction commands. It also added a check of the runtime identifier on messages in the root hash service and updated its CometBFT fork. Its protocol versions are unchanged from 26.0.
- Implementation:Released
- Release:26.1 published 2026-06-08
- Activation:listed as the Mainnet version on the network parameters page at review
Sources: oasisprotocol/oasis-core maintainers — Oasis Core change log (v26.1) (external site) · oasisprotocol on GitHub — Oasis Core v26.1 release (external site) · Oasis documentation — Mainnet network parameters (external site) · oasisprotocol on GitHub — go/v0.2601.0 (Version 26.1) (external site)
-
Bitcoin Core disclosed a PrivateBroadcast IP-address leak
Bitcoin Core disclosed that the PrivateBroadcast feature introduced in 31.0 could, under specified transaction-submission, Tor, and peer conditions, reveal an originator's IP address. The project said the flaw would be fixed in 31.1, whose release notes subsequently list the fix.
- Stage:Reported
Sources: Bitcoin Core contributors — Disclosure of an IP address leak in PrivateBroadcast (external site) · Bitcoin Core contributors — Bitcoin Core 31.1 release notes (external site)
-
EOS Rio published alpha builds of a community Spring 1.2.x maintenance line
EOS Rio, a producer, released Spring v1.2.3-alpha1 from its own fork, describing it as continuing Spring after upstream work stalled. It is built on v1.2.2 with a rule of no consensus, wire-format or API changes, moves the optimized contract compiler to a current LLVM version and collects unreleased upstream fixes. A second alpha, proposed in September 2026, adds fixes for security and stability reports, including checks in BLS host functions and Savanna vote handling.
- Implementation:alpha builds published by a producer
- Release:alpha, for testing only
- Activation:none; no consensus rule changes
Sources: EOS Rio (GitHub) — Spring v1.2.3-alpha1 (eosrio/spring maintenance line) (external site) · EOS Rio (GitHub) — release: v1.2.3-alpha2, community security and stability fixes (external site) · AntelopeIO (GitHub) — Spring v1.2.2 release notes (external site)
-
Frax rebuilt its Fraxtal op-node on Optimism's op-node 1.19.0 and moved its node setup to it
On 4 June 2026 Frax published op-node 1.19.0-frax-1.2.1, its Fraxtal consensus client with the Frax 1.2.1 changes carried onto Optimism's op-node 1.19.0; the release note lists no other change. On 17 June 2026 Frax switched the Docker setup in its fraxtal-node repository, for mainnet and the Hoodi testnet, to this op-node build and to op-reth v2.3.1-frax-1.3.4, and replaced the node start-up script. No fraxtal-node release was tagged for this change and it was not marked required.
- Implementation:released as a Frax op-node build; adopted in the fraxtal-node master configuration on 2026-06-17
- Release:op-node 1.19.0-frax-1.2.1 component release; no fraxtal-node release tag for it as of 2026-09-27
- Activation:operator upgrade; no hard fork or activation time stated
Sources: Frax Finance on GitHub — op-node-1.19.0-frax-1.2.1 (external site) · Frax Finance on GitHub — fraxtal-node commit cc49857: Update reth/node versions (external site) · Frax Finance on GitHub — FraxFinance/fraxtal releases (external site) · Frax Finance on GitHub — fraxtal-node releases (external site)
-
Cronos zkEVM Alpha to be shut down in June 2027
Cronos announced the sunset of Cronos zkEVM, its separate Ethereum-settled ZK Stack chain. Bridge deposits closed at the announcement, withdrawals stay open for about a year, and final shutdown is set for 3 June 2027 at 03:00 UTC. Cronos cited resource focus and ecosystem growth below the level needed to sustain a parallel chain.
- Implementation:bridge deposits disabled
- Release:withdrawal-only period
- Activation:final shutdown scheduled for 2027-06-03 03:00 UTC
Sources: Cronos — Sunsetting the Cronos zkEVM Alpha in 2027 (external site) · Cronos — Cronos zkEVM documentation (external site)
-
Cosmos chain registry marks Evmos as killed
A merged change to the Cosmos chain registry set Evmos's status from live to killed, stating that mainnet evmos_9001-2 was shut down through proposal 331 and halted at about block 37,318,000 around 18 May 2026.
- Implementation:Merged
- Release:published in the registry's master branch
- Activation:in effect
Sources: Cosmos chain-registry maintainers — chore(evmos): mark chain status as killed (#7710) (external site) · Cosmos chain-registry maintainers — Evmos chain registry record (external site)
-
Mandatory v0.14.16 releases change Spark Name renewals from block 1,329,000
Firo's mandatory v0.14.16.0 release (15 May 2026) let owners extend, update or transfer a Spark Name and keep credit for the validity they had left, so they pay only for added time. v0.14.16.1 (3 June 2026) fixed an overflow bug in that new code and a flaw that let Spark Name transfer permissions stay valid indefinitely. Firo told all wallets, nodes and masternodes, including those already on v0.14.16.0, to upgrade before block 1,329,000, expected around 22 June 2026.
- Implementation:credit rule shipped in v0.14.16.0; overflow and transfer-permission fixes in v0.14.16.1; reference code starts the new Spark Name rules at block 1,329,000
- Release:v0.14.16.0 released 2026-05-15 and v0.14.16.1 released 2026-06-03, both labelled mandatory
- Activation:height 1,329,000 is below the 1,384,521 height Firo's explorer reported on 2026-09-27; the date that block was mined was not checked
Sources: Firo developers (firoorg) — Firo v0.14.16.1 (GitHub release) (external site) · Firo — Mandatory Release: Firo v0.14.16.1 (external site) · Firo developers (firoorg) — Firo v0.14.16.0 (GitHub release) (external site) · Firo — Mandatory Release: Firo v0.14.16.0 (external site) · Firo developers (firoorg) — Firo reference node: src/firo_params.h (master) (external site) · Firo — Firo Insight API status (external site)
-
Mandatory node release 1.6.3 for mainnet, testnet and stagenet
Waves published node 1.6.3 on 3 June 2026 and marked it mandatory for mainnet, testnet and stagenet, asking every node operator to update. The release notes say it updates dependencies and strengthens transaction validation, but they do not list the specific checks. They name no new protocol feature for producers to vote on, and nodes moving from 1.6.2 do not need to rebuild their state.
- Implementation:implemented in node 1.6.3; followed by node 1.6.4 on 2026-08-27
- Release:mandatory release 1.6.3 published 2026-06-03; not a pre-release
- Activation:no feature activation named in the release; the changes apply on each node once its operator installs it
Sources: wavesplatform on GitHub — Waves node v1.6.3 release notes (external site) · wavesplatform on GitHub — Waves node releases (Atom feed) (external site) · wavesplatform on GitHub — Waves node releases (external site)
-
XDC Innovation Labs published a draft post-quantum signature standard for trade documents (XDSS-PQ)
XDC Innovation Labs, a contributor that builds node infrastructure for XDC, published XDSS-PQ Draft v1.0, a proposed standard that signs long-lived trade-finance documents with two post-quantum schemes, ML-DSA and Falcon (FN-DSA), and treats a document as valid only if both signatures verify. The page calls the work forward-looking and in development. The XDC Foundation says the protocol team began a post-quantum initiative in March 2026 with a Falcon prototype in a development codebase.
- Proposal:Draft v1.0 specification published
- Implementation:a Falcon prototype in a development codebase, per the XDC Foundation; not verified
- Release:not released
- Activation:not active on mainnet
Sources: XDC Innovation Labs — XDSS-PQ Specification (Draft v1.0) (external site) · XDC Innovation Labs — About - XDC Innovation Labs (external site) · XDC Foundation — Seven Years of XDC Mainnet: Welcoming the Future of Finance (external site)
-
zcashd 6.20.0 shipped immediate NU6.2 support and Orchard fixes
zcashd 6.20.0 added support for NU6.2 at mainnet height 3,364,600, updated the Orchard circuit verifying key after disclosure of a critical implementation flaw, and enforced the valid proof-data length for Orchard proofs.
- Stage:Release
Source: Zcash developers — zcashd 6.20.0 release (external site)
-
Saga company hands long-term operation of the blockchain to Alapin Holdings
Saga announced it had sold its crypto arm and launched Saga AI Labs. The post says the agreement transfers long-term operational responsibility for the Saga blockchain protocol and its associated crypto ecosystem to Alapin Holdings, described as a protocol operator within the dao5 family, which will oversee the network's continued operation as independent infrastructure. The announcement does not say what changes, if any, validators or token holders should expect.
- Implementation:agreement announced by Saga
- Release:no software change
- Activation:chain still producing blocks on 2026-09-27; the operator change was not independently confirmed
Sources: Saga — Saga Sells Crypto Arm as Success in AI Business Grows, Launches Saga AI Labs (feed item) (external site) · Saga (via EIN Presswire) — Saga Sells Crypto Arm as Success in AI Business Grows, Launches Saga AI Labs (press release) (external site) · Saga — Saga home page (external site) · Saga — About Saga (external site) · Polkachu public REST endpoint — ssc-1 latest block (height 13,799,747) (external site) · Saga (GitHub) — sagaxyz/ssc tags (external site)
-
SIP-4 SKL burning moved to production for SKALE on Base
SIP-4, posted on 7 January 2026 and approved in a SKALE DAO Snapshot vote that closed on 21 January, makes every SKALE Expand deployment send half of its revenue from subscriptions, gas and credit sales back to Ethereum each month, where it is burned as SKL (or used to buy SKL that is then burned); the other half goes to that deployment's node operators. A June 2026 forum post said the mechanism had left beta and was live for SKALE on Base, with the first burns imminent. The economics of the original Ethereum deployment are unchanged.
- Proposal:approved by SKALE DAO Snapshot vote (closed 2026-01-21)
- Implementation:shipped according to the 2026-06-01 forum post
- Release:moved out of beta into production for SKALE on Base
- Activation:live for SKALE on Base per the post; actual burns not verified
Sources: SKALE Network Forum — SKL Burning Is Live: SIP-4 Moves From Vote to Production (external site) · SKALE Network Forum — [SIP-4]: SKL Burning & SKALE Expand Economics (external site) · Snapshot — Snapshot hub: skale.eth proposals, states, scores and quorum (read 2026-09-29) (external site)
-
op-reth became Boba's only supported execution client
Boba's docs say op-geth and op-erigon reached end-of-life on 31 May 2026 and that op-reth is the only supported execution client. Node operators must migrate using Boba's migration tools, and Boba published op-reth snapshots dated 26 May 2026.
- Implementation:op-reth v2.3.1 named as the required client
- Release:released; snapshots published 2026-05-26
- Activation:legacy clients unsupported from 2026-05-31
Sources: Boba Network Docs — Preparing for Isthmus and Jovian breaking changes (external site) · Boba Network Docs — Node Operators (external site) · Boba Network Docs — Node Snapshots (external site) · Boba Network Docs — Node Software Releases (external site)
-
Hashport bridge permanently shut down
Hashport, a bridge between Hedera and other networks run by a group of validators, states that it was permanently decommissioned on 31 May 2026 at 12:00 UTC. Its notice says all bridging infrastructure is offline and wrapped assets are permanently unredeemable.
- Implementation:service decommissioned
- Release:not applicable to a shutdown
- Activation:offline since 2026-05-31
-
Three Sui mainnet halts on 28 and 29 May 2026
Sui mainnet stopped three times over two days. Two halts came from a gas-charging bug involving address balances introduced in release 1.72, which caused an arithmetic underflow during settlement; the third came from a latent bug in how validators keep randomness state across restarts. Sui reports that no user funds were at risk and no committed transaction was reverted.
- Implementation:three fixes implemented
- Release:emergency node releases shipped on 28 and 29 May 2026
- Activation:network resumed after each halt
Sources: Sui Foundation blog — Sui mainnet halts resolved after major upgrade (external site) · MystenLabs/sui repository — MystenLabs/sui releases (external site)
-
Bitlayer's official bridge drops BRC-20 and Runes tokens
Bitlayer announced that its official bridge would stop supporting BRC-20 and Runes tokens, permanently disabling deposits and withdrawals for them, and advised holders to bridge back to Bitcoin before the cut-off. BTC, ETH and stablecoins were stated to be unaffected. The post is dated 28 May 2026 but gives 30 May 2025 as the cut-off date.
- Implementation:Announced
- Release:not a software release
- Activation:cut-off date stated inconsistently (2025 in the body, 2026 post date)
Sources: Bitlayer Blog — Discontinuation of BRC20 and Runes Asset Support on the Official Bridge (external site) · Bitlayer Documentation — Peg Tokens (external site) · Bitlayer Documentation — Proof of Reserve (external site)
-
Aleo Stack v4.7.0 brought consensus version 15 and view-only program functions
Provable announced Aleo Stack v4.7.0, which carries consensus version 15 and requires validators and client nodes to upgrade before its activation height. Programs can now be deployed with view-only functions that read on-chain state. Node operators can stream finalize events, such as mapping updates and staking rewards, to outside services through a plugin framework, and the Aleo SDK caches proving material to speed up proving on the user's side. The snarkOS v4.7.0 mainnet release was published on GitHub on 28 May 2026.
- Implementation:shipped across snarkOS, snarkVM, Leo and the Aleo SDK per the post
- Release:mainnet release v4.7.0 published on GitHub 2026-05-28, followed by point releases up to v4.7.5 on 2026-06-23
- Activation:V15 mainnet height not confirmed here. Inference: later releases scheduled versions up to V20, so V15 is most likely active
Sources: Provable — Announcing Aleo Stack v4.7.0 (external site) · ProvableHQ/snarkOS maintainers — snarkOS v4.7.0 release (external site) · ProvableHQ/snarkOS maintainers — ProvableHQ/snarkOS releases (external site)
-
Bitlayer discontinues its BitVM Bridge
Bitlayer announced it would discontinue its existing BitVM Bridge for an architectural overhaul. BTC deposits to mint YBTC stopped on 28 May 2026 and withdrawals were allowed until 3 June 2026, after which all bridge functions were disabled. The Security Council was to settle broker liquidity directly and burn the matching YBTC on Ethereum, with small leftover balances redeemed over the counter. YBTC.B was stated to be unaffected.
- Implementation:announced; a Phemex article updated 27 August 2026 reported the bridge closed since June 2026
- Release:not a software release
- Activation:deposits disabled 28 May 2026 and withdrawals ended 3 June 2026 per the post
Sources: Bitlayer Blog — Announcement: Discontinuation of BitVM Bridge Service (external site) · Bitlayer Documentation — BitVM Bridge Network (BBN) Governance Framework (external site) · Bitlayer Documentation — BitVM Bridge Mainnet (external site) · Phemex Blog — What Is Bitlayer (BTR) and What Happened to Its Bitcoin Bridge (external site)
-
Network version 28 (Fire Horse) activated on mainnet
Filecoin's NV28 upgrade was scheduled by Lotus v1.36.0 for epoch 6052800 on 27 May 2026, and the Filecoin blog announced it live that day. It lets contracts check sector status and expiry (FIP-0112), adds a P-256 signature precompile for passkeys (FIP-0113), adds the CLZ opcode (FIP-0114) and changes base-fee adjustment to a tip-based target (FIP-0115).
- Proposal:FIPs 0112 to 0115 Final
- Implementation:implemented in Lotus v1.36.0 with built-in actors v18
- Release:Lotus v1.36.0 released 2026-05-13
- Activation:announced live on mainnet 2026-05-27; activation not independently observed
Sources: filecoin-project/lotus — Lotus v1.36.0 (network version 28, Fire Horse) (external site) · Filecoin (filecoin.io) — Filecoin's NV28 Fire Horse Network Upgrade is Here (external site) · Filecoin Improvement Proposals — FIP-0115: Premium Percentile Base Fee Target (external site)
-
Union Bridge released on Rootstock testnet
Rootstock released Union Bridge, a BitVMX-based bridge in which disputes are meant to be settled on Bitcoin with proofs rather than by a fixed signer set, on testnet through Atlas. The release is experimental, lacks dispute resolution and fraud proofs, and Rootstock plans a second testnet in 2026 and a gradual mainnet launch in 2027.
- Implementation:basic flows only; no dispute resolution yet
- Release:Testnet
- Activation:not on mainnet; mainnet planned for 2027
Sources: Rootstock — Introducing Union Bridge on Testnet: Verifiable Bitcoin Bridging Begins (external site) · Rootstock — Introducing Atlas: The easiest way in to BTCFi (external site)
-
StarkWare published v0.14.3 pre-release notes: faster blocks and an automatic minimum-fee rule
The pre-release notes scheduled v0.14.3 for mainnet on 6 July 2026. It cuts the typical block slot from 2 to 1.5 seconds with a lower per-block gas target (SNIP-40), adjusts the minimum L2 gas price automatically from the STRK/USD price (SNIP-35), switches the core contract's program hash to Blake, and drops support for JSON-RPC 0.8. L2BEAT's governance team said it was inclined to vote against, citing sequencer fee incentives.
- Proposal:SNIP-35 and SNIP-40 proposed in April and May 2026
- Implementation:Released
- Release:scheduled for mainnet on 2026-07-06
- Activation:described as running on mainnet by L2BEAT at review time
Sources: Starknet Community Forum — Starknet 0.14.3 pre-release notes (external site) · Starknet Community Forum — [SNIP-40] More frequent blocks (external site) · Starknet Community Forum — SNIP 35 - Automatically adjust base fee to STRK price (external site) · L2BEAT — Starknet (external site)
-
AIP 9 proposes shrinking the active validator set to 80
AIP 9 proposed cutting the active validator set from about 105 to 80 by changing the validatorCount staking parameter, to strengthen validator incentives; it says the change is not a runtime upgrade and does not change consensus, slashing or emissions. No transparency report records it being applied. The set was later cut to 10 during the August 2026 outage recovery and then raised in steps; a read of the parameter on 2026-09-29 returned 70.
- Proposal:AIP posted on the forum 2026-05-25
- Implementation:parameter change only; no code needed
- Release:no transparency report for 80 found
- Activation:not confirmed; the set was cut to 10 and then 15 in the outage recovery, and on-chain validatorCount read 70 on 2026-09-29
Sources: Avail Forum — AIP 9: Reduce Mainnet Active Validator Set to 80 (external site) · Avail Project (GitHub governance repository) — Transparency Report 21: Technical Committee Actions During Mainnet Recovery (external site) · OnFinality (Avail-listed public endpoint) — Avail mainnet RPC (OnFinality public endpoint): Staking.ValidatorCount storage read and runtime metadata read (external site) · L2BEAT — Avail data availability (no bridge) (external site)
-
Seneca hard fork cut the active validator set from 80 to 21
PIP Labs released story v1.8.0 (Seneca), a mandatory consensus-client hard fork scheduled for mainnet block 18,173,000 that reduces the number of active validators from 80 to 21 under SIP-00011. The proposal, posted on 30 April 2026, argued that fewer validators cut consensus messaging; validators replying on the forum objected that 21 would concentrate control. Validators outside the top 21 stop earning rewards, and their delegators must redelegate or unbond.
- Proposal:SIP-00011 posted on the forum on 30 April 2026; the thread shows objections from validators and describes no token vote
- Implementation:shipped in story v1.8.0
- Release:mandatory hard-fork release
- Activation:took effect at block 18,173,000, which the official explorer dates to 2 June 2026; the live active-set size was not read
Sources: PIP Labs (GitHub) — Seneca (Story v1.8.0) release notes (external site) · DATA Foundation forum — [Proposal] SIP-00011: Reducing the Active Validator Set from 80 to 21 (external site) · Datanetscan — Block 18,173,000 (Seneca upgrade height) in the Datanetscan API (external site) · PIP Labs (GitHub) — Polybius (Story v1.3.2) release notes (external site)
-
ICON Foundation set 31 December 2026 as the date to halt the ICON chain permanently
The Foundation announced that the ICON Network will shut down on 31 December 2026: the chain will be permanently halted, a read-only archive will be offered for historical lookups, and ICX can no longer be migrated after that date. It said a governance vote would ask validators to approve the shutdown in May 2026, and that migration would become one way from 30 September.
- Proposal:validator governance vote announced for May 2026; result not verified
- Implementation:not yet: blocks were still produced on 29 September 2026
- Release:shutdown date announced
- Activation:planned for 31 December 2026
Sources: ICON Foundation — Final Date Set for SODA Migration, ICON Network to Shut Down End of 2026 (external site) · ICON Foundation — ICX to SODA Migration Update: Two-Way Migration Closes Friday, September 25 (external site) · ICON public API endpoint (ctz.solidwallet.io) — ICON mainnet JSON-RPC: icx_getLastBlock (read 29 September 2026) (external site)
-
Osmosis cut its active validator set to 70
Governance proposal 1017 lowered the maximum number of active validators from 100 to 70, removing the lowest-staked validators. The proposal cited more efficient network communication, lower hardware demands and faster block production. It follows earlier cuts to 120 in February 2025 and 100 in September 2025.
- Proposal:proposal 1017 passed
- Implementation:parameter change
- Release:no software release needed
- Activation:active; cap of 70 observed on 2026-09-27
Sources: Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 1017: Reduce Validator Set to 70 (on-chain record) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis staking module parameters (on-chain query) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis bonded validator count (on-chain query) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis governance proposals, newest 200 (on-chain query) (external site)
-
Foundation plans Qtum to Ethereum bridge and bridged USDC
The Qtum Foundation said its Ethereum bridge, a MetaMask Snap and Circle's bridged USDC contracts were audited and expected to launch in summer 2026, with a third-party exchange and other apps to follow later in the year.
- Proposal:Announced
- Implementation:code and audits described by the foundation
- Release:expected summer 2026
- Activation:not confirmed at review
Sources: Qtum Blog — Qtum Development Updates for 2026 (external site) · Qtum project — Qtum Bridge (bridge-core README) (external site) · qtum.info — qtum.info token page: Bridged USDC (USDC.e) (external site)
-
Two-year window to claim legacy layer-1 LSK closes
The window to claim LSK from the retired Lisk layer 1 on the new network closed on 21 May 2026, two years after the snapshot at height 24,823,618. Lisk says unclaimed tokens went to the Lisk DAO treasury and that late claims or reimbursements are not possible; historical data stays readable through the legacy chain service.
- Implementation:claim window ended as set in the April 2024 announcement
- Release:no release involved
- Activation:closed on 2026-05-21
Sources: Lisk Support — Legacy L1 LSK (FAQ) (external site) · Lisk, via the Internet Archive — LSK Token Migration Snapshot Height Announcement (archived copy) (external site) · Lisk Documentation (Onchain Foundation) — Legacy Chain Service (external site) · Lisk Support — DAO Cessation (FAQ) (external site)
-
Chia 2.7.1 security release published
Protocol/reference-client release: Chia Network urged immediate installation of 2.7.1 as the next security-hardening release after 2.6.x and 2.7.0. The publisher reported no known mainnet exploitation at publication; this is an attributed statement, not independent incident verification.
- Claim:Released
Sources: Chia Network Inc. — Chia 2.7.1 is Out, Upgrade Now (external site) · Chia Network Inc. — chia-blockchain 2.7.1 release (external site)
-
Release v0.73 turned on the simple fee model and high-volume entity creation on Hedera mainnet
Hedera's release notes record v0.73 on mainnet on 20 May 2026, after testnet on 29 April 2026, and say the release enables HIP-1261 simple fees and HIP-1313 high-volume entity creation on mainnet. Simple fees price each transaction as a base fee plus extras, split into node, network and service parts. The high-volume option lets entity-creation transactions go above the standard throttle in exchange for a congestion multiplier of up to four times.
- Proposal:HIP-1261 simple fees Final
- Implementation:included in release v0.73
- Release:released; testnet 2026-04-29, mainnet 2026-05-20
- Activation:enabled on mainnet according to the release notes
Sources: Hedera documentation — Consensus node release notes (external site) · Hiero improvement proposals — HIP-1261: Simple fees (external site) · Hedera documentation — Fee model (external site)
-
initiad v1.4.7 made nodes back off from re-sending pending transactions
Initia Labs published L1 node software v1.4.7 on 2026-05-20. Its one listed change moves the node to Initia's CometBFT fork v0.38.21-initia.4, which adds a time-limited gossip history to the mempool. A pending transaction that a node keeps re-sending to peers now waits longer between attempts, and a transaction the node has just removed is not taken back in straight away. The same fix shipped that day in the v1.5.0-alpha.2 pre-release.
- Implementation:merged in the CometBFT fork (pull request 94) and backported to the v1.4 release line
- Release:released 2026-05-20 as v1.4.7 (not a pre-release); also in pre-release v1.5.0-alpha.2
- Activation:takes effect per node once installed; no network-wide activation height named
Sources: initia-labs on GitHub — Release v1.4.7 (external site) · initia-labs on GitHub — Initia CometBFT fork release v0.38.21-initia.4 (external site) · initia-labs on GitHub — feat(mempool): add ttl gossip history to guard outbound flow (external site) · initia-labs on GitHub — Release v1.5.0-alpha.2 (pre-release) (external site) · initia-labs on GitHub — initia releases feed (external site)
-
Next node release V29 'Piotric' described; development builds continue
The Nano Foundation described the next node release, V29 Piotric: startup checks that compare representative weights and balances with the ledger and stop the node on a mismatch, a backlog limit that rises during bootstrap to undo a sync slowdown caused by V28's bounded backlog, a reworked election scheduler and vote replier, topology indexing groundwork, and new operator commands including a ledger rollback option. Automated development builds of V29.0 were tagged on GitHub through 26 September 2026, and the docs list 29.0 as the next planned release with no date.
- Proposal:described by the Nano Foundation as the next node release
- Implementation:in development; automated development builds tagged through V29.0DB94 (2026-09-26)
- Release:not released; the docs list 29.0 as next planned release with date TBD
- Activation:not activated; no activation announced
Sources: Nano Foundation (Nano Blog) — Nano Ecosystem Round Up of 2026 So Far (external site) · Nano Foundation (GitHub) — nano-node releases Atom feed (external site) · Nano Documentation (Nano Foundation) — Node Releases (external site)
-
Address balances and gasless stablecoin transfers shipped for Sui mainnet
Node release mainnet-v1.72.2 added address balances, a per-address balance for each coin type alongside coin objects, and gasless transfers for seven allowlisted stablecoins (USDC, USDsui, suiUSDe, USDY, FDUSD, AUSD and USDB) with a 0.01 minimum. The Sui Foundation announced the transfers as rolling out on mainnet the same day.
- Proposal:SIP-58 (address balances)
- Implementation:implemented in node v1.72.2
- Release:mainnet-v1.72.2 released 2026-05-20
- Activation:announced as rolling out on mainnet on 2026-05-20; exact activation epoch not verified
Sources: MystenLabs/sui repository — mainnet-v1.72.2 (external site) · Sui Foundation blog — Sui launches gasless stablecoin transfers (external site) · Sui Documentation — Gasless stablecoin transfers (external site) · Sui Documentation — Address balances (external site)
-
A vault was drained through a signing-library flaw, and the network halted
THORChain's first exploit report describes how, on 15 May 2026, a node that had churned in two days earlier rebuilt one vault's key through flaws in the GG20 signing library and drained about 10.7 million US dollars (the second report says about 10 million). Automatic solvency halts and node votes stopped trading, signing, chain observation and churn within hours; the other four vaults were unaffected.
- Implementation:halt applied; library patched in later releases
- Release:exploit reports published 20 May, 3 July and 6 August 2026
- Activation:trading resumed around 22 June 2026 per THORChain's June network report
Sources: THORChain blog — THORChain Exploit Report #1 (external site) · THORChain blog — THORChain Exploit Report #2 (external site) · THORChain blog (prepared by THORSec) — THORChain Exploit Report #3 (external site) · THORChain Dev Docs — ADR 028: Exploit Conciliation (external site) · THORChain blog — State of the Network - June 2026 (external site)
-
Draft proposals to replace World Chain's permissioned fault proofs
WIP-1005 and WIP-1006 propose moving from the permissioned fault-proof game to a design with a one-day challenge window, three proof lanes (validity proof, trusted hardware and Security Council) and WLD-denominated bonds. A pre-release of proof components followed on 25 August 2026, and further release-candidate tags followed, the latest being rc.4 on 13 September 2026. None of these is a final release or a mainnet activation.
- Proposal:Draft
- Implementation:proof components at release-candidate stage: rc.1 pre-release published 2026-08-25; latest tag rc.4 on 2026-09-13
- Release:release candidates only; no final proofs v1.0.0 release in the repository's release feed at review time
- Activation:not active
Sources: Worldcoin on GitHub — WIP-1005: Proof System Upgrade (external site) · Worldcoin on GitHub — WIP-1006: Proof System Architecture (external site) · Worldcoin on GitHub — Releases: worldcoin/world-chain (external site) · Worldcoin on GitHub — Proofs v1.0.0-rc.4 (external site) · L2BEAT — World Chain (external site)
-
conflux-rust v3.0.3-fix security release
A node release fixing a possible crash (panic) under certain circumstances; the release notes strongly recommend that operators upgrade. It is not described as a hard fork.
- Implementation:Released
- Release:v3.0.3-fix published 2026-05-19
- Activation:not a consensus change
Sources: Conflux developers (Conflux-Chain) — conflux-rust v3.0.3-fix (external site) · Conflux developers (Conflux-Chain) — conflux-rust releases (external site)
-
Evmos governance passes proposal 331 to shut the chain down
Proposal 331, titled Evmos shutdown, was submitted as a software-upgrade proposal and passed with about 99.98% of the voting stake in favour. It set nodes to halt at height 37,318,000, around 18 May 2026, and carried the messages of proposal 330, which had failed to execute.
- Proposal:Passed
- Implementation:halt height set in the approved upgrade plan
- Release:no new release published in the evmos/evmos repository
- Activation:chain halted around 18 May 2026; registry marks it killed
Sources: Stakeflow — Evmos Proposal #331: Evmos shutdown (external site) · Stakeflow — Evmos Proposal #330: Restore IBC connection with osmosis & IBC transfer (external site) · Cosmos chain-registry maintainers — chore(evmos): mark chain status as killed (#7710) (external site) · ChainCatcher — The Cosmos ecosystem Evmos network has been shut down (external site)
-
Manta ends rewards for the MANTA staking program behind Manta Pacific's fast-finality design
Manta's staking pages now say the Manta Staking program is being sunset and that staking rewards stopped on 20 May 2026. The program let MANTA holders delegate to operators running Manta's Symbiotic finality-provider software, one half of a design in which staked MANTA and BTC back signatures on Manta Pacific state roots to shorten withdrawal waits. Operators may shut down their nodes, and delegators can unstake through the staking dashboard. Manta's docs history shows operator setup guides added from October 2025.
- Implementation:sunset notice added to the staking docs on 14 May 2026
- Release:not a software release
- Activation:rewards stopped on 20 May 2026, per the notice
Sources: Manta Network Documentation — Staking Overview (with sunsetting notice) (external site) · Manta Network Documentation — Staking FAQs (external site) · Manta Network (GitHub, Manta-Network/docs) — Update atlantic staking docs (#343) (external site) · Manta Network (GitHub) — Recent commits to Manta-Network/docs (Atom feed) (external site) · L2BEAT — Manta Pacific (external site)
-
Osmosis v31.0.3 updated CometBFT to v0.38.23 with vote, sync and light-client fixes
Osmosis v31.0.3 was released on 14 May 2026 and was still the newest tagged Osmosis release on 27 September 2026. Its notes list only a CometBFT update, and the dependency file at that tag pins CometBFT v0.38.23. The CometBFT v0.38.23 notes, published 8 May 2026, fix the handling of empty (nil) votes, stop a peer from feeding a syncing node a false maximum height, correct when the light client stops comparing witnesses and remove a crash path in the ABCI socket server's error recovery.
- Implementation:CometBFT v0.38.23 included in Osmosis v31.0.3
- Release:released 2026-05-14
- Activation:takes effect on each node when its operator installs it; how many validators run it was not checked
Sources: Osmosis maintainers — Osmosis v31.0.3 release (external site) · Osmosis maintainers — Osmosis v31.0.3 go.mod (external site) · CometBFT maintainers — CometBFT v0.38.23 release (external site) · Osmosis maintainers — Release notes from osmosis (Atom feed) (external site) · Osmosis on-chain state via Osmosis public REST endpoint — Osmosis proposal 1044: Alloyed BTC: Restore backing after the nBTC incident (on-chain record) (external site)
-
Sonic introduced NorthStar session runtimes
Sonic described NorthStar as a session-based scaling protocol that lets an app open a short-lived dedicated runtime for traffic peaks and close it afterwards.
- Implementation:devnet per project docs
- Release:Announced
- Activation:not on mainnet
Sources: Sonic SVM — Intro to NorthStar (external site) · Sonic SVM — NorthStar documentation (external site)
-
Ledger Wallet added native Aleo support with private sends
Aleo announced, and Ledger confirmed on 18 May 2026, that Ledger Wallet desktop supports ALEO natively. Users install the Aleo app on the device, approve sharing a view key so the app can show the private balance, and send from either a public balance or a private record with confirmation on the device.
- Implementation:available in Ledger Wallet desktop 4.2.0 or later
- Release:announced by Aleo 2026-05-13 and by Ledger 2026-05-18
- Activation:available at announcement per Ledger; not tested in this review
Sources: Aleo — Aleo + Ledger: Shielded transactions, hardware-secured keys (external site) · Ledger — New in Ledger Wallet: Secure Private Transactions with Aleo (external site)
-
Emergency runtime upgrade rejects wrapped bridge sends
The Technical Committee used its emergency path to apply a runtime upgrade that rejects Avail-to-Ethereum bridge sends wrapped inside proxy, multisig, scheduler or batch calls, after finding that such wrappers could produce bridge data for a send that did not execute or leave funds stuck. Direct bridge sends keep working. A related fault in March 2025 had caused losses for bridge sends made through multisig or proxy calls.
- Implementation:runtime upgrade changing bridge transaction validation
- Release:executed through the emergency proposal path
- Activation:applied at block 2,920,735 per the report
Sources: Avail Forum — Transparency Report 20: Avail Bridge Wrapped Transaction Safety Fix (external site) · Avail Forum — Transparency Report 16: Critical Runtime Upgrade - Filtering VectorX Bridge transactions (external site) · Avail Docs — Bridge AVAIL between Avail DA and Ethereum (external site) · Avail Docs — Governance on Avail (external site)
-
Ronin mainnet became an Ethereum Layer 2 on the OP Stack
After a planned outage of about 10 hours on 12 May 2026, Ronin mainnet resumed as an OP Stack Layer 2 run by Conduit, with data on EigenDA and RON kept as gas. Validator staking ended, emissions fell to 5 million RON a year for builders, and a new explorer replaced the old one.
- Proposal:OP Stack adoption voted by governing validators in 2025
- Implementation:Completed
- Release:Mainnet
- Activation:active since 12 May 2026
Sources: Ronin blog — Ronin is Home. (external site) · Ronin blog — Ronin is coming home to Ethereum (external site) · Ronin blog — Powering Ronin's Homecoming to Ethereum (external site) · L2BEAT — Ronin (external site)
-
Neutron v11 moved governance to the standard module and added inflation and slashing
Neutron v11.0.0, applied at height 56277000 around 13 May 2026, replaced contract-based DAO voting with the standard Cosmos governance module, added minting and distribution modules, set slashing penalties and removed the fee-burning and revenue modules. Because token voting had not reached quorum since 1 April 2026, the upgrade height was submitted by the DAO-elected privileged multisig.
- Proposal:scheduled by the DAO-elected privileged multisig because token voting lacked quorum
- Implementation:released as v11.0.0
- Release:released 2026-05-12
- Activation:applied at height 56277000
Sources: Neutron contributors — Neutron v11.0.0 release (external site) · Neutron contributors (mainnet-assets) — Neutron v11.0.0 Upgrade, Instructions (external site) · Neutron contributors — v11.0.0 upgrade handler source (external site) · Solva public REST endpoint for neutron-1 — Applied upgrade plan v11.0.0 (on-chain query) (external site) · Solva (solva-solutions/neutron-wasmd) — CosmWasm module authorization policy (Neutron wasmd fork, v0.61.14-neutron) (external site)
-
Blockstream publishes Liquid roadmap with post-quantum work and BitVM bridge research
The roadmap lists planned and research items: a hard fork allowing issued assets other than L-BTC above the 21 million limit, targeting a late May 2026 activation window; fees paid in assets other than L-BTC, under review by the federation's technology board; an optional user-pays peg-in policy, merged and available in a release candidate; cheaper Taproot sweeps of the peg's bitcoin targeted for 2027; staged post-quantum readiness; and a BitVM-style bridge with lower trust assumptions as a research track.
- Proposal:roadmap items at different stages
- Implementation:varies by item
- Release:most items not released at publication
- Activation:not confirmed for any consensus change in this review
Sources: The Liquid Blog — Blockstream Shares Liquid Development Roadmap: 0-Conf, PQ Readiness, BitVM & More (external site) · ElementsProject (GitHub) — elements-23.3.4 (external site)
-
Monero v0.18.5.0 released
The recommended reference-client release added SOCKS v5 support to the daemon and wallet, removed daemon UPnP support, restricted sensitive ZMQ and wallet-RPC methods, and included bug fixes. This is client-release evidence, not a consensus activation claim.
- Stage:Stable release
- Activation:Not claimed
Sources: Monero community — Monero 0.18.5.0 'Fluorine Fermi' released (external site) · The Monero Project contributors — Monero v0.18.5.0 release (external site)
-
Custom transaction unlock time deprecation announced
The project announced that custom transaction unlock time was planned for consensus deprecation with a future FCMP++ fork; the post said no fork date was set. A relay rule already prevented those transactions from entering ordinary node mempools, but that operational rule is not proof that the planned consensus deprecation had activated.
- Stage:Proposal
- Activation:Not activated
Source: Monero community — Deprecating Monero's Custom Transaction Unlock Time (external site)
-
Renter-host protocol gained shared account pools
core v0.21.0 added pool RPCs to the renter-host protocol, letting a renter fund one shared pool that many accounts draw on, so each account need not be funded separately. hostd v2.9.0 (2026-06-03) added host-side support, and indexd v0.3.0 (2026-06-30) switched apps to one pool per connect key. This is a change to the off-chain protocol between renters and hosts, not to consensus.
- Implementation:shipped in core v0.21.0, hostd v2.9.0 and indexd v0.3.0
- Release:Released
- Activation:available when both the renter's and the host's software support it; no network activation
Sources: Sia Foundation (GitHub) — core v0.21.0 release notes (external site) · Sia Foundation (GitHub) — hostd v2.9.0 release notes (external site) · Sia Foundation (GitHub) — indexd v0.3.0 release notes (external site) · Sia Foundation (GitHub) — core CHANGELOG (external site) · Sia Foundation blog — The State of Sia, May 2026 (external site)
-
Node guide raises non-validator memory to 128 GB
The official node guide changed the stated machine specification for non-validating nodes from 64 GB to 128 GB of RAM, matching validators. The CPU (16 vCPUs) and storage (500 GB SSD) figures did not change.
- Implementation:documentation change
- Release:published in the node guide
- Activation:guidance in effect from 9 May 2026
Sources: hyperliquid-dex (GitHub) — node commit f256f31: update spec (external site) · hyperliquid-dex (GitHub) — hyperliquid-dex/node: Running a node (external site)