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 7 of 14.
One chain's developments, A to Z
-
Beam disclosed an emergency hard fork fixing a range-proof flaw
Beam disclosed that an emergency hard fork at block 3,928,666 fixed a flaw in its Bulletproofs range proofs that could in theory have let someone create outputs with negative amounts and inflate the supply. Developers said a scan of the chain's history found no such pattern, and they assessed exploitation as unlikely.
- Implementation:fix shipped in the emergency-hf6 pre-release and hotfix release 7.5.14493
- Release:emergency-hf6 pre-release published 2026-06-30; 7.5.14493 published 2026-07-01
- Activation:active at block 3,928,666 per Beam; activation date not stated
Sources: Beam blog — Hard Fork Six (external site) · BeamMW — Emergency network upgrade (emergency-hf6) release notes (external site) · BeamMW — HOTFIX - Groovy Gluon 7.5.14493 release notes (external site) · BeamMW — Beam node and wallet releases (external site)
-
Casper node 2.2.2 security release active on mainnet after the 2.2.1 fix
Casper published node 2.2.1 on 2026-05-26, which rejects transactions initiated by the system account, and 2.2.2 on 2026-07-01, described only as a security release. The 2.2.2 mainnet chainspec activates at era 22931, and the Casper Association's public node reported protocol 2.2.2 on 2026-09-29.
- Implementation:casper-node v2.2.1 and v2.2.2
- Release:released 2026-05-26 and 2026-07-01
- Activation:2.2.2 active: activation era 22931 in the chainspec, and a public node reported protocol 2.2.2 on 2026-09-29
Sources: Casper Network (GitHub) — casper-node v2.2.1 release notes (external site) · Casper Network (GitHub) — casper-node v2.2.2 release notes (external site) · Casper Network (casper-node repository, GitHub) — Casper mainnet chainspec, protocol version 2.2.2 (external site) · Casper Association — Casper Association public mainnet node, JSON-RPC info_get_status (read 2026-09-29) (external site) · Casper Network (GitHub) — casper-node releases Atom feed (external site)
-
v9 upgrade cut Celestia's block time to about 3 seconds
The v9 upgrade activated at height 11,771,699. It carries CIP-048, which lowers the block time target from about 6 seconds to about 3 seconds by shortening consensus timeouts, and rescales block-count settings such as the evidence window so their real-time durations stay the same.
- Proposal:CIP-050 and CIP-048 marked Draft in the CIP repository
- Implementation:released in celestia-app v9; Mainnet Beta page lists v9.0.8
- Release:activated on Mainnet Beta
- Activation:active from height 11,771,699
Sources: Celestia Docs — Network upgrades (external site) · Celestia Improvement Proposals — CIP-050: v9 Network Upgrade (external site) · Celestia Improvement Proposals — CIP-048: Lower block time to 3 seconds (external site) · Celestia Docs — Mainnet Beta (external site) · celestiaorg — celestia-app v9.0.8 (external site)
-
Dash Core 23.1.7 hardens nodes against denial-of-service from peers
Dash Core 23.1.7 is a patch release focused on how nodes handle traffic from other peers. It stopped a network thread from running at full CPU when receive buffers back up, limited quorum key-generation messages to verified masternodes and checked their size and structure, fixed a null-pointer crash in BLS share verification, rejected oversized InstantSend input sets early and validated governance vote-sync requests. It also fixed builds on newer compilers. The developers said the issues do not affect consensus or put funds at risk.
- Implementation:shipped in Dash Core 23.1.7
- Release:stable patch release published 2026-07-01; superseded by 23.1.8 on 2026-08-03
- Activation:no consensus change; takes effect on each node as it upgrades
Sources: Dash Core developers (dashpay) — Dash Core 23.1.7 release announcement (external site) · Dash Core developers (dashpay) — Dash Core v23.1.7 release notes (external site)
-
Near One described work toward a Wasmtime contract runtime
Near One published work on replacing NEAR's contract VM with Wasmtime. The article is relevant research but alone does not establish protocol activation or mainnet availability.
- Implementation:Research and development
- Release:Not established
- Activation:Not established
Source: Near One — Replacing NEAR's Contract VM with Wasmtime (external site)
-
Robinhood announced public mainnet launch
Robinhood's July 1 newsroom post says the public mainnet was officially launching; the same-day Arbitrum post says mainnet was live on the Arbitrum Platform. The later Robinhood page update date is preserved separately and is not substituted for launch date.
- Type:Launch
- Proposal:Completed announcement
- Release:Public mainnet announced live
- Activation:Announced active by two first party sources
Sources: Robinhood — Robinhood Accelerates Global Expansion with Robinhood Chain Mainnet, Stock Tokens, Agentic Trading and New Suite of DeFi Products (external site) · Arbitrum — Robinhood Chain mainnet is live, built with the Arbitrum Platform (external site)
-
Chia Network announced BuyXCH personal spending limits
CNI product announcement, not a consensus change: Chia Network announced personal spending-limit updates for BuyXCH. This record does not establish current product availability, regional eligibility, pricing or transaction status.
- Claim:Announced
Source: Chia Network Inc. — BuyXCH Personal Limits (external site)
-
dYdX Labs launched Arcus on Robinhood Chain and said dYdX v4 stays supported
dYdX announced Arcus, a decentralized exchange built jointly by dYdX Labs and Robinhood Crypto that runs on Robinhood Chain, which the post describes as an EVM-compatible Layer 2 built by Robinhood. The post said spot trading was live and opened a waitlist for perpetuals. It also said dYdX v4 will continue to be supported and that funds and positions remain accessible on dYdX Chain.
- Implementation:Arcus described as launched in the announcement
- Release:launched per the announcement: spot trading live, perpetuals on a waitlist
- Activation:not a dYdX Chain protocol change
Source: dYdX — A new arc (external site)
-
Draft ECIP-1130 proposes the Bastion EVM upgrade
Diego López León and Istora Mandiri opened ECIP-1130, a draft hard fork named Bastion. It would add transient storage opcodes, MCOPY, BLS12-381 and secp256r1 precompiles, a CLZ opcode, bounds and new pricing for MODEXP, and narrower SELFDESTRUCT behaviour. It leaves fees unchanged, defers account-code delegation and a per-transaction gas cap, and sets no activation block.
- Proposal:Draft ECIP
- Implementation:reference implementations still to be linked
- Release:not in any release reviewed here
- Activation:no activation block on Mordor or mainnet
Sources: Ethereum Classic Improvement Proposals — ECIP-1130: Bastion EVM and Protocol Upgrades (external site) · Ethereum Classic Improvement Proposals (GitHub) — ECIPs repository (external site)
-
Toccata hard fork activated on Kaspa mainnet
The Toccata upgrade activated at DAA score 474,165,565, adding covenants, covenant IDs, zero-knowledge proof verification in script and per-application sequencing commitments (KIPs 16, 17, 20 and 21). The default minimum relay fee rose from 1 to 100 sompi per gram.
- Proposal:KIPs 16, 17, 20 and 21 marked Active
- Implementation:implemented in Rusty Kaspa v2.0.0 and v2.0.1
- Release:released 2026-06-05 (v2.0.0) and 2026-06-15 (v2.0.1)
- Activation:active on mainnet since 2026-06-30
Sources: Kaspa (kaspa.org) — Developments (external site) · Kaspa developers (kaspanet) — Mainnet Toccata Release - v2.0.0 (external site) · Kaspa developers (kaspanet) — Mainnet Toccata Release - v2.0.1 (external site) · Kaspa developers (kaspanet) — Kaspa Toccata Hardfork Node Setup Guide (external site) · Kaspa Docs (kaspanet) — Toccata Dev Guide (external site)
-
Sia Storage mobile app launched on iOS and Android
The Foundation's May 2026 recap reports that the Sia Storage mobile app launched for iOS and Android at Consensus Miami, with a free storage allowance. The app encrypts and erasure-codes data on the device and uses the Sia Storage hosted indexer to manage contracts with hosts.
- Implementation:apps released
- Release:launched on iOS and Android per the Foundation's recap
- Activation:available per the Foundation; not tested in this review
Sources: Sia Foundation blog — The State of Sia, May 2026 (external site) · The Sia Storage Company — Sia Storage (external site) · Sia Foundation (Sia Docs) — About Storing Data on Sia (external site)
-
MainNet moves to Canton protocol version 35 with a Logical Synchronizer Upgrade
Canton announced that Logical Synchronizer Upgrades are live on MainNet with Canton 3.5: the upgraded synchronizer runs in parallel and the switch completes in seconds or minutes. The Foundation's schedule set the MainNet upgrade from protocol version 34 to 35 for 27 June 2026, with party onboarding and other topology changes paused for the preceding 24 hours.
- Implementation:shipped in Canton 3.5
- Release:released; minimum Splice 0.6.5 for validators
- Activation:MainNet upgrade scheduled for 2026-06-27 13:00 UTC; Canton's 29 June post says the upgrades are live on MainNet
Sources: Canton Network Blog — Canton Network Goes Live with Logical Synchronizer Upgrades (external site) · Canton Network Forum (Announcements) — Canton 3.4 to canton 3.5 transition (external site)
-
Native USDC, EURC and CCTP went live on Cronos
Cronos announced that Circle-issued USDC and EURC and Circle's CCTP were live on Cronos EVM. Circle's own pages list the Cronos USDC and EURC contracts and list Cronos as CCTP domain 32. Cronos says bridged USDC (USDC.e) keeps working during a transition in which the ecosystem moves liquidity to native USDC.
- Implementation:contracts deployed and listed by Circle
- Release:announced live 2026-06-29
- Activation:active as of this review
Sources: Cronos — Native USDC, EURC, and CCTP Are Live on Cronos (external site) · Circle — USDC contract addresses (external site) · Circle — EURC contract addresses (external site) · Circle — CCTP supported chains and domains (external site)
-
Loopring's exchange contract was replaced with an admin-only executor
The Loopring multisig upgraded the exchange proxy on Ethereum to new code whose only function lets the proxy owner make arbitrary calls from the exchange, including sending its assets. Normal operation stopped, and the forced-withdrawal and Merkle-proof exits in the old code no longer exist. L2BEAT archived the project at the same time.
- Implementation:upgrade executed on Ethereum; replacement code verified on Sourcify
- Release:admin executor contract
- Activation:active since 29 June 2026
Sources: L2BEAT — Loopring (external site) · L2BEAT (GitHub) — Loopring project configuration (external site) · L2BEAT (GitHub) — Loopring contract diff history (external site) · Sourcify — ProxyAdminExecutor verified source (29 June 2026 version) (external site) · Etherscan — Loopring: Exchange v2 (external site)
-
NEP-645 proposed post-quantum transaction access keys
NEP-645 documents ML-DSA transaction authorization, says Draft, and states stabilization at protocol version 85 in neard 2.13. Its scope excludes validator/block signing and implicit-account derivation. Mainnet protocol 86 was observed later, but no ML-DSA transaction was exercised by this review.
- Proposal:Draft at review
- Implementation:stated-stable-at-protocol-85-and-shipped-in-neard-2.13
- Release:Released code
- Activation:inferred-available-from-mainnet-protocol-86-observation; not transaction-tested
Sources: NEAR NEPs — NEP-645: Post-Quantum Transactions (external site) · NEAR nearcore — nearcore 2.13.0 (external site)
-
Ushuaia upgrade activated: larger data-availability bandwidth
Ushuaia, the 21st Tezos protocol upgrade, activated at block 13,857,889. It raised Data Availability Layer bandwidth from about 0.66 MB/s to 10 MB/s, made the data attestation delay dynamic (about 2 to 3 blocks instead of 11), and let rollup-specific virtual-machine upgrades activate through the rollup's own governance instead of a full layer 1 amendment cycle. Enshrined liquid staking and post-quantum tz5 accounts shipped disabled, for test networks only.
- Proposal:adopted by on-chain vote
- Implementation:implemented in Octez v25
- Release:Released
- Activation:active on mainnet since 2026-06-30 UTC; two features remain disabled on mainnet
Sources: Nomadic Labs on Tezos Spotlight — 15x Bandwidth, Better Rollup Governance: Ushuaia is Live! (external site) · Tezos documentation (docs.tezos.com) — History of amendments (external site) · Octez and Tezos protocol documentation — Version 25 release notes (external site)
-
Loopring announced the shutdown of its layer-2 exchange
Loopring announced that its exchange was being sunset. L2BEAT summarizes the post as saying the exchange no longer accepts deposits and that deposited tokens will be transferred to users. Loopring's website now states that Loopring is no longer operational.
- Proposal:announced by Loopring; no governance vote described in the reviewed sources
- Implementation:exchange contract replaced on 29 June 2026
- Release:no software release; a shutdown
- Activation:in effect; loopring.org says Loopring is no longer operational
Sources: L2BEAT — Loopring (external site) · Loopring — Loopring Has Shut Down (external site)
-
Base published remediation for the June 25–26 block-production outages
Base reported two complete block-production halts lasting 116 minutes and 20 minutes. Its postmortem attributes both to stale execution journal state after transaction validation failure, records a sequencer patch and recovery, and separately identifies an engine-reset race that contributed to the recurrence.
- Type:Release
- Proposal:Not applicable
- Release:Sequencer remediation deployed
- Activation:Incidents resolved 2026 06 26
Source: Base Engineering Team — Postmortem: June 25th Block Production Outage (external site)
-
Gaia v27.5.0 released
Gaia v27.5.0 updated its ibc-go dependency from v10.6.0 to v10.7.0.
- Release:Released
- Activation:not inferred from release alone
Source: cosmos/gaia maintainers — Gaia v27.5.0 release notes (external site)
-
Lisk node v0.4.21 makes the Karst network upgrade mandatory for Lisk Mainnet
Lisk's node release v0.4.21 moved to op-node v1.19.1 and op-reth v2.3.2, the mandatory clients carrying the Karst activation time for Lisk Mainnet, 8 July 2026 at 16:00:01 UTC, pending governance approval. Release v0.4.22 followed on 29 June with op-reth v2.3.3 to fix gas estimation after Karst. The Superchain Registry's Lisk configuration lists the same Karst time.
- Proposal:pending governance approval when the release was published
- Implementation:shipped in lisk-node v0.4.21 and v0.4.22
- Release:mandatory node release
- Activation:scheduled for 2026-07-08 16:00:01 UTC in the registry; activation on chain not independently checked
Sources: Lisk (GitHub, LiskHQ/lisk-node) — Lisk node v0.4.21: mandatory upgrade ahead of Karst on Mainnet (external site) · Lisk (GitHub, LiskHQ/lisk-node) — Lisk node releases (external site) · Lisk (GitHub, LiskHQ/lisk-node) — Lisk node releases (Atom feed) (external site) · Optimism (GitHub, ethereum-optimism/superchain-registry) — Superchain Registry: Lisk mainnet configuration (lisk.toml) (external site)
-
Story became the DATA Network and the IP ticker became DATA
The foundation announced that Story is becoming the DATA Foundation, the Story Network the DATA Network and the IP token DATA, one-to-one with no holder action required. It said the rename does not break integrations, the network runs without interruption and the validator set is unchanged, and it moved its stated focus from IP licensing to provenance, processing and licensing of AI training data through Trace, Poseidon and partner apps such as Kled.
- Implementation:names changed on the foundation's site, docs, explorer and RPC addresses; PIP Labs published a wrapped DATA contract described as a rebrand of wrapped IP
- Release:announced 25 June 2026
- Activation:effective at announcement per the foundation; no chain upgrade was announced for it
Sources: The Data Foundation blog — We're becoming The DATA Foundation (external site) · DATA Foundation Docs — Mainnet: network resources (external site) · PIP Labs (GitHub) — WDATA: Wrapped DATA token (external site)
-
Neutron v11.1.0 released with CosmWasm dependency updates, scheduled for height 60580000
Neutron v11.1.0, published on GitHub on 25 June 2026, is marked as a consensus-breaking release that operators must not switch to early. Its listed changes update the CosmWasm virtual machine library (wasmvm, from 3.0.3 to 3.0.5 in the notes) and the wasmd contract module (v0.61.12, then a further update), and its upgrade handler only runs the standard module migrations. The operator notes set a coordinated in-place upgrade at height 60580000, about 1 July 2026 15:00 UTC, and require libwasmvm 3.0.7. It is the last release in the original neutron-org repository, which was later archived.
- Proposal:not stated in the release or upgrade notes; no proposal record was reviewed in this pass
- Implementation:released as v11.1.0 (wasmvm and wasmd updates, standard module migrations)
- Release:released 2026-06-25
- Activation:scheduled for height 60580000, about 2026-07-01 15:00 UTC, per the upgrade notes; on-chain application not checked in this pass
Sources: Neutron contributors — Neutron v11.1.0 release (external site) · Neutron contributors (mainnet-assets) — Neutron v11.1.0 Upgrade, Instructions (external site) · Neutron contributors — v11.1.0 upgrade handler source (external site) · Neutron contributors — neutron-org/neutron releases feed (external site) · Neutron contributors — neutron-org/neutron (archived repository and maintenance notice) (external site)
-
ZAN, Ant Digital Technologies' Web3 brand, joined as an enterprise validator
Theta Labs announced that ZAN, the Web3 brand of Ant Digital Technologies, is running an enterprise validator node and published its validator address. The post lists the other enterprise validators as including Google, Samsung, Sony, CAA, Binance, Deutsche Telekom, Docomo Global and Cloudician.
- Implementation:validator node announced as live
- Release:Announced
- Activation:stake at the announced address observed in a 2026-09-27 explorer read
Sources: Theta Labs blog — ZAN, Ant Digital Technologies' Web3 Brand, Joins Theta Network as Strategic Enterprise Validator (external site) · Theta Labs — Theta Explorer API: all stake records (external site)
-
Cronos v1.7.8 adds an opt-in fix for failing transaction traces
The Cronos node repository published v1.7.8 as a regular release, not a pre-release. It addresses an old gas-accounting bug: when a node replays a transaction that is already on chain for debug_traceTransaction, debug_traceBlock or debug_traceCall, the fee it works out again can differ from the fee first charged, and the trace then fails. The release adds an optional traceReplay setting to the trace configuration. When it is set and the upfront fee deduction fails, the node logs a warning and finishes the trace without charging the fee. The setting is off by default.
- Implementation:opt-in traceReplay setting for debug trace calls, off by default
- Release:v1.7.8 published 2026-06-24, not marked pre-release
- Activation:no network-wide activation named; applies on nodes that install it and only when a trace call sets traceReplay
Sources: crypto-org-chain/cronos maintainers — Cronos v1.7.8 release notes (external site) · crypto-org-chain/cronos maintainers — Cronos releases (external site) · crypto-org-chain/cronos maintainers — Cronos releases (Atom feed) (external site)
-
initiad v1.4.8 stopped transactions that panic during pre-checks from crashing nodes
Initia Labs published v1.4.8 on 2026-06-23. Its single commit wraps the transaction pre-checks (the ante handler) in panic recovery where they run outside the SDK's usual protection: the background mempool cleanup worker and the block proposal handlers. The code comments say a transaction that panicked there, for example one with a fee amount larger than a 64-bit integer, would crash the node; now it is dropped or rejected instead.
- Implementation:one commit (4441618) on the release/v1.4.x branch
- Release:released 2026-06-23 as v1.4.8 (not a pre-release)
- Activation:takes effect per node once installed; a team-run node reported v1.4.8 on 2026-09-27
Sources: initia-labs on GitHub — Release v1.4.8 (external site) · initia-labs on GitHub — Commit 4441618: wrap full ante with recover() (external site) · initia-labs on GitHub — initia releases feed (external site) · Initia Labs public REST endpoint — Live node info (initiad and CometBFT versions) (external site)
-
Fantom Opera's shutdown postponed to at least the end of 2026
On 7 April 2026 Sonic Labs said validator migration was complete and set Fantom Opera's retirement for 5:00 PM GMT on 30 June 2026, after which the Opera FTM to S bridge would close; the route for FTM held as a token on Ethereum was not affected. On 23 June 2026, alongside a leadership change that made Matt Visser chief executive, Sonic Labs said Opera would stay live until at least the end of 2026, that the bridge would be funded regularly for that period, and that any change would come with plenty of notice.
- Implementation:retirement postponed
- Release:Announced
- Activation:Opera to stay live until at least the end of 2026, per Sonic Labs
Sources: Sonic Labs blog — The First 1% (external site) · Sonic Labs blog — Sonic's Successful Network Migration: What This Means for Fantom Opera (external site) · Sonic Labs blog — Leadership update from Sonic Labs (external site)
-
Neutron entered long-term maintenance mode
Governance proposal 1, submitted 22 June and passed 29 June 2026, said Neutron was entering long-term maintenance. It cut the active validator set from 18 to 13, retuned minting for a block interval of about 7 seconds instead of 1, and lowered the minimum deposit ratio for proposals. Hadron Labs' engagement ended on 30 June; on the same day the Neutron account said foundation-supported front ends were deprecated and published a command-line withdrawal guide.
- Proposal:proposal 1 passed 2026-06-29
- Implementation:parameter changes executed on passage
- Release:not a software release
- Activation:maintenance mode from 2026-07-01
Sources: Neutron on-chain governance (via Solva REST endpoint) — Governance proposal 1: Governance, staking and mint parameters updates + Fund community pool (external site) · Neutron on X — Full Guide: Using CLI to Withdraw Funds From Neutron Applications (X syndication record) (external site) · Neutron contributors — Neutron v11.0.0 release (external site) · Solva — Proposal: Neutron Long-Term Security Maintenance Mandate and 12-Month Funding (external site)
-
Dash Core 23.1.5 corrects a wrong mainnet checkpoint shipped in 23.1.4
Dash Core 23.1.5 came out one day after 23.1.4 to fix a single mistake: the built-in mainnet checkpoint for block 2,487,500. A checkpoint is a block hash written into the node software that the node expects to find at a given height. According to the fix, 23.1.4 had stored the chain's minimum-work figure in that slot instead of the block's hash. The release notes list no other functional change and describe the upgrade as optional for all nodes, although recommended.
- Implementation:fix merged 2026-06-19 (dash#7368) and shipped in Dash Core 23.1.5
- Release:stable patch release published 2026-06-20; later superseded by 23.1.7 and 23.1.8
- Activation:no network activation; takes effect on each node as it upgrades
Sources: Dash Core developers (dashpay) — Dash Core v23.1.5 release (external site) · Dash Core developers (dashpay) — Dash Core v23.1.5 release notes (external site) · Dash Core developers (dashpay) — fix: correct v23.1.4 checkpoint hash (dash#7368) (external site) · Dash Core developers (dashpay) — Dash Core releases (Atom feed) (external site)
-
Core team reported the June 10 Axelar bridge contract exploit
SCRT Labs reported that on 10 June 2026 an attacker exploited the Secret-side contract for the Axelar bridge, minting roughly 4.67 million US dollars of unbacked bridged tokens from a counterfeit chain and redeeming them for real reserves on the Axelar side. Bridging through Axelar was disabled and the connection paused.
- Implementation:bridge route disabled and connection paused
- Release:incident report published
- Activation:remediation pending at review
-
Beryl is live on Base Mainnet
Beryl was announced on June 18, 2026, and current Base upgrade documentation marks it live on Mainnet on June 25, 2026. The upgrade introduced B20 precompile-based tokens, reduced the single-proof withdrawal finalization window from seven days to five, and shipped Reth V2; the Base v1.1.1 GitHub release instructs node operators to upgrade before the June 25 activation.
- Type:Upgrade
- Proposal:Specified
- Release:required-node-release-v1.1.1
- Activation:Mainnet live observed in current docs
Sources: Base — Beryl Overview (external site) · Base Engineering Team — Introducing Base Beryl (external site) · Base contributors — Base v1.1.1 (external site)
-
Node patch 9.0.3 corrects trace call data and adds default eth_getLogs limits
Rootstock published version 9.0.3 of its node software, RSKj, as an optional patch in the Vetiver line. It fixes incorrect call data reported for internal calls by the trace_transaction and trace_block methods, corrects the commit hash recorded in Docker images and sets default limits on the eth_getLogs method. Rootstock says nodes that rely on the tracing methods should update.
- Implementation:released as RSKj 9.0.3
- Release:optional patch release; update advised for nodes using the tracing methods
- Activation:no network activation; changes apply when an operator installs the release
Sources: Rootstock — Vetiver 9.0.3: Patch Release (external site) · Rootstock (GitHub) — RSK Vetiver Release 9.0.3 (external site) · Rootstock (GitHub) — Release notes from rskj (external site)
-
go-flare v1.14.0 (Granite upgrade) schedules a 500 gwei fee floor and a 300M FLR validator cap
The Flare Foundation released go-flare v1.14.0, which moves the node to AvalancheGo v1.14.0 (the Granite upgrade) and schedules its changes for Coston on 11 June, Coston2 on 16 June, Songbird on 7 July and Flare Mainnet on 14 July 2026, each at 12:00 UTC. On Flare it raises the minimum C-chain base fee to 500 gwei, raises the maximum validator stake from 200M to 300M FLR, and sets a 20% minimum delegation fee for validators, previously 0%.
- Proposal:implements parts of FIP.16, accepted on 24 April 2026
- Implementation:shipped in go-flare v1.14.0
- Release:released 17 June 2026; a v1.14.2 release candidate in July schedules no new fork times
- Activation:scheduled for Flare Mainnet on 14 July 2026 at 12:00 UTC; validator stakes above the old cap fit activation, but no block was checked for the fee floor
Sources: Flare Foundation (GitHub) — go-flare v1.14.0 (external site) · Flare Foundation (GitHub) — Release Notes: Flare and Songbird networks (external site) · Flare Developer Hub — Register as Validator (external site) · Flare (flare-api.flare.network) — Flare P-chain API: platform.getCurrentValidators (read 2026-09-29) (external site) · Flare (flare-explorer.flare.network) — Flare Explorer API: network stats (read 2026-09-29) (external site) · Flare Governance Proposals — FIP.16: Restructure FLR Tokenomics for Long-Term Network Sustainability (external site)
-
Move-based account authentication was enabled on IOTA mainnet
Node release v1.25.0 (protocol version 28) enabled Move-based account authentication on mainnet, so an account's authorization can be decided by a Move function instead of a single key. The Foundation's Q2 2026 update described account abstraction as live on mainnet. IOTA's documentation pages still label the feature a testnet and devnet release candidate.
- Proposal:specified in improvement proposal IIP-0009
- Implementation:implemented in node releases during 2026
- Release:mainnet release v1.25.0 published 2026-06-17
- Activation:enabled on mainnet by v1.25.0 according to its release notes; wallet support not reviewed
Sources: iotaledger/iota releases — [Mainnet] v1.25.0 (external site) · iotaledger/iota releases — [Mainnet] v1.32.1 (external site) · IOTA Foundation blog — IOTA & TWIN Progress Update: Q2 2026 (external site) · IOTA Documentation — Account Abstraction (external site) · IOTA Foundation blog — IOTA Q1 2026 Progress Update (external site)
-
Telos released TelosZero Core 1.2.2, its own node software line
Telos announced TelosZero Core 1.2.2, the first node software release maintained by Telos itself, based on Antelope Spring 1.2.2 with selected later fixes, Telos genesis materials and a checksummed Ubuntu package. Telos described it as the first step of Project Lightspeed and said future Telos-specific protocol work, including work toward quantum-safe infrastructure, will be reviewed on its main branch.
- Implementation:released as teloszero-v1.2.2
- Release:production release on the release/1.2-teloszero branch
- Activation:no activation height; took effect as operators upgraded
Sources: Telos blog — Telos Releases TelosZero Core (external site) · Telos Network (GitHub) — TelosZero Core 1.2.2 release (external site) · Telos Docs — Exchange Guide: Updating Your Telos Zero Node Software to the Latest Release (external site)
-
Grin node 5.5.0 fixes parallel sync peer handling
Grin v5.5.0 lists a fix to how the node picks and blocks peers during parallel state sync, and to terminal-interface startup and shutdown. The commit comparison also shows the node's database binding moving to a new library, IPv6 as the default listen address and validation of sync segment indices.
- Implementation:shipped in v5.5.0
- Release:stable release published 2026-06-16
- Activation:no consensus change; takes effect as nodes upgrade
Sources: GitHub API (mimblewimble/grin) — Grin v5.5.0 release record (external site) · GitHub API (mimblewimble/grin) — Grin commits between v5.4.1 and v5.5.0 (external site)
-
Chia Network announced the Permuto Volatility Cup
Ecosystem-project announcement, not a consensus change: Chia Network reported that Permuto launched its statistical-volatility perpetuals production platform on Chia. The announcement does not independently verify continued service availability, eligibility, market claims or project safety.
- Claim:Reported
Source: Chia Network Inc. — Welcome to the Permuto Volatility Cup (external site)
-
Runtime 4401 was released, approved by referendum and activated on 2026-07-13, becoming Moonbeam's last runtime
Moonbeam tagged runtime 4401 on GitHub on 2026-06-15. It set the maximum gas for one EVM transaction to 35 million, made a signed CallPermit count as used even when the call it authorizes fails, began charging EVM gas for P256 signature checks and added a limit on transactions per block. Referendum 155, which authorized the Moonbeam upgrade, is shown as executed. Subscan shows spec 4401 in force by 13:33 UTC on 2026-07-13 and still in force at the final block.
- Proposal:OpenGov Referendum 155 (Root track) opened for voting 2026-06-22 per the forum; Subscan shows it executed, with a call hash matching the release notes
- Implementation:Runtime built for Moonbase Alpha, Moonriver and Moonbeam; node client v0.52.3 named as the minimum version
- Release:Tagged on GitHub 2026-06-15; the Moonbeam upgrade was scheduled for about 13:00 UTC on 2026-07-13
- Activation:Active on Moonbeam by block 16,427,400 (2026-07-13 13:33 UTC) per Subscan, and still the runtime at final block 16,796,696
Sources: Moonbeam Foundation (GitHub) — Runtime runtime-4401 (external site) · Moonbeam Foundation (GitHub) — Moonbeam v0.52.3 (external site) · Moonbeam Community Forum — [Runtime] RT4401 Schedule (external site) · Subscan — Moonbeam referendum 155 (external site) · Subscan — Moonbeam block 16427400 (external site) · Subscan — Moonbeam block 16796696 (external site)
-
DashPay wallet added cross-chain swaps through Maya Protocol
dash.org announced that the DashPay wallet can swap DASH to other assets such as Bitcoin, Ethereum and stablecoins through Maya Protocol, a THORChain fork; Dash says DASH was the first new chain Maya added after its 2023 launch. iOS support was stated as coming. At review, Maya's node API still listed a DASH pool but reported a network-wide chain halt.
- Implementation:integrated in the DashPay Android wallet
- Release:announced live on Android; iOS stated as coming
- Activation:Maya network halted at review; cause not verified
Sources: Dash (dash.org) — DashPay Maya Swaps Now Live (external site) · Maya Protocol — MAYAChain node API: pools (external site) · Maya Protocol — MAYAChain node API: mimir settings (external site)
-
Ravencoin Core 4.7.0 patched an asset transfer overflow bug behind miner signalling
Version 4.7.0 added checks that reject out-of-range asset amounts, closing a bug that the release notes say let anyone holding one unit of an asset create an amount near 2^64. Enforcement needs about 70% of miners to signal readiness; the 4.8.0 notes say that vote had not completed before 4.8.0 was needed. The source was published in August as pull request 1287.
- Implementation:fix published as pull request 1287 on 10 August 2026
- Release:binaries 13 June 2026; GitHub release 14 June 2026; carried into 4.8.0
- Activation:miner signalling window opened 12 June 2026; activation inferred around 14 August 2026, not confirmed
Sources: RavenProject — Ravencoin v4.7.0: Patch the asset transfer qty overflow bug (external site) · RavenProject — V4.8.0 Core Release: Patch 2 major bugs (external site) · RavenProject — Fix the asset transfer qty overflow bug (pull request 1287) (external site) · RavenProject — Ravencoin Core consensus/tx_verify.cpp: asset input and output checks (external site) · blockbook.ravencoin.org — Blockbook: Ravencoin block 4,489,632 (external site) · blockbook.ravencoin.org — Blockbook: Ravencoin block 4,493,664 (external site)
-
L2BEAT recorded a five-day pause in Metis posting data and state roots to Ethereum
L2BEAT's liveness record shows no transaction-data submissions and no state-root updates from Metis to Ethereum from 13 June 2026 (about 03:30 UTC) until 18 June 2026 (about 11:05 UTC), against a usual interval of roughly 40 minutes. The event log of Metis's state commitment contract on Ethereum shows no state-root posts between 13 June 03:34 UTC and 18 June 11:05 UTC, matching L2BEAT. No Metis announcement explaining the pause was found in this review.
- Implementation:incident; cause not published in the sources reviewed
- Release:no related Metis node release found
- Activation:posting resumed on 18 June 2026 per L2BEAT and the Ethereum event log
Sources: L2BEAT — Metis Andromeda (external site) · Blockscout (Ethereum) — Event logs of the Metis state commitment contract on Ethereum, June 2026 (external site)
-
Astar is retiring Wasm (ink!) smart contracts
The Astar Foundation proposed retiring Wasm contracts because ink! was discontinued by its maintainers and pallet-contracts is no longer maintained upstream. Uploads and new instances were frozen with runtime 2207 on 15 June 2026, a 90-day migration window closed around 10 September, and runtime 2400, enacted on 19 September, blocks all calls to Wasm contracts and settles the pallet's held balances. Runtime 2500 removes the pallet and was released on 23 September.
- Proposal:announced by the Astar Foundation on 2026-06-12
- Implementation:freeze in runtime 2207, call block in runtime 2400, pallet removal in runtime 2500
- Release:runtime 2500 released 2026-09-23
- Activation:freeze live 2026-06-15; calls blocked since 2026-09-19; pallet removal not live on 2026-09-29 (spec version 2400)
Sources: Astar Forum — WASM smart-contract sunset on Astar and Shiden (external site) · Subsquare (Astar democracy) — Referendum 59: Runtime upgrade to 2207 (slot-based Aura migration phase 3; Wasm upload freeze) (external site) · Subsquare (Astar democracy) — Referendum 63: Runtime upgrade to 2400 (WASM smart-contract decommission, step 1 of 2) (external site) · Astar Network (GitHub) — runtime-2400 release notes (external site) · Astar Network (GitHub) — runtime-2500 release notes (external site) · Astar — Astar public RPC (state_getRuntimeVersion read, 2026-09-29) (external site)
-
Neo-CLI v3.10.0 added wallet, RPC and Docker changes without a hard fork
Neo released Neo-CLI v3.10.0 as an optional upgrade for TestNet and MainNet. It activates no hard fork, stays compatible with the current network and needs no resync. Neo's notice lists BIP-39 mnemonic import and export for wallets, a separate Expired result in transaction validation, rejection of duplicate Conflicts attributes, a DeferredRelay plugin that relays transactions automatically, wallet RPC methods and CLI commands named sign, relay, signmsg and verifymsg, an official Docker image and fuller RPC diagnostics. It also lists the NeoVM SHL/SHR fix, jump-table refactor and cryptographic verification update, saying the release prepares for the Gorgon hard fork without activating it; the July v3.10.1 notice names these as Gorgon's changes.
- Implementation:released in Neo-CLI v3.10.0 and core library v3.10.0
- Release:released June 2026 as an optional upgrade
- Activation:no hard fork; takes effect when a node installs it. Neo planned MainNet deployment for 26 June 2026, which was not confirmed in this review
Sources: Neo — Neo-CLI v3.10.0 TestNet and MainNet Upgrade Notice (external site) · neo-project/neo-node maintainers — Neo CLI v3.10.0 (external site) · neo-project/neo maintainers — neo v3.10.0 release (external site) · Neo — Neo-CLI v3.10.1 TestNet and MainNet Upgrade Notice (external site)
-
Grin node 5.4.1 fixes parallel sync and peer handling
Grin v5.4.1 is a point release of the reference node published without notes. Its seven commits fix a loop that could leave parallel state sync stuck while requesting kernel segments, cap how many items the node will allocate when decoding sync segments from peers, stop treating newly learned peers as healthy before they are checked and mark peers that fail pings as defunct, and refresh the list of seed nodes a new node contacts first.
- Implementation:shipped in v5.4.1
- Release:stable release published 2026-06-11
- Activation:no consensus change; takes effect as nodes upgrade
Sources: Grin developers (mimblewimble/grin) — Grin v5.4.1 (external site) · GitHub API (mimblewimble/grin) — Grin commits between v5.4.0 and v5.4.1 (external site) · GitHub API (mimblewimble/grin) — PIBD sync stuck fixes (pull request 3822) (external site) · GitHub API (mimblewimble/grin) — More reliable peers check (pull request 3824) (external site) · GitHub API (mimblewimble/grin) — PIBD: bound segment decoding allocations (pull request 3850) (external site)
-
Bitcoin Cash Node moved its funding multisig and replaced an unreachable signer
Bitcoin Cash Node said it moved its development fund (about 2,048 BCH) to a new 3-of-5 multisig on 27 May 2026, replacing one co-signer: its founding lead maintainer, freetrader, whom the project said nobody had been able to contact since May 2024.
- Implementation:funds moved to the new multisig on 2026-05-27 per the notice
- Release:announced 2026-06-10
- Activation:not a protocol activation
-
Client 2.8.1 scheduled the Cancun, Prague and Pascal upgrades for 30 June 2026
Chiliz released client v2.8.1, which set mainnet fork times of 11:00 CEST on 30 June 2026 for Cancun and 11:30 CEST for Prague and Pascal, after release candidate 2.8.0-rc1 had scheduled the same upgrades for the Spicy testnet on 18 May 2026. Chiliz's changelog says they bring blob transactions, transient storage and EIP-7702 account delegation, and the docs moved the recommended compiler target to Prague with Solidity 0.8.30.
- Implementation:client 2.8.0-rc1 on Spicy (2026-05-18) and 2.8.1 for mainnet
- Release:v2.8.1 published 2026-06-10
- Activation:scheduled for 2026-06-30; header fields observed in a 2026-09-29 mainnet block
Sources: Chiliz (GitHub) — Chiliz Chain client v2.8.1 release notes (external site) · Chiliz (GitHub) — Chiliz Chain client v2.8.0-rc1 release notes (Spicy testnet) (external site) · Chiliz Chain Docs — Blockchain code changes (external site) · PublicNode (Allnodes) — PublicNode Chiliz RPC: latest block read on 2026-09-29 (external site)
-
NVNM Chain launched as a shared-security consumer of MANTRA
Inveniam Labs announced that NVNM Chain, built with MANTRA and described as a MANTRA Layer 2, had launched in May 2026. On-chain records show it as an Interchain Security consumer chain (nvnm-1) run by seven opted-in MANTRA validators; NVNM's site describes an invitation-only closed beta while its docs call the mainnet live.
- Implementation:consumer chain registered and launched on MANTRA's provider module
- Release:closed beta per NVNM's site
- Activation:seven validators active on 27 September 2026
Sources: Inveniam Labs (GlobeNewswire) — NVNM Chain Announces Upcoming Launch of $NVNM Token and MANTRA Community Early Access Initiative (external site) · Inveniam — Inveniam to Acquire MANTRA (external site) · MANTRA (public API node) — Interchain Security consumer chain 0 (nvnm-1) record (mantra-1 public REST endpoint) (external site) · MANTRA (public API node) — Interchain Security consumer 0 validator set (mantra-1 public REST endpoint) (external site) · NVNM Chain — NVNM Chain (external site) · MANTRA — NVNM Chain Launches as MANTRA L2 to Power Verifiable AI Data (external site)
-
Release 1.25.0 added beta non-SGX nodes and machine ID replacement
SCRT Labs published node software 1.25.0, the newest release in its original repository. The notes list four additions: operators can replace a node's machine ID by sending a dedicated transaction; nodes can run in beta on hardware without Intel SGX if paired with an existing SGX node; the emergency validator list is updated; and machines validated through Proof of Cloud are supported. The next day the team said on-chain proposal 354 had been submitted to upgrade mainnet to 1.25.
- Proposal:proposal 354 submitted (forum notice 2026-06-11); outcome not read in this pass
- Implementation:features shipped in node release 1.25.0; non-SGX support marked beta
- Release:published 2026-06-10 in the scrtlabs repository
- Activation:not confirmed in this pass; no chain endpoint was read
Sources: scrtlabs/SecretNetwork maintainers — SecretNetwork v1.25.0 release notes (external site) · Secret Network Forum (SCRT Labs post) — Mainnet Upgrade to 1.25 (external site) · scrtlabs/SecretNetwork maintainers (GitHub) — scrtlabs/SecretNetwork release feed (Atom) (external site) · Secret3dev on GitHub — Secret3dev/SecretNetwork releases (external site)
-
Toncoin renamed Gram (GRAM) after a community vote
The official TON channel announced that 81.22% of votes favoured renaming the native coin from Toncoin (TON) to Gram (GRAM), effective 15 June 2026 at 12:00 UTC. The network name, balances, addresses, contracts, NFTs, staking and DeFi positions were unchanged, and no swap or migration was required.
- Proposal:community vote June 1-8, 2026; 81.22% in favour
- Implementation:name, ticker and logo change only
- Release:not a protocol change
- Activation:effective 2026-06-15 12:00 UTC
Sources: Gram of TON (Telegram channel) — Native Token Rename: Toncoin (TON) to Gram (GRAM) (external site) · TON (ton.org) — TON: The Open Network (external site) · Trezor — Gram (prev. Toncoin) support status (external site) · Ledger — Toncoin wallet (external site)
-
Eclipse Foundation reset ES's role around the Human API app
The Foundation said it had sold part of its treasury to fund operations, that its focus had been Human API, a mobile app it says has passed 100,000 users new to crypto, and that ES is Human API's only token. It dropped the utility-token framing for ES in favour of user incentives it is exploring, kept supply fixed at 1 billion, and published a new allocation: 24% float, 29% ecosystem and development, 16% contributors and 31% early supporters and investors, with a third of the last two groups unlocking on 16 July 2026 and the rest monthly over 24 months.
- Implementation:treasury sale reported as completed; token mechanisms described as being explored
- Release:announced in a Foundation blog post
- Activation:not a protocol change
Source: Eclipse Collective — Updated $ES Tokenomics (external site)
-
Governance raised MANTRA inflation to 16% and the Association's share of issuance
Proposal 33, which also scheduled the v8.2.0 upgrade, raised the fixed yearly inflation rate from 8% to 16% and the share of new issuance going to the MANTRA Chain Association from 40% to 60%, citing a staked share of about 25% and rising security costs.
- Proposal:passed as proposal 33
- Implementation:mint settings updated
- Release:v8.2.0 released
- Activation:16% shown in live settings on 27 September 2026
Sources: MANTRA (on-chain governance record) — Governance proposal 33: v8.2.0 upgrade, inflation recalibration and emissions update (external site) · Polkachu (governance proposal mirror) — Mantra proposal 33: v8.2.0 mainnet upgrade (external site) · MANTRA (public API node) — Mint parameters (mantra-1 public REST endpoint) (external site) · MANTRA (public API node) — Annual provisions (mantra-1 public REST endpoint) (external site) · MANTRA Chain Docs — Inflation and Vesting Schedule (external site)