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 5 of 14.
One chain's developments, A to Z
-
Fiber Network v0.9.0 focuses on reliability and security
The Fiber reference node added a database migration system, backup and restore, on-chain settlement of pending payments after a channel is force-closed, and routing, watchtower and recovery improvements, with broad input-validation and resource-exhaustion hardening. A follow-up v0.9.1 on 2026-09-11 fixed settlement edge cases.
- Implementation:Released
- Release:v0.9.0 published 2026-08-06; v0.9.1 published 2026-09-11
- Activation:not a CKB consensus change
Sources: Nervos Network (nervosnetwork/fiber) — Fiber v0.9.0 (external site) · Nervos Network (nervosnetwork/fiber) — Fiber releases (external site) · Nervos Network (nervosnetwork/fiber) — Fiber Network Node (external site)
-
Era node software core v31.4.0 added support for Protocol Upgrade 29.5
Matter Labs published release core v31.4.0 of the zksync-era node software. Its notes list support for Protocol Upgrade 29.5; let the node's Ethereum watcher take proof verification key hashes from the new-protocol-version event and handle both formats of upgrade events; fix how the verifier component masks factory dependency hashes; and remove a sort from one database query. The notes do not say whether node operators must install it or when version 29.5 took effect on mainnet. Core v31.5.0 followed on 8 August 2026; its notes list one change, a vm2 library update labelled v32.
- Implementation:Protocol Upgrade 29.5 support merged into the core node code, with Ethereum watcher, verifier and database changes
- Release:core v31.4.0 published on GitHub on 2026-08-06; core v31.5.0 marked Latest from 2026-08-08
- Activation:takes effect on each node when its operator installs it; the release gives no mainnet activation time for protocol version 29.5
Sources: Matter Labs (GitHub) — core: v31.4.0 (external site) · Matter Labs (GitHub) — core: v31.5.0 (external site) · Matter Labs (GitHub) — matter-labs/zksync-era releases (external site) · ZK Nation Forum — Notice of 2026 Instant Upgrades: Security Patches (external site)
-
B² publishes a recovery runbook for rollup nodes stuck after long outages
B² added an operator runbook for rollup nodes that fall so far behind that the batch data they need has already expired from B² Hub, which keeps blobs for a limited period. The fix stops the normal derivation software, feeds the node the current chain tip from a public B² endpoint, and resets its safe and finalized markers.
- Implementation:Documented
- Release:runbook and scripts published
- Activation:available to operators
Sources: B² Network (GitHub) — Add b2 op-geth catch-up/recovery runbook and scripts (external site) · B² Network Documentation — OP-Geth Catch-Up & Recovery Runbook (external site) · B² Network Documentation — Deploy a rollup node (external site)
-
Greymass launched a browser version of the Anchor wallet with free Vaulta accounts
Aaron Cox of Greymass announced Anchor for the web, a non-custodial wallet that runs in the browser with passkey-protected keys and Ledger support in Chrome-based browsers. It creates Vaulta accounts for free after a Google or Apple sign-in, and apps built on Greymass's Wharf libraries can trigger account creation from inside the app. The post says the project began as network-funded work and was first planned as an account.vaulta.com service.
- Implementation:Launched
- Release:available at anchorwallet.io
- Activation:available per Greymass; not tested in this review
Sources: Aaron Cox (Greymass), jesta.blog — Anchor for the web (external site) · Greymass — Anchor Wallet (external site) · Vaulta Documentation — Accounts (external site)
-
Shielded transfers announced live on Dash Platform mainnet
dash.org announced that shielded transfers are live on the Dash Platform (Evolution) mainnet. Dash Platform 4.0, released on 1 July 2026, introduced an Orchard-based shielded pool for Platform credits under protocol version 12, with private transfers, shielding from a main-chain asset lock and shielded withdrawals back to the main chain.
- Implementation:shipped in Dash Platform 4.0.0
- Release:v4.0.0 published 2026-07-01; v4.1.0 (protocol version 13) followed on 2026-07-27
- Activation:announced live on mainnet 2026-08-04; exact activation height not verified
Sources: Dash (dash.org) — Shielded transactions are live on the Dash Evolution mainnet (external site) · Dash Platform developers (dashpay) — Dash Platform v4.0.0 release notes (external site) · Dash Platform developers (dashpay) — Dash Platform v4.1.0 release notes (external site) · Dash documentation — Dash Platform docs: Shielded Pool (external site)
-
Repository for the retired proof-of-work client archived
The HorizenOfficial/zen repository, home of the client for Horizen's former proof-of-work chain, was archived and made read-only; its notice says vulnerability reports are no longer accepted and points to the current Horizen docs.
- Implementation:repository archived
- Release:final release was zend 6.0.0 (1 July 2025)
- Activation:archived 4 August 2026
Sources: Horizen contributors — HorizenOfficial/zen (archived) (external site) · Horizen contributors — zend v6.0.0 release notes (external site)
-
Dash Core 23.1.8 fixes three remotely triggerable node crashes
Dash Core 23.1.8, the latest stable 23.1 patch at review, fixed three crashes a remote peer could trigger: one while removing masternode provider transactions after an operator-key change, one from an unchecked quorum type in signature-share messages and one from quorum commitments that reference a block with no known parent. It also added limits and checks across many peer message handlers, including quorum signing, ChainLock, governance, CoinJoin, spork and bloom-filter messages. The developers said consensus rules and funds are not affected.
- Implementation:shipped in Dash Core 23.1.8
- Release:stable patch release published 2026-08-03; latest stable Dash Core release at review
- Activation:no consensus change; takes effect on each node as it upgrades
Sources: Dash Core developers (dashpay) — Dash Core 23.1.8 release announcement (external site) · Dash Core developers (dashpay) — Dash Core v23.1.8 release notes (external site) · Dash Core developers (dashpay) — Dash Core releases (Atom feed) (external site)
-
Mwixnet mixing service opened for community testing on testnet
A Grin developer reported deploying a public testnet route for mwixnet, with one swap server and one mixer running over Tor, and published a test guide while wallet and server compatibility work continued.
- Proposal:community test
- Implementation:testnet route deployed by a developer
- Release:not released for mainnet
- Activation:not active on mainnet as of 2026-09-27
Sources: Grin forum — Mwixnet community TEST (external site) · Grin developers — mimblewimble/mwixnet (external site) · Grin forum — Grin Development Progress Reports (external site)
-
Node release v2026.07 improves QUIC connection and public-broadcast performance
TON's v2026.07 node release improved the performance of QUIC connections and public broadcasts between nodes, added metrics for QUIC and fixed stability issues. The release notes credit several bug-bounty participants. They describe no change to contract behaviour, fees or consensus rules.
- Implementation:implemented in node software
- Release:released 2026-08-03
- Activation:no network-wide activation described; changes apply to nodes that install the release
Sources: ton-blockchain maintainers — TON v2026.07 release notes (external site) · ton-blockchain maintainers — TON releases (external site)
-
AtomicAssets v2 contract released and running on WAX mainnet
The AtomicAssets maintainers released version 2.0.0 of the AtomicAssets NFT contract, adding mutable templates, per-field schema media types, collection author succession, template maintenance actions and CPU reductions. It also ends new token backing: the backing action now always fails, while tokens already backed are still released when an asset is burned. The contract code hash read on WAX mainnet on 29 September 2026 matched the published v2.0.0 build.
- Implementation:released as v2.0.0 after five release candidates
- Release:GitHub release v2.0.0 published 2026-08-03
- Activation:live: the atomicassets account's code hash on 2026-09-29 equalled the v2.0.0 wasm hash
Sources: AtomicAssets (GitHub) — AtomicAssets v2.0.0 release (external site) · AtomicAssets (GitHub) — AtomicAssets CHANGELOG (external site) · Greymass (public WAX API node) — WAX Chain API get_code_hash (atomicassets) via wax.greymass.com (external site)
-
Community node 3.2: security fixes, new gas model and a six-month proof window, activated by miner vote
Community release 3.2 is mandatory. It upgrades to Pact 5.4.1, charges signatures and proofs by size and verification cost, shrinks the cross-chain proof window to six months, fixes several security flaws and activates by miner vote. Live block headers show the vote passed and the new rules took effect at block height 7,156,800 on 20 August 2026. A transparency post on 21 August 2026 described the flaws and said none had been exploited.
- Proposal:released for miner vote
- Implementation:implemented in 3.2 and 3.2.1
- Release:released 2026-08-02 (3.2) and 2026-08-21 (3.2.1)
- Activation:activated at block height 7,156,800 on 2026-08-20, read from live block headers; no activation announcement found
Sources: Kadena Community Edition — chainweb-node Community Edition 3.2 (external site) · Kadena Community Edition — chainweb-node Community Edition changelog (external site) · Kadena Community Edition — KDA Community Edition posts (Medium feed) (external site) · Kadena Community Edition — chainweb-node Community Edition 3.1 (external site) · Kadena Community Edition — Community node block header, chain 0, height 7,156,800 (external site) · Kadena Community Edition — Community mainnet version definition (Mainnet.hs) (external site)
-
Litecoin Core 0.21.5.6 added MWEB relay limits and a soft-fork rule
An urgent maintenance release that limits expensive MWEB light-client requests, caps MWEB transaction weight and inputs in relay policy, and adds a soft-fork rule from height 3,154,440 rejecting MWEB kernels that signal a peg-out with an empty peg-out list.
- Implementation:merged and released
- Release:Released
- Activation:rule scheduled from height 3,154,440; chain tip is past that height
Sources: litecoin-project — Litecoin Core v0.21.5.6 (external site) · Litecoin Space — Litecoin Space API: chain tip height (external site)
-
Governance raised the burn tax from 0.5% to 1.5%
Proposal 12223, a tax-module parameter change, raised the burn tax on taxable transfers from 0.5% to 1.5%. Its text says the existing 80/10/10 split stays: 1.2 percentage points burned, 0.15 to the community pool and 0.15 to the oracle reward pool. Voting ended on 2 August 2026 with the proposal passed, and the tax parameters read on 2026-09-29 show a rate of 0.015.
- Proposal:passed as proposal 12223 (voting ended 2026-08-02)
- Implementation:governance parameter change; no new software
- Release:no release needed; executed by the governance module
- Activation:in effect: tax parameters read on 2026-09-29 show 1.5%
Sources: Terra Classic on-chain state via PublicNode REST endpoint — Terra Classic proposal 12223: Set the On-Chain Tax Rate to 1.5% (external site) · Agora, Terra Classic community forum — Set the On-Chain Tax Rate to 1.5% (forum discussion) (external site) · Terra Classic on-chain state via PublicNode REST endpoint — Terra Classic tax module parameters (external site) · Terra Classic community documentation (terra-classic-io/website repository) — Terra Classic module specification: tax (external site) · Terra Classic community documentation (terra-classic-io/website repository) — Terra Classic docs: Transaction best practices (external site) · Terra Classic community documentation (terra-classic-io/website repository) — Terra Classic docs: Fees (external site)
-
Moonbeam entered maintenance mode and later stopped producing blocks
From 00:00 UTC on 2026-08-01 the network rejected all user transactions while blocks continued for a final wind-down. The last finalized block found in this review, 16,796,696, is dated 2026-08-10 11:35:57 UTC.
- Implementation:maintenance mode active from 2026-08-01
- Release:not applicable
- Activation:block production observed to end 2026-08-10
Sources: Subscan — Moonbeam explorer (external site) · Subscan — Moonbeam block 16796696 (external site) · CryptoSlate — Moonbeam just halted all user transactions (external site)
-
IBC closed in both directions on Sei
Governance Proposal 121, which passed on 31 July 2026, switched off outbound IBC transfers on Sei, after Proposals 116 and 120 had already disabled inbound transfers. IBC tokens still on Sei can move between Sei addresses but can no longer be sent back to their origin chains over IBC.
- Proposal:Proposal 121 passed 31 July 2026
- Implementation:IBC module outbound transfers disabled; inbound disabled by Proposals 116 and 120
- Release:governance parameter change; v6.4 (April 2026) added the inbound switch
- Activation:active per Sei documentation
Sources: Sei Documentation — SIP-03 Migration Guide (external site) · Sei Documentation — Sei EVM Upgrade for Exchanges and Custodians (external site) · Sei Documentation — Sei Network Interoperability Framework (external site) · Sei Blog — Sei v6.4 Is Live on Mainnet: What It Means for IBC (external site)
-
Sei v6.6 brought the first Giga components to mainnet
The mandatory v6.6.0 release, targeting mainnet height 224,201,091 on 4 August 2026, made the Ares execution client the default execution path for upgraded nodes and began the first, operator-controlled phase of the Eidos storage migration, which separates EVM history from other chain state. Autobahn consensus code is included but disabled until a separate network activation.
- Proposal:Software upgrade Proposal 122 (v6.6, height 224,201,091) was open for voting on 31 July 2026 per Sei's blog and is shown as passed on the Seistream explorer
- Implementation:Released
- Release:v6.6.0 released 31 July 2026 as a mandatory mainnet upgrade
- Activation:Sei's Giga page reports activation on 4 August 2026; the upgrade height was not checked on chain
Sources: Sei Protocol contributors — sei-chain v6.6.0 release notes (external site) · Sei Blog — Ares and Eidos, the first components of the Giga Upgrade, will go live in Sei 6.6 (external site) · Sei Blog — The Eidos Upgrade: replacing Sei's storage database while the chain is running (external site) · Sei Documentation — What Is Sei Giga? (external site) · Sei Documentation — Sei Giga Technical Specification (external site) · STAKEME — Proposal #122: v6.6 (external site)
-
java-tron GreatVoyage-v4.8.2.1 (Heraclitus) non-mandatory maintenance release
GreatVoyage-v4.8.2.1 (Heraclitus) was published as a non-mandatory upgrade after Pyrrho. Its notes list one functional change, improved HTTP API performance, plus two dependency updates: libp2p from 2.2.8 to 2.2.9 and grpc-java from 1.81.0 to 1.83.0. They describe no new virtual-machine feature, TIP or governance parameter.
- Implementation:shipped in java-tron v4.8.2.1
- Release:non-mandatory release; no deadline stated in the release notes
- Activation:no network activation described; the changes apply to nodes that install the release
Sources: tronprotocol (GitHub) — GreatVoyage-v4.8.2.1 (Heraclitus) release notes (external site) · tronprotocol (GitHub) — Release notes from java-tron (Atom feed) (external site)
-
Governance revives expired IBC light clients for Injective, UX Chain and Secret
Kava governance passed three proposals replacing expired IBC light clients with fresh ones: Injective (voting closed 26 May 2026), UX Chain (3 June 2026) and Secret (30 July 2026). An expired client stops token transfers on that path until a vote restores it. The same Secret client had already been revived in August and December 2025, and the UX Chain client had expired again by 27 September 2026.
- Proposal:Passed
- Implementation:substitute clients applied on-chain
- Release:no software release involved
- Activation:paths restored after each vote; the UX Chain client had expired again by 27 September 2026
Sources: Kava Labs public REST endpoint — Proposal 216: Recover IBC light client for Injective (external site) · Kava Labs public REST endpoint — Proposal 217: Recover IBC light client for UX Chain (external site) · Kava Labs public REST endpoint — Proposal 220: Recover IBC light client for Secret (external site) · Kava Labs public REST endpoint — Proposal 203: Recover IBC light client for Secret (external site) · Kava Labs public REST endpoint — Proposal 209: Recover IBC light client for Secret (external site) · Kava Labs public REST endpoint — Kava IBC client 07-tendermint-124 (UX Chain) status (REST endpoint) (external site)
-
SIMD-0286 block limit increase reported activated on Mainnet
Protocol activation: the July 30 official changelog reported that Mainnet activated the SIMD-0286 feature gate, raising the per-block compute limit to 100 million compute units. This capacity ceiling does not guarantee that every block is full or that transaction fees and latency remain constant.
- Stage:Activated
Source: Solana Foundation — Solana Changelog: July 30, 2026 (external site)
-
PoX-5 hard fork activated at Bitcoin block 960,230
Stacks activated Epoch 4.0, bringing PoX-5 (SIP-045) and Clarity 6 (SIP-044). The change added Bitcoin bonds that pair BTC with locked STX, removed most staking cooldown cycles, sent miner BTC into a reward pool converted to sBTC instead of paying stakers' Bitcoin addresses directly, and restored the 1,000 STX coinbase.
- Proposal:SIP-044 and SIP-045 approved by community vote (reported 21 July 2026)
- Implementation:implemented in stacks-core 4.0.1
- Release:stacks-core 4.0.1 released 15 July 2026 as a mandatory upgrade
- Activation:active from Bitcoin block 960,230, reached 30 July 2026
Sources: Stacks Labs — The Stacks PoX-5 Hardfork Is Live: What Comes Next (external site) · Stacks Labs — SIP-044 and SIP-045 Approved: Bitcoin Staking Is Ratified (external site) · Stacks Improvement Proposals (stacksgov) — SIP-045: PoX-5 Bitcoin Staking (external site) · Stacks core contributors (GitHub) — stacks-core release 4.0.1 (external site) · Stacks Foundation — Stacks 4.0.1 Network Upgrade - Clarity 6 & Bitcoin Staking (Hard Fork) (external site) · Stacks Documentation — Epoch 4.0 Consensus Changes (external site)
-
Osaka1 fork set a 1 gwei minimum base fee from 5 August 2026
Bera-Reth v1.4.3 announced the Osaka1 hard fork for 5 August 2026 at 16:00 UTC, enforcing a network-wide minimum base fee and minimum blob base fee of 1 gwei each. The release notes say fees at these floors are burned rather than paid to the proposer. Operators were told to run v1.4.4, released the same day, which restored a transaction-pool tip check. BeaconKit's notes for the fork say Osaka1 changed only the execution layer, so the consensus client did not need an upgrade.
- Implementation:Bera-Reth v1.4.3, superseded by v1.4.4
- Release:Released
- Activation:live on mainnet since 2026-08-05 per Berachain's upgrade table
Sources: Berachain (GitHub) — bera-reth v1.4.3 (Osaka1) (external site) · Berachain docs — Protocol Features (upgrade timeline) (external site) · Berachain (GitHub) — Bera-Reth releases (external site) · Berachain (GitHub) — BeaconKit v1.4.2-rc.0 (Osaka1 on Bepolia) (external site)
-
Bitcoin Cash Node v29.1.0 minor release
Bitcoin Cash Node released v29.1.0, a minor release with RPC and REST usability improvements, bug fixes and performance work, and recommended that users of earlier releases upgrade.
- Implementation:Released
- Release:released 2026-07-29
- Activation:not a protocol activation
Sources: Bitcoin Cash Node — Announcing Bitcoin Cash Node v29.1.0 (external site) · Bitcoin Cash Node (GitHub) — Bitcoin Cash Node release 29.1.0 (external site) · Bitcoin Cash Node — Bitcoin Cash Node v29.1.0 release notes (external site)
-
Bitlayer shuts down its public testnet
Bitlayer announced that it would shut down its public testnet at 23:00 UTC on 31 July 2026, discontinuing all testnet services, data and endpoints. Test data would not be kept and test assets would not be converted to mainnet. Mainnet services were stated to be unaffected.
- Implementation:Announced
- Release:not a software release
- Activation:scheduled for 31 July 2026 at 23:00 UTC per the post
Sources: Bitlayer Blog — Bitlayer Testnet Shutdown Notice (external site) · Bitlayer Documentation — Network (external site)
-
csprUSD stablecoin to be upgraded as Casper's standard dollar settlement token
The Casper Association said csprUSD, a dollar stablecoin first launched by Sarson Funds in 2024, is being upgraded with a new contract built for Casper 2.0 and CEP-3009 signed transfer authorizations, to serve as the default settlement asset for Casper's x402 payment facilitator.
- Proposal:upgrade announced by the Casper Association
- Implementation:new contract described; address not published in the post
- Release:not confirmed
- Activation:not confirmed on mainnet
Sources: Casper Association — Introducing csprUSD: The Stablecoin of the Machine Economy (external site) · Casper Association — Sarson Funds csprUSD Stablecoin Live on Casper Network Testnet (external site) · Casper Association — The latest from the Casper Association (news index) (external site)
-
Node v3.1.2 adds four newer opcodes to the Ontology EVM
Ontology released node v3.1.2, which it described as security optimisations plus four EVM additions: PUSH0, BASEFEE, MCOPY and transient storage (TSTORE and TLOAD). All mainnet nodes had to upgrade before block height 20,800,000, which Ontology estimated for 21 August 2026. Ontology noted that these are four specific additions, not the complete opcode set of any single Ethereum upgrade.
- Implementation:shipped in ontology v3.1.2
- Release:released 29 July 2026; upgrade mandatory for all mainnet nodes
- Activation:scheduled for height 20,800,000; the chain was past that height on 2026-09-29
Sources: Ontology News — Ontology MainNet v3.1.2: Four Ethereum Opcodes Arrive on the Ontology EVM (external site) · Ontology (GitHub) — ontology v3.1.2 release (external site) · Ontology — Ontology public node REST: current block height (read 2026-09-29) (external site)
-
Akash announced confidential-compute deployments
Akash announced that tenants can request trusted-execution hardware (Intel TDX or AMD SEV-SNP, with NVIDIA GPUs in confidential mode) so that provider operators cannot read workload memory, under AEP-83. The post says provider capacity is at an early stage and that automatic attestation is still being built.
- Proposal:AEP-83
- Implementation:announced as available with early provider capacity
- Release:Announced
- Activation:not a chain upgrade; availability depends on provider hardware
Source: Akash Network — Confidential Compute Comes to Akash (external site)
-
Beam proposed lustration to verify circulating supply
Beam proposed a one-time disclosure step: each output created before a future activation height would reveal its amount and asset type the first time it is spent, so nodes can check disclosed totals against the emission schedule. Ownership would stay hidden, and new outputs would stay fully confidential.
- Proposal:published proposal; draft BIP-5 posted 8 August 2026 for discussion, status unassigned, no vote result found
- Implementation:not verified
- Release:no release carrying it was verified
- Activation:not active; activation height to be set by vote
Sources: Beam blog — Lustration Proposal: Verifying Beam's Supply Integrity (external site) · Beam Biweekly (community newsletter by Danai Raza) — Beam Biweekly: August 2026 Ed. #2 (external site) · Beam community forum (test forum) — BIP-5: BeamX DAO vote on Lustration (draft and discussion) (external site)
-
Governance removed stuck IBC rate limits on USDC and USDT
Proposal 40 passed on 2026-07-28 and removed the rate limits on Noble USDC and Kava USDT. The proposal said the limits had been measured against an outdated snapshot that never reset, leaving almost no room for outbound transfers.
- Proposal:passed (proposal 40)
- Implementation:executed as a governance message
- Release:no software release required
- Activation:effective on passage
Sources: Dymension Hub governance via NodeStake public API — Proposal 40: Remove IBC rate limits for Noble USDC and Kava USDT (external site) · Dymension Hub via NodeStake public API — IBC denomination trace for USDC (live Hub query) (external site) · Dymension Hub via NodeStake public API — IBC denomination trace for USDT (live Hub query) (external site) · Dymension Hub via NodeStake public API — IBC rate limits (live Hub query) (external site)
-
Juno v30 approved: fee market and Cosmos SDK 0.53
Governance proposal 377 passed and scheduled the v30.0.0 upgrade at height 40,420,069. The release moves Juno to Cosmos SDK 0.53, CometBFT 0.38, IBC-Go 10 and CosmWasm 2.2 support, turns on an on-chain fee market for JUNO with a minimum base gas price of 0.075 ujuno, adds voting-snapshot state and removes several retired modules, including the global fee and interchain query modules.
- Proposal:proposal 377 passed
- Implementation:released as v30.0.0
- Release:released 2026-07-16
- Activation:applied at height 40,420,069 per on-chain upgrade record
Sources: Juno on-chain state via PublicNode REST endpoint — Juno proposal 377: Upgrade Juno Mainnet to v30.0.0 (external site) · CosmosContracts — Juno v30.0.0 release (external site) · CosmosContracts mainnet repository — Juno v30 mainnet upgrade instructions (external site) · Juno on-chain state via PublicNode REST endpoint — Juno applied upgrade plan v30 (external site) · Juno on-chain state via Polkachu REST endpoint — Juno fee market parameters (external site)
-
Kaia Safe interface retired as Safe Global adds Kaia support
Kaia announced that Safe Global now supports Kaia mainnet and the Kairos testnet directly, and that its own hosted interface, safe.kaia.io, would close on 31 August 2026. Kaia's migration guide, updated on 18 September 2026, confirms the interface was retired and that existing Safe accounts, owners, thresholds and assets are unchanged.
- Implementation:Kaia supported on Safe Global
- Release:announced 2026-07-28
- Activation:safe.kaia.io retired on 31 August 2026, per Kaia's guide
Sources: Kaia Blog — Important Update: Kaia Safe is moving to Safe Global (external site) · Kaia Docs — Migrate to Safe Global (external site)
-
Movement said MVMT Labs filed for Chapter 11 and the network is not part of the filing
In a CEO update, Movement said the network was operating normally, that MVMT Labs, Inc. had filed for Chapter 11 as a separate entity, and that Move Industries, the foundation, MOVE and the network are not part of that filing.
- Implementation:filing reported by Movement
- Release:not applicable to software
- Activation:Movement states network operations are unaffected
Source: Movement Network — An update from Torab Torabi, CEO, Movement (external site)
-
Holders rejected SCRT Labs' proposal to migrate SCRT to Arbitrum
SCRT Labs proposed migrating SCRT to a new ERC-20 token on Arbitrum, claimable one-for-one from a 1 September snapshot, and said it would end support for the existing chain on that date either way. Signaling proposal 360 was rejected when voting closed on 28 July 2026; a Foundation counter-proposal (361) voted the same day was also rejected.
- Proposal:rejected on chain
- Implementation:not implemented
- Release:not applicable
- Activation:no migration activated
Sources: Secret Network governance (public REST endpoint) — Proposal 360: Migrate $SCRT to Arbitrum via Snapshot (external site) · Secret Network governance (public REST endpoint) — Proposal 361: Continue Secret Network on Cosmos under community stewardship (external site) · Secret Network Forum (SCRT Labs post) — $SCRT is Moving to Arbitrum (external site) · Secret Network Forum (SCRT Labs post) — Signaling Proposal: Migrate $SCRT to Arbitrum via Snapshot (external site) · Secret Network Forum (Secret Network Foundation post) — Signaling Proposal: Continue SCRT under community with remediation (external site) · Secret Network Forum (Secret Network Foundation draft, with an SCRT Labs reply) — Community Continuance of Secret Network (L1) (external site)
-
ApeChain's docs removed the native-yield and interim Security Council sections
A 27 July 2026 commit titled 'Removed native yield and security council' deleted the 'Functional Native Yield' line from ApeChain's architecture page and the section describing an interim Security Council of Ape Foundation and infrastructure-partner signers, which ApeCoin DAO elections were meant to replace. The same cleanup pull request removed several third-party tool pages.
- Implementation:documentation change merged
- Release:live on docs.apechain.com
- Activation:no change to chain rules; effect on yield or signers not established
Sources: Ape Foundation (GitHub, ape-foundation/apechaindocs) — Commit 45d84d1: Removed native yield and security council (external site) · Ape Foundation (GitHub, ape-foundation/apechaindocs) — Pull request #73 (cleanup): commits (external site) · Ape Foundation (ApeChain Docs) — ApeChain Architecture (external site) · L2BEAT — ApeChain (external site)
-
ApeChain's node guide moved to the apechain-3.9.9 Nitro image and a July 2026 snapshot
The Ape Foundation's docs repository updated the Run a Node page on 27 July 2026 to point operators to a v3.9.9 replica guide and the Docker image nitro-node:apechain-3.9.9, replacing the apechain-v3.5.6 image. On 3 August 2026 it added a snapshot dated 30 July 2026 with resumable download steps and its exact size.
- Implementation:node image apechain-3.9.9 referenced in ApeChain's docs
- Release:documented for operators; no release notes found
- Activation:no activation height or date published
Sources: Ape Foundation (GitHub, ape-foundation/apechaindocs) — Commit 692f0fa: Update run-node.mdx (v3.9.9 replica guide and image) (external site) · Ape Foundation (GitHub, ape-foundation/apechaindocs) — Commit aea95f3: Update run-node.mdx (30 July 2026 snapshot) (external site) · Ape Foundation (ApeChain Docs) — Run a Node (external site)
-
Lotus v1.36.2 corrected Ethereum-style RPC answers and changed tracing settings
Lotus Node v1.36.2 is a recommended patch release, not tied to a network upgrade. It corrects several Ethereum-style RPC methods (eth_call and eth_estimateGas now accept a from address that is a contract or not yet on-chain, and lookups of replaced transactions return null), makes StateWaitMsg wait for the confirmation depth a caller asks for, and replaces the Jaeger tracing exporter with an OpenTelemetry (OTLP) exporter.
- Implementation:changes shipped in Lotus v1.36.2
- Release:released 2026-07-27 as a recommended patch
- Activation:takes effect per node when operators upgrade; no network upgrade attached; adoption not observed
Source: filecoin-project/lotus — Lotus v1.36.2 (external site)
-
Flow described a fee recalibration expected to raise most fees 2 to 4 times
Flow described FLIP 370, which recalibrates execution-effort weights after finding the old model under-priced execution. Flow expects most transactions to pay roughly 2 to 4 times more and about 171,000 fewer FLOW to be minted per month, because staking rewards are paid from fees before new issuance.
- Proposal:FLIP 370 marked accepted in Flow's FLIP repository
- Implementation:flow-go v0.51.0 updates the node software's built-in mainnet weights to FLIP 370 values
- Release:flow-go v0.51.0 released for a mainnet height-coordinated upgrade dated 18 August 2026
- Activation:whether the fee weights charged on mainnet have switched was not confirmed
Sources: Flow Foundation — Transaction Fees Are Rising, FLOW Issuance Is Falling (external site) · onflow/flips repository — FLIP 370: Execution effort calibration III (external site) · onflow/flow-go repository — v0.51.0: 18th Aug 2026 - Height Coordinated Upgrade on Mainnet28 (external site)
-
Telos mainnet switched to Savanna finality
Telos announced that the switchtosvnn multisig executed at block 480,286,656 on 27 July 2026, moving mainnet to Savanna consensus. Active block producers now also run finalizers that vote with BLS keys, and Telos reported finalizer policy generation 1 with a threshold of 15, all 21 scheduled finalizers active, and the last irreversible block trailing the head by 2 blocks instead of about 330. The system contract used for the upgrade was deployed on 16 July and recorded as telos.contracts v1.8.0.
- Proposal:executed as an on-chain multisig proposal (switchtosvnn)
- Implementation:shipped in TelosZero Core and the v1.8.0 system contract
- Release:system contract deployed 2026-07-16
- Activation:active on mainnet since block 480,286,656 on 2026-07-27
Sources: Telos blog — Telos Lightspeed: Instant Finality is live (external site) · Telos Network (GitHub) — telos.contracts v1.8.0: Telos Instant Finality system contract (external site) · Telos blog — Project Lightspeed: Instant Finality Upgrade (external site) · Telos Foundation — Telos Zero chain API get_info (Telos Foundation endpoint) (external site)
-
B² documents its multi-signer price oracle for B² mainnet
B² added a developer guide for its oracle service, which publishes BTC, uBTC, WBTC, uniBTC and USDT prices on B² mainnet. A coordinator gathers median prices from four exchanges, and the on-chain contract accepts a new price only with valid signatures from at least 3 of 4 signers. Feeds are offered through Chainlink-style and Supra-style interfaces.
- Implementation:deployed per guide
- Release:documentation published with mainnet addresses
- Activation:contracts listed for chain ID 223
Sources: B² Network (GitHub) — Add B2 Oracle Service Guide (external site) · B² Network Documentation — Integrate B² Network Oracle Services (external site)
-
Akash node v2.1.1 released with an escrow fix and a new Pyth price verifier
Akash published node v2.1.1, a patch release on the v2.1 line. It changes the order in which the escrow module saves a closing account: related payments are now stored as closed before the account itself, because a market-module hook could otherwise see a closed account with a still-open payment and fail with an 'account closed' error. It also adds a CosmWasm verifier contract for Pyth's upgraded price messages, which checks signatures from a 3-of-5 quorum of Pyth router signers instead of Wormhole guardians. The release notes name no upgrade height or governance proposal.
- Implementation:escrow fix (pull request 2078, merged 2026-07-07) and Pyth router-signer verifier contract (pull request 2079, merged 2026-07-23)
- Release:released 2026-07-24; not a pre-release
- Activation:no upgrade height or proposal named; applies per node once installed; validator adoption and mainnet deployment of the verifier not checked
Sources: akash-network/node maintainers — Akash node v2.1.1 release (external site) · akash-network/node maintainers — fix(escrow): save closed payments before account hooks (external site) · akash-network/node maintainers — feat(contracts): add pyth pro verifier (external site) · akash-network/node maintainers — akash-network/node upgrades/software at tag v2.1.2 (external site) · Akash Network — Mainnet 18 upgrade guide (v2.1.0) (external site) · Polkachu public Akash REST node — Applied upgrade plan v2.1.0 (akashnet-2 chain state) (external site)
-
Gaia v27.6.0 released
Gaia v27.6.0 increased the maximum CosmWasm contract size, allowlisted selected governance and staking gRPC queries for CosmWasm, and updated wasmd/wasmvm dependencies.
- Release:Released
- Activation:not inferred from release alone
Source: cosmos/gaia maintainers — Gaia v27.6.0 release notes (external site)
-
ZEN staking opened on Horizen Mainnet
Following the DAO's approval of ZenIP 42408 in March 2026, Horizen opened ZEN staking on Horizen Mainnet, with reward distribution set to begin on 27 July 2026. Stakers bridge ZEN from Base via Stargate and need ETH for gas.
- Proposal:approved as ZenIP 42408
- Implementation:staking app live
- Release:Released
- Activation:rewards scheduled from 27 July 2026
Sources: Horizen Blog — How to Stake ZEN on Horizen Mainnet (external site) · Horizen Blog — $ZEN Staking is Back on Horizen (external site)
-
Legacy transactions disabled after the Zilliqa Ledger app nonce flaw was exploited
Zilliqa released a client hotfix at about 12:59 UTC on 20 July 2026, the day after KuCoin reported drained wallets; its hard fork took effect at block 31,759,109 at 16:37 UTC that day and stopped all legacy (non-EVM) transactions. The flaw in the Zilliqa Ledger app let anyone rebuild a key from four or more public signatures. Zilliqa's post-mortem, published 20 August, records 683,130,969.66 ZIL of proven theft from 51 accounts since 4 March 2026 and 6,772 exposed accounts, and says Zilliqa announced on 30 July that every legacy holder would move to EVM addresses.
- Implementation:client hotfix released about 12:59 UTC on 20 July 2026 (node release v0.21.7 published 12:45 UTC)
- Release:emergency hard fork; validators told to upgrade
- Activation:active since block 31,759,109 (16:37 UTC, 20 July 2026)
Sources: Zilliqa — Ledger Incident Hub (external site) · Zilliqa — Post-mortem: legacy Schnorr nonce bias (external site) · Zilliqa (GitHub) — zq2 v0.21.7 release (external site) · Zilliqa (zq2 repository, GitHub) — zilliqa/src/cfg.rs at tag v0.21.10 (external site) · Zilliqa (zq2 repository, GitHub) — zq2-mainnet chain specification at tag v0.21.10 (external site) · Blockscout (Zilliqa 2 mainnet instance) — Zilliqa Blockscout API: block 31,759,109 (external site)
-
MIP-12 cut Monad's block time to 300 ms
MIP-12 lowered the consensus vote pace from 400 ms to 300 ms and scaled block limits down to match: 150 million gas per block, with matching transaction and byte limits, and an 18 MON block reward, down from 25 MON. It activated on mainnet at round 89,758,000 on 23 July 2026, and the Foundation's post that day gives 600 ms finality.
- Proposal:MIP-12, created 1 June 2026, status Final
- Implementation:shipped in monad-bft v0.15.0 and v0.15.1
- Release:v0.15.1 set the mainnet activation round
- Activation:activated on mainnet 23 July 2026
Sources: Monad Foundation blog — Monad Mainnet now has 300ms block times and 600ms finality (external site) · Monad Improvement Proposals (Category Labs) — MIP-12: Decrease Block Time (external site) · Monad Documentation (Monad Foundation) — Releases (external site) · Category Labs (GitHub) — monad-bft v0.15.1 (MIP-12 mainnet activation) (external site)
-
SIMD-0553 resource and inclusion fee design was accepted
Accepted protocol proposal, not activation: SIMD-0553 specifies a base inclusion fee paid to the leader and a resource-based fee burned according to requested cost units. The proposal was merged on July 20; this record is dated by the changelog that reported it. Acceptance and repository merge do not prove implementation, feature-gate activation or Mainnet use.
- Stage:Proposal
Sources: Solana Foundation — Solana Changelog: July 23, 2026 (external site) · Solana Foundation and contributors — SIMD-0553: Resource and Inclusion Fee (external site)
-
Cairo v2.20.0 compiler release removed generated panic wrappers from the core library
StarkWare published version 2.20.0 of the Cairo compiler after three release candidates. It lets code read tuple elements with dot notation (t.0), accepts more constant expressions and recompiles faster after small edits. It also breaks some existing code: the core library no longer includes the wrapper functions generated by #[panic_with], such as u256_sub and array_at, and using the #[panic_with] attribute now produces a deprecation warning unless the project opts in.
- Implementation:released as a stable version after release candidates rc.0 to rc.2
- Release:v2.20.0 published on GitHub on 2026-07-23
- Activation:no network activation; applies when a developer compiles with this version
Sources: StarkWare (GitHub) — Cairo v2.20.0 (external site) · StarkWare (GitHub) — Releases: starkware-libs/cairo (external site)
-
Taiko published a postmortem of the June 2026 proof exploit
Taiko Labs described how an attacker used rogue debug-mode SGX provers and forged timestamps to trigger the open-proving fallback, finalize a fake Taiko state on Ethereum and withdraw about USD 1.75 million through the bridge on 21 and 22 June 2026. The bridge was paused for 10 days, refilled one for one from Taiko's own funds and reopened on 2 July.
- Implementation:debug-mode check added and fake checkpoints invalidated on 2026-06-29
- Release:postmortem published
- Activation:bridge reopened 2026-07-02
Source: Taiko Labs — Taiko Security Incident: A Postmortem and Next Steps (external site)
-
Aztec Labs reported about 370,000 AZTEC slashed for inactivity after the v5 upgrade
The v5 node software shipped with a 24-hour slashing grace period instead of the intended 7 days, because an earlier fix was never carried into the v5 branch. From 15 July, nodes voted to slash sequencers that were offline, mostly operators who had not yet upgraded. About 370,000 AZTEC was slashed; the slash veto council then paused further rounds, and Aztec Labs restored the defaults and added monitoring.
- Implementation:patched defaults released; QA process and monitors added
- Release:incident report published
- Activation:slash round 159 executed; rounds 160 to 180 paused by the veto council
-
B² reports unauthorized access to its B2 staking contract and suspends staking
B² said it had found a security incident in its B2 token staking service: someone had gained unauthorized access to the staking contract's upgrade authority. B² suspended B2 staking, said the issue was contained and promised to compensate affected users in full, with unstaking handled through support tickets. News reports put the loss at about 8.59 million B2, which the attacker sold on BNB Smart Chain.
- Implementation:incident reported by B²; staking suspended
- Release:not a protocol release
- Activation:suspension announced 22 July 2026; later status not verified
Sources: Metaverse Post — B² Network Suffers $3.86M Exploit, Offers Attacker Legal Immunity For Partial Refund (external site) · CoinDesk — Bitcoin, Ethereum-linked protocols lose $35 million in multiple attacks hours apart (external site)
-
Celo mainnet switched its execution client to op-reth
Celo mainnet moved from op-geth to op-reth on 22 July 2026, after Celo Sepolia on 24 June. Nodes still running op-geth will not be able to follow the canonical chain going forward.
- Implementation:Celo-compatible op-reth released
- Release:Released
- Activation:running on mainnet since 22 July 2026
Sources: Celo Forum (Celo Core Co.) — Celo Mainnet Is Now Running op-reth (external site) · Celo Documentation — Run a node (external site)
-
GIP-153 proposed turning Gnosis Chain into a rollup on Ethereum
GIP-153 proposed retiring the Gnosis Chain validator set and relaunching the chain as a rollup settling on Ethereum, first with interim proving likely based on trusted hardware and later with zero-knowledge proofs, while keeping xDAI as gas and users' addresses, balances and contract state. The GnosisDAO Snapshot vote closed on 19 August 2026 in favour (about 123,158 GNO for, 115 against); genesis is targeted for December 2026 or January 2027.
- Proposal:approved in a GnosisDAO Snapshot vote that closed on 2026-08-19
- Implementation:not confirmed in a primary source; the plan depends on Ethereum Economic Zone technology
- Release:not released
- Activation:not active; targeted December 2026 or January 2027
Sources: GnosisDAO forum — GIP-153: Should Gnosis Chain transition into the Ethereum Economic Zone? (external site) · GnosisDAO on Snapshot — GIP-153: Should Gnosis Chain transition into the Ethereum Economic Zone? (Snapshot vote) (external site) · Cointelegraph — GnosisDAO Approves Gnosis Chain for Ethereum Economic Zone (external site)