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 4 of 14.
One chain's developments, A to Z
-
Theta Labs announced its annual treasury unstake of 30 million THETA
Theta Labs said it would unstake 30 million of the 60 million THETA in its treasury (the post also mentions 15 million staked with Crypto.com) to fund enterprise validators, EdgeCloud, AI agents, academic partnerships, marketing, community grants and legal costs. It said this would cut its share of all staked THETA from about 48% to about 23%.
- Implementation:unstake announced
- Release:announced by Theta Labs
- Activation:Theta Labs' September 1 roundup says the unstake was carried out; not independently checked on chain
Sources: Theta Labs blog — Fueling 2026-2027 Growth: Annual Theta Validator Unstake (external site) · Theta Labs blog — Theta Roundup: August 2026 (external site) · Theta Labs — Theta Explorer API: all stake records (external site)
-
Zallet published beta.3
Zallet's beta.3 release continued the wallet replacement work after its July beta releases. The project still labels the wallet beta and warns that breaking changes and missing RPC methods remain possible.
- Stage:Release
Sources: Zcash developers — Zallet 0.1.0-beta.3 release (external site) · Zcash developers — Zallet wallet status and security warnings (external site)
-
Encrypted mempool framework initialised on mainnet in shadow mode
Governance executed a proposal that initialises the encrypted-mempool framework on mainnet and turns on its distributed key generation in shadow mode. Encrypted pending transactions hide a transaction's payload until it is ordered; the docs describe the feature as live on devnet and testnet with mainnet to follow.
- Proposal:AIP-144 marked Accepted
- Implementation:framework initialised; key generation running in shadow mode
- Release:delivered by governance proposal 204
- Activation:not available to users on mainnet as of 2026-09-27
Sources: Aptos Governance (Aptos Foundation) — Initialize Encrypted Mempool Framework and Enable ChunkyDKG Shadow V1 (external site) · Aptos Foundation AIPs — AIP-144: Encrypted Mempool (external site) · Aptos Docs — Encrypted Pending Transactions (external site) · Aptos Labs (public mainnet API) — Mainnet REST API: ledger information (external site)
-
Conflux v3.1.0 hard fork completed on mainnet
The v3.1 network upgrade, which nodes had to adopt before epoch 155,140,000, was reported complete on 25 August 2026. It adds Ethereum Osaka-era features to eSpace (a count-leading-zeros opcode and a secp256r1 signature precompile used by passkeys), bounds the ModExp precompile, requires canonical transaction encoding, fixes stake-dispute evidence checks and cross-space handling of set-code delegation, and includes a security fix whose details were withheld until after the upgrade.
- Proposal:CIPs 166, 167, 172, 173, 174, 175 and 176 bundled in the release
- Implementation:implemented in conflux-rust v3.1.0
- Release:v3.1.0 published 2026-08-10
- Activation:mainnet upgrade reported complete on 2026-08-25
Sources: Conflux Forum (Conflux team) — Conflux v3.1.0 Network Hardfork Upgrade Completed (Aug 25, 2026) (external site) · Conflux Forum (Conflux team) — Conflux v3.1.0 Network Hardfork Upgrade Announcement (Aug 3, 2026) (external site) · Conflux developers (Conflux-Chain) — conflux-rust v3.1.0 (external site) · Conflux documentation — Hard fork v3.1 (external site)
-
Post-incident report: a launch-era inflation bug was exploited on mainnet
The project's report says a bug in how consensus handled the regular and stake transaction trees together, present since launch, allowed inputs to be double-spent. It was reported through the bug bounty on 12 August 2026, exploited on mainnet between 16 and 17 August, and fixed in dcrd 2.1.6 on 18 August. About 2,078 DCR was created, and exchanges were asked to pause deposits and withdrawals while the chain was watched. Developers chose not to roll back the chain.
- Implementation:fix shipped in dcrd 2.1.6; double-spend watching service built; upgrade-signalling fields planned
- Release:report published 2026-08-25
- Activation:fix in force on upgraded nodes since 2026-08-18; no rollback
Sources: Decred blog — Decred Consensus Vulnerability: Post-Incident Report (external site) · Decred developers — dcrd v2.1.6 release notes (external site)
-
Lisk announces the Lisk Chain will shut down on 31 October 2026 and the Lisk DAO will wind down
Lisk announced that it is becoming a money operations platform for finance teams and that the Lisk Chain and the Lisk DAO are winding down, with the chain shutting down on 31 October 2026. A DAO proposal, described as proposed at announcement and passed by September, burned 100 million LSK (total supply from 400 million to 300 million), made unlocking penalty-free and moved the remaining treasury to Lisk Ltd; Lisk also says new staking is no longer possible. Celo Core Co. offers projects an optional migration path to the Celo network.
- Proposal:DAO proposal passed; vote dates and totals not read
- Implementation:staking contract updated per Lisk's DAO FAQ; burn reported done there but in progress in Lisk's token FAQ; chain still running at review
- Release:Announced
- Activation:chain shutdown scheduled for 31 October 2026; not yet reached at review
Sources: Lisk — Introducing the New Lisk (external site) · Lisk Support — DAO Cessation (FAQ) (external site) · Lisk Support — LSK Token (FAQ) (external site) · Lisk Support — Lisk Chain Closure (FAQ) (external site) · L2BEAT — Lisk (external site) · TechAfrica News — Lisk Pivots to Business Finance Platform, Plans Lisk Chain Shutdown (external site)
-
MIP-8 page-based storage (MONAD_TEN) activated on mainnet
Client release v0.16.1 set the MONAD_TEN revision, which carries MIP-8, to activate on mainnet at 14:30 UTC on 2 September 2026. MIP-8 groups contract storage into pages of 128 slots: the first access to a page is priced cold and the rest of the page is warm, and the state trie commits to pages. Node operators first ran both database layouts side by side and then dropped the old one.
- Proposal:MIP-8, created 5 March 2026, status Final
- Implementation:shipped in v0.16.0 (testnet) and v0.16.1 (mainnet activation)
- Release:v0.16.1 published 25 August 2026
- Activation:activated on mainnet 2 September 2026 at 14:30 UTC
Sources: Category Labs (GitHub) — monad-bft v0.16.1 (MONAD_TEN mainnet activation) (external site) · Monad Documentation (Monad Foundation) — Releases (external site) · Monad Improvement Proposals (Category Labs) — MIP-8: Page-ified Storage State (external site) · Monad Foundation blog — MIP-8: page-aware storage for the EVM (external site) · Monad Documentation (Monad Foundation) — MIP-8 Activation and Page Storage Migration (external site) · Monad Documentation (Monad Foundation) — Current Facts for AI Agents (external site)
-
Theta Edge Node left beta
Theta Labs announced that Edge Node, the software that lets a computer relay and cache video, transcode video and render 3D jobs for TFUEL, is now fully released rather than beta. AI workloads run through a separate EdgeCloud client, not Edge Node.
- Implementation:Released
- Release:full release announced
- Activation:available per Theta Labs; not tested in this review
Sources: Theta Labs blog — Theta Edge Node Enters Full Release (external site) · Theta Labs blog — Theta Roundup: August 2026 (external site)
-
Glamsterdam gas-repricing impact guidance identified contracts and tooling to retest
The Foundation reported that scheduled state-creation and state-access repricings could affect a small set of contracts and warned wallets, RPC infrastructure and node tooling to update gas-estimation assumptions. Testing guidance on Platåberget is not Mainnet activation.
- Type:Upgrade
- Proposal:Scheduled for inclusion
- Release:Testnet tooling guidance
- Activation:Testnet only not mainnet
Sources: Ethereum Foundation — Glamsterdam Repricing Impact for Smart Contract Developers (external site) · Ethereum Foundation — Announcing the Platåberget Testnet (external site) · Ethereum Improvement Proposals — EIP-7773: Hardfork Meta - Glamsterdam (external site)
-
Linea Besu v2.2.0 node package released on Besu 26.8.0
The Lineth project published version 2.2.0 of the Linea Besu package, the Besu execution client bundled with Linea's sequencer, tracer, state-recovery and Shomei plugins. The release adds support for custom liveness signers in Linea Besu, updates the bundled Besu client to 26.8.0, and tidies logging and image builds. It is a client release for node operators, not a network upgrade, and it was followed a month later by v2.3.0.
- Implementation:Custom liveness signer support and a Besu 26.8.0 update in the Linea Besu package
- Release:Linea Besu package v2.2.0 published on GitHub 24 August 2026, not marked pre-release; superseded by v2.3.0
- Activation:Not tied to a network activation; applies to a node when its operator installs it
Sources: Lineth (GitHub) — Linea Besu v2.2.0 (external site) · Lineth (GitHub) — lineth-monorepo releases (external site)
-
v3.20 resumed churn and switched on protocol-owned liquidity controls
THORNode v3.20 unblocked validator churn after more than 60 days, made the protocol-owned liquidity controls operational (nodes set 20% of system income to it), and shipped an experimental Stable Reserve for one-to-one stablecoin swaps, disabled by default. It also applied a residual ADR-028 remediation and added Zcash and Monero work that was not yet activated.
- Implementation:shipped in THORNode v3.20.0 (private binary), with patch releases through v3.20.3
- Release:v3.20.0 tagged 2026-08-19
- Activation:upgrade at block 27,580,000; churn and POL active; Stable Reserve disabled by default; Zcash and Monero not active in the 2026-09-29 read
Sources: THORChain blog — THORChain Protocol Upgrade v3.20 (external site) · THORChain (GitLab) — THORNode v3.20.0 release (external site) · THORChain blog — State of the Network - August 2026 (external site) · THORChain blog — How THORChain's New System Income Distribution Works (external site) · THORChain Midgard API, public endpoint run by Liquify — Midgard /v2/network via Liquify (read 2026-09-29) (external site) · THORNode API, public endpoint run by Liquify — THORNode /thorchain/inbound_addresses via Liquify (read 2026-09-29) (external site)
-
Forum staff described a 60-day late-claim process for unmigrated GLMR
Replying on Moonbeam's official forum, a staff moderator said holders who missed the deadline have 60 days to submit a late claim to the foundation helpdesk with address, amount and storage details, reviewed case by case, and warned that missing the window may mean permanent loss of access.
- Implementation:process described by staff
- Release:email-based review
- Activation:window start date not stated
Sources: Moonbeam Community Forum — Missed date for migration requirement (external site) · Moonbeam Foundation — GLMR and MOVR migration portal (external site)
-
BounceBit halts its chain after an exploit and says it will permanently sunset it
Between 21:02 UTC on 19 August and 01:54 UTC on 20 August 2026, an attacker used an authorization flaw in a vesting module inherited from Evmos to move about 286.5 million BB from nine accounts. Block production stopped at height 20,702,857 at 02:36 UTC on 20 August. On 21 August BounceBit said it would permanently sunset BounceBit Chain and reissue BB as a BEP-20 token on BNB Chain, using balances from block 20,697,260, just before the first unauthorized transfer.
- Implementation:block production halted at height 20,702,857 on 20 August 2026
- Release:announced by BounceBit on X; no notice on its website, docs, blog or Medium feed at review
- Activation:chain stopped; permanent sunset announced 21 August 2026
Sources: The Block — BounceBit to sunset blockchain, migrate to BNB Chain after $3 million exploit (external site) · Crypto Briefing — BounceBit shuts down chain after attacker moves 286.5 million BB (external site) · Crowdfund Insider — Bitcoin Restaking Platform BounceBit To Wind Down L1 Blockchain Following Exploit (external site) · BounceBit — BounceBit Blog (external site) · BounceBit — BounceBit posts on Medium (feed) (external site) · BounceBit — BounceBit website (external site)
-
Gaia v28.0.0 released
Gaia v28.0.0 removed the Interchain Security provider module and included an upgrade-handler parameter migration. The earlier Hub Unit notice described a public-testnet soak and a future mainnet software-upgrade proposal, so the binary release is not presented as Hub activation.
- Release:Released
- Activation:mainnet activation not established; governance proposal and upgrade height require separate evidence
Sources: cosmos/gaia maintainers — Gaia v28.0.0 release notes (external site) · Cosmos Hub Unit — Advance notice: Gaia v28.0.0 ICS provider module removal (external site)
-
Mesa pre-fork releases gave mainnet node operators a manual and an automatic upgrade path
On 21 August 2026 o1Labs published two mainnet node releases for the Mesa hard fork, with a blog post listing operators' tasks. Operators had to install one of them before the stop-transaction slot at 10:00 UTC on 3 September. Version 3.5.0-mainnet-stop-slot is the manual path: from that slot upgraded nodes produce only empty blocks, block production halts at 15:00 UTC, and the operator then installs the separate Mesa release and restarts. Version 4.0.0-mainnet (automode) is the automatic path: it carries the Mesa software and switches the node over by itself at the halt. The Mesa network was scheduled to start at 18:00 UTC the same day. Devnet had gone through the same sequence on 19 August.
- Proposal:MIP6 to MIP9 approved in the December 2025 on-chain vote
- Implementation:Mesa implemented in daemon 4.0.0; 3.5.0 is the pre-fork build that sets the stop slots for the manual path
- Release:3.5.0-mainnet-stop-slot and 4.0.0-mainnet published 2026-08-21; the manual-path Mesa release 4.0.0-mainnet-mesa followed on 2026-09-03
- Activation:not an activation; Mesa went live on mainnet on 2026-09-03, recorded separately in mesa-hard-fork-mainnet-2026-09
Sources: MinaProtocol/mina maintainers (o1Labs) — Mina Mainnet 3.5.0 Stop Slot Release (external site) · MinaProtocol/mina maintainers (o1Labs) — Mina Mainnet 4.0.0 Automode Upgrade Release (external site) · Mina Protocol blog — Mesa MAINNET Upgrade: Timelines and Operators' Tasks (external site) · Mina documentation — Mesa Fork Schedule (external site)
-
ArbOS 61 Elara activated on Arbitrum One
Official documentation records governance approval and activation at 17:00 UTC, with One-specific minimum-base-fee management and a 96 KB Stylus limit. Priority-fee collection, compliance filtering and AltDA were not enabled on One by this activation.
- Type:Upgrade
- Proposal:Governance approved
- Release:Released
- Activation:Activated mainnet
Sources: Arbitrum Foundation — ArbOS Elara: Compliance Filtering, Priority Fee Support (external site) · Arbitrum Documentation — ArbOS 61 Elara (external site)
-
Arbitrum described a roadmap toward ZK settlement
An official Arbitrum blog post with an individual author byline described engineering milestones and said Offchain Labs would bring a future DAO proposal, which would be required to upgrade Arbitrum One. Roadmap publication is not production activation.
- Type:Roadmap
- Proposal:Roadmap before dao proposal
- Release:Not established
- Activation:Not active from this evidence
Source: Arbitrum Foundation — ZK Settlement is Coming to Arbitrum (external site)
-
Isthmus and Jovian scheduled on Boba Sepolia; mainnet not yet scheduled
Boba set the Isthmus upgrade, which also brings the Prague EVM changes, for Boba Sepolia on 20 August 2026 and Jovian for 25 August 2026. Boba Mainnet dates were not yet scheduled at review time.
- Implementation:op-reth v2.3.1 and op-node v1.19.0 required
- Release:released for testnet
- Activation:scheduled on Boba Sepolia for 2026-08-20 and 2026-08-25; mainnet not scheduled
Source: Boba Network Docs — Preparing for Isthmus and Jovian breaking changes (external site)
-
HONEY stablecoin renamed Bera USD (BUSD)
Berachain changed its stablecoin's name and symbol from HONEY to Bera USD (BUSD) on 19 August 2026. The contract address stayed the same, so balances, approvals and integrations carried over with no migration, swap or claim.
- Implementation:name and symbol changed at the existing contract
- Release:Done
- Activation:effective 2026-08-19
Sources: Berachain docs — BUSD Token (external site) · Berachain docs — Frequently Asked Questions (external site)
-
Movement published a guide to using Ledger devices with the Motion wallet
Movement's guide explains importing Ledger accounts into Motion and signing Movement transactions with the Ledger Aptos app, noting that Motion requires blind signing so the device may show only a transaction hash.
- Implementation:guide published
- Release:available per Movement's guide
- Activation:Motion's homepage still lists hardware support as on the way; not tested here
Sources: Movement Network — How to Use Ledger with Motion Wallet (external site) · Movement Network — Motion Wallet (external site) · Ledger — Aptos Wallet (external site)
-
Ravencoin Core 4.8.0 fixed a KAWPOW header flaw exploited from 7 August 2026
Release 4.8.0 requires, from block 4,487,776, that the height declared inside a KAWPOW header match the block's real height, and adds a checkpoint at block 4,487,775. The release notes say the flaw let a miner bypass the DAG and GPU requirements and stopped nodes from syncing or restarting. According to 2Miners, pools rebuilt the chain from the last clean block after finding 96 forged blocks, replacing about three days of history.
- Implementation:fix published as pull request 1289 on 18 August 2026
- Release:Ravencoin Core 4.8.0 released 19 August 2026; 2Miners says it distributed a patched build on 10 August
- Activation:header check enforced by upgraded nodes from block 4,487,776
Sources: RavenProject — V4.8.0 Core Release: Patch 2 major bugs (external site) · RavenProject — V4p8p0: fix the DAG/GPU-bypass mining bug (pull request 1289) (external site) · 2Miners — August 2026 Work Progress: Ravencoin Chain Rescue, Pearl Hard Fork, and Kaspa Reward Cut (external site) · blockbook.ravencoin.org — Blockbook: Ravencoin block 4,487,775 (external site) · blockbook.ravencoin.org — Blockbook: Ravencoin block 4,487,776 (external site) · RavenProject — Ravencoin Core chainparams.cpp (develop) (external site)
-
Community continuance proposal passed, minting new SCRT to fund the chain
Proposal 365 passed on 19 August 2026, scheduling the 1.26.0 community continuance upgrade at height 26,790,327. The plan keeps the existing chain, creates a new stewardship entity, and funds it, core development, validators, relayers, builders and bridge exploit victims with a large new mint and a fixed 5% inflation rate. The upgrade was later applied at that height.
- Proposal:passed on chain
- Implementation:upgrade released from the community repository
- Release:v1.26.0-community-continuance published 2026-08-20
- Activation:applied at height 26,790,327
Sources: Secret Network governance (public REST endpoint) — Proposal 365: Community Continuance of Secret Network (L1) (external site) · Lavender.Five Nodes public endpoint — Applied upgrade plan v1.26.0-community-continuance (public REST endpoint) (external site) · Secret3dev on GitHub — v1.26.0-community-continuance release (external site) · Secret Network Forum (Secret Network Foundation post) — Secret^3: Community Continuance of Secret Network L1 (external site) · Lavender.Five Nodes public endpoint — Total uscrt supply (public REST endpoint) (external site) · Lavender.Five Nodes public endpoint — Current inflation (public REST endpoint) (external site)
-
dcrd 2.1.6 ships an emergency fix for a consensus vulnerability
dcrd 2.1.6 fixed a critical consensus-related vulnerability and told everyone to upgrade or risk being forked off the network. It also fixed a possible periodic deanonymisation attack on mixing and several denial-of-service issues.
- Implementation:shipped in dcrd 2.1.6
- Release:stable release published 2026-08-18
- Activation:tightened rules enforced by upgraded nodes immediately; not a ticket-holder vote
Sources: Decred developers — dcrd v2.1.6 release notes (external site) · Decred developers — Decred binary releases (dcrd, dcrwallet, Decrediton) (external site) · Decred blog — Decred Consensus Vulnerability: Post-Incident Report (external site) · Decred developers (GitHub) — dcrd releases (Atom feed) (external site)
-
Report on the July 2026 peer-message flood: ledger kept validating
An incident report described a flood of junk validator manifest messages that began on the evening of 30 July 2026 and caused mass peer disconnects across the network, including at two default-list validators. The report says the ledger never halted or forked, no funds or keys were affected, and a 3.2.1 hotfix limiting manifest sizes and caches was released on 31 July, with limits adjusted in 3.3.0.
- Implementation:manifest size, per-message and cache limits added to the reference server
- Release:3.2.1 hotfix released 2026-07-31; limits loosened in 3.3.0 the following week
- Activation:server software change, effective as each operator upgrades; the report describes no amendment
Source: XRP Ledger blog (xrpl.org) — Vulnerability Disclosure Report: XRPL Manifest Flood (external site)
-
Abstract's Ethereum contracts moved to ZK Stack protocol version 0.30.1 with new proof verifiers
L2BEAT recorded three upgrades of Abstract's main contract on Ethereum in August 2026, moving it to protocol version 0.29.5 (4 August), 0.30.0 (8 August) and 0.30.1 (16 August), each with new Boojum proof verifiers. L2BEAT names Abstract's multisig as applying the last two, describes the first two verifier sets as the same as ZKsync Era's, and says the 0.30.1 verifiers had been registered in the shared ZK Stack contracts beforehand. For each upgrade L2BEAT noted that the new verifiers had not yet been reproduced.
- Implementation:applied to Abstract's contracts on Ethereum mainnet
- Release:protocol version 0.30.1 recorded by L2BEAT
- Activation:active since 2026-08-16 per L2BEAT's contract record
Sources: L2BEAT — Abstract (external site) · Abstract Foundation (GitHub) — abstract-node releases (external site)
-
Traffic-based app rewards (CIP-0104) not activated on MainNet; no new date set
The Canton Foundation said traffic-based app rewards would not go live on MainNet on 18 August 2026 because the on-chain proposal combining the supporting Daml models with activation was not approved. The notice said the models would instead be enabled on 18 August and Super Validators would gain a voting interface for featured-app weights, while activation awaits further governance with no revised date.
- Proposal:CIP-0104 approved on 2026-02-12
- Implementation:supporting Daml models scheduled to be enabled on MainNet on 18 August 2026, per the 17 August notice
- Release:shipped in Splice; the combined activation proposal was not approved
- Activation:not active on MainNet as of the 17 August 2026 notice; no revised date
Sources: Canton Network Forum (Announcements) — CIP-0104 MainNet Go-Live Update (external site) · Canton Foundation (CIPs repository) — CIP-0104: Traffic-Based App Rewards (external site) · Canton Network Docs — Canton Coin Tokenomics (external site)
-
A public short-term Glamsterdam testnet was announced
The Foundation announced Platåberget for post-Glamsterdam experimentation and warned about tooling with hard-coded gas limits. A testnet announcement is not Mainnet activation.
- Type:Testnet
- Proposal:Selected for testing
- Release:Testnet
- Activation:Testnet announced not mainnet
Sources: Ethereum Foundation — Announcing the Platåberget Testnet (external site) · ethereum.org community — Glamsterdam (external site)
-
Node release v2026.08 adds collators to Catchain 2.0
TON's v2026.08 node release added collators to its Simplex-based consensus, letting specialized nodes build blocks on behalf of validators, along with better node metrics and stability fixes.
- Implementation:implemented in node software
- Release:released 2026-08-17
- Activation:mainnet use not verified
Sources: ton-blockchain maintainers — TON v2026.08 release notes (external site) · ton-blockchain maintainers — TON releases (external site)
-
WAX plans to cut active guilds from ten to seven and standbys from six to three
WAX said that from September 2026 the number of active block-producing guilds would fall from ten to seven and standby guilds from six to three, and that its enhanced API provider program would shrink to three lead infrastructure providers offering full Hyperion history, AtomicAssets and Light APIs, while every guild keeps providing chain RPC APIs. WAX gave cost pressure on operators as the reason and said Office of Inspector General seats are also being restructured.
- Proposal:announced plan
- Implementation:the system contract lets the eosio account change the active guild count one step at a time, with a cooldown that defaults to one day (feature listed in wax-3.2.0)
- Release:no software release; a parameter change
- Activation:incomplete or in progress: the 2026-09-29 schedule listed eight active guilds
Sources: WAX (wax-io.medium.com) — WAX.io blog feed (external site) · Greymass (public WAX API node) — WAX Chain API get_producer_schedule via wax.greymass.com (external site) · WAX (wax-system-contracts GitHub) — WAX extensions to eosio.system: architecture overview (external site) · AntelopeIO (docs GitHub repository) — Antelope Consensus Protocol (external site)
-
Dogecoin Core development branch caps inbound peers per network subnet
A change merged into Dogecoin Core's master branch limits how many inbound connections a node accepts from the same public network range, so a node's peers come from more varied networks. It is not in any release yet.
- Proposal:pull request 4036
- Implementation:merged into the development branch
- Release:not in any release (latest release 1.14.9)
- Activation:no activation needed; applies only to nodes running a future release that includes it
Sources: Dogecoin Core developers — Improve inbound peer diversity/limit subnet conns, pull request 4036 (external site) · Dogecoin Core developers — Dogecoin Core releases (external site)
-
Harmony rolls back to 11 August after an exploit and restarts on 20 August
After an exploit that the migration FAQ later called a forge-mint incident, Harmony released v2026.1.2, which rejects the abandoned blocks and known malicious blocks by hash and adds safeguards for an emergency restart. Validators replaced their databases with a clean copy ending at shard 0 block 92,730,034 and shard 1 block 94,978,278 and restarted on a coordinated signal, running v2026.1.3. On-chain timestamps show the next canonical shard-0 block at 13:51:41 UTC on 20 August 2026.
- Implementation:rollback executed
- Release:v2026.1.2 on 2026-08-15, v2026.1.3 on 2026-08-19
- Activation:chain restarted 2026-08-20
Sources: Harmony (GitHub) — Mainnet Release 2026.1.2 (external site) · Harmony (GitHub) — Reject abandoned branch hashes (#5106) (external site) · Harmony (GitHub, rollback-92730034 branch) — Node operator rollback guide (external site) · Harmony (GitHub, rollback-92730034 branch) — Validator rollout notes: shard-0 clean-database recovery (external site) · Harmony — Harmony shard 0 public RPC (external site) · harmony-migration repository (polymorpher) — Harmony migration user FAQ (external site)
-
Proposal to finalise Mint and Lend parameters and extend claims is rejected (proposal 221)
Proposal 221, the second phase of the wind-down, would have finalised the Mint and Lend parameter changes, aligned limits on deprecated markets and extended the incentive claim deadline to 31 December 2026. Voting closed on 15 August 2026 with about 45 million KAVA voting no and about 22 million no with veto, against about 0.13 million yes.
- Proposal:Rejected
- Implementation:not applied
- Release:no software release involved
- Activation:not activated
-
Pasteur hard fork scheduled and then activated on BSC mainnet
BNB Chain announced the Pasteur hard fork for 25 August 2026 at 02:30 UTC with client v1.7.7. It lets builders hand validators pre-executed blocks so validators skip a second execution pass (BEP-675), rejects duplicate validators in bridge signature checks (BEP-682) and makes rotated validator keys lose privileges while still facing pending slashes (BEP-695). A 14 September post confirmed it went live on 25 August.
- Proposal:BEP-673 meta proposal with BEP-675, BEP-682 and BEP-695
- Implementation:shipped in client v1.7.7
- Release:mandatory mainnet release
- Activation:activated on mainnet 2026-08-25 02:30 UTC
Sources: BNB Chain Blog — Pasteur Hardfork Arrives on BSC Mainnet on August 25 (external site) · BNB Chain Docs — Pasteur Upgrade of BSC (external site) · BNB Chain (GitHub) — bsc v1.7.7 (Pasteur hardfork) (external site) · BNB Chain Blog — Post-Pasteur Hard Fork: BSC Packs 28% More Gas Per Block With More Scale Ahead (external site)
-
Governance appointed Solva as Neutron's security-only maintainer
Proposal 4, submitted 14 August and passed 21 August 2026, appointed Solva as security maintainer for up to 12 months, recognised solva-solutions/neutron as the canonical patch repository and funded a capped allocation from the community pool. The first patch under the mandate, v11.2.0, was applied at height 61317700 around 27 August 2026.
- Proposal:proposal 4 passed 2026-08-21
- Implementation:mandate active
- Release:v11.2.0 released 2026-08-24; v11.2.1 on 2026-09-07
- Activation:v11.2.0 applied at height 61317700
Sources: Neutron on-chain governance (via Solva REST endpoint) — Governance proposal 4: Neutron Security Maintenance Mandate (external site) · Solva — Proposal: Neutron Long-Term Security Maintenance Mandate and 12-Month Funding (external site) · Solva — Neutron v11.2.0 release (external site) · Solva — solva-solutions/neutron (canonical maintenance repository) (external site)
-
Validator instructions and mainnet validator configuration published
Plasma's node templates v1.0.0 added instructions and configuration for running a validator on devnet, testnet and mainnet: generating a BLS12-381 keystore, setting a fee recipient and switching the node role. The templates say this does not place a node in the active validator set; enrolment still needs the Plasma team.
- Implementation:validator templates published
- Release:released 2026-08-14
- Activation:no open enrolment; validators join through the Plasma team
Sources: Plasma (PlasmaLaboratories, GitHub) — node-templates v1.0.0 release (external site) · Plasma (PlasmaLaboratories, GitHub) — Plasma Node Templates README (external site) · Plasma Docs — Tokenomics (external site)
-
Spark multi-input forgery bug disclosed and temporarily mitigated
Firo disclosed a bug that could let multi-input Spark transactions forge coins, reported on 1 August 2026. Version 0.14.17.2 limited Spark spends to a single input until a permanent fix. Firo said it found no inflation beyond about 200 FIRO created by the researcher to prove the issue.
- Implementation:single-input restriction shipped in v0.14.17.2
- Release:v0.14.17.2 released 2026-08-13
- Activation:restriction in effect until the September 2026 fork
Sources: Firo — Spark vulnerability mitigated (external site) · Firo developers (firoorg) — Firo releases (external site) · Firo developers (firoorg) — Firo v0.14.17.2 (GitHub release) (external site)
-
Algorand 5.0.0 consensus upgrade added post-quantum accounts and size-based fees
go-algorand 5.0.0 shipped a consensus upgrade with native Falcon-1024 accounts, a per-byte surcharge for oversized notes, arguments, programs and logic signatures, larger apps and AVM version 13. The Foundation reported that the upgrade reached its 90% support threshold on 15 August 2026, followed by a wait of about a week. Block headers read from a public mainnet node show the new protocol version taking effect at round 64,318,659 on 22 August 2026 (UTC).
- Proposal:approved by block-proposer upgrade vote, per the Foundation
- Implementation:released in go-algorand 5.0.0, followed by patch releases 5.0.1 and 5.0.2
- Release:5.0.0 stable released 2026-08-12
- Activation:active on mainnet since round 64,318,659 (2026-08-22 17:43 UTC), per public-node block headers matched to consensus version 42
Sources: algorand/go-algorand maintainers — Algorand 5.0.0 release notes (external site) · Algorand Foundation — Getting ahead of the (elliptic) curve: what's in the next consensus upgrade (external site) · Algorand Foundation — Algorand v5.0.0 is here. Here's what it means for you. (external site) · algorand/go-algorand maintainers — go-algorand protocol/consensus.go (external site) · Nodely — Mainnet block 64,318,659 header (Nodely public algod) (external site) · algorand/go-algorand maintainers — algorand/go-algorand releases (external site)
-
Nitro v3.11.3 was released for ArbOS 61 operators
Offchain Labs published Nitro v3.11.3 on GitHub on August 12 (its release notes carry an August 3 version date), and the ArbOS 61 documentation identifies it as the minimum mandatory version for Arbitrum One and Nova node operators ahead of Elara activation. The client release alone is not activation evidence.
- Type:Release
- Proposal:Not applicable
- Release:Released
- Activation:Not established by release
Sources: Offchain Labs — Arbitrum Nitro v3.11.3 (external site) · Arbitrum Documentation — ArbOS 61 Elara (external site)
-
Runtime 2300 moved Astar to Polkadot SDK stable2512 and lowered the collator minimum to 1
Referendum 60 enacted runtime 2300, which moves Astar's runtime to the Polkadot SDK and Frontier stable2512 line, sets the relay parent offset to 0 and reduces the minimum number of collator candidates from 5 to 1. Collators and RPC nodes had to run client v5.50.0 alongside it.
- Proposal:passed as referendum 60
- Implementation:shipped in runtime 2300 with client v5.50.0
- Release:released 2026-07-28 (runtime) and 2026-07-30 (client)
- Activation:enacted on Astar mainnet on 2026-08-12
Sources: Subsquare (Astar democracy) — Referendum 60: Runtime upgrade to 2300 (Polkadot SDK stable2512) (external site) · Astar Network (GitHub) — runtime-2300 release notes (external site) · Astar Network (GitHub) — v5.50.0 client release notes (external site) · Astar Docs — Learn about Collators (external site)
-
Grin wallet 5.5.0 adds a built-in Tor client and mixing APIs
grin-wallet v5.5.0 integrates the Arti Tor client, exposes interfaces for the experimental mwixnet mixing service, resumes and speeds up output scanning, and fixes Slatepack address handling. It followed node v5.5.1 on 2026-08-11, which updated TLS and HTTP dependencies and switched the terminal interface backend.
- Implementation:shipped in wallet v5.5.0 and node v5.5.1
- Release:stable releases published 2026-08-11 and 2026-08-12
- Activation:no consensus change; takes effect as users upgrade
Sources: GitHub API (mimblewimble/grin-wallet) — Grin wallet release records (external site) · GitHub API (mimblewimble/grin-wallet) — Grin wallet commits between v5.4.1 and v5.5.0 (external site) · GitHub API (mimblewimble/grin) — Grin v5.5.1 release record (external site) · GitHub API (mimblewimble/grin) — Grin commits between v5.5.0 and v5.5.1 (external site)
-
Harmony v2026.1.1 fixes cross-shard receipt replay and a quorum-counting flaw
Harmony published node release v2026.1.1, whose only listed change is pull request 5101. Its commits fix two flaws. The signature check used for committees from before staking began counted every committee member instead of the members who actually signed, so a block with no signers and an empty signature could pass as having a quorum. And for receipts from blocks older than an earlier replay fix, the marker that records a cross-shard receipt as already used was built from unsigned fields, so a genuine receipt could be resubmitted with altered details and credited again on the receiving shard with no matching debit on the sending shard. The release notes do not call the upgrade mandatory and set no activation epoch.
- Implementation:fixes merged 2026-08-12 in pull request 5101
- Release:v2026.1.1 published 2026-08-12
- Activation:no hard fork or activation epoch stated; applied on nodes that installed it; uptake not verified
Sources: Harmony (GitHub) — Mainnet Release 2026.1.1 (external site) · Harmony (GitHub) — Cx receipt fixes main (#5101) (external site) · Harmony — Harmony shard 0 public RPC (external site) · Harmony (GitHub, rollback-92730034 branch) — Validator rollout notes: shard-0 clean-database recovery (external site) · The Block — Harmony to fully sunset Layer 1, proposes token migration to Ethereum for AI video initiative (external site)
-
Elements 29.4.1 release candidate tagged for testing; no final 29.x release yet
The Elements project published a signed elements-29.4.1rc1 tag on 12 August 2026. It is a release candidate, not a final release, and GitHub shows no release notes for it. Blockstream's May 2026 roadmap said Elements had reached parity with Bitcoin Core 29, aimed for a release candidate by July 2026 and left the final release to Technology Board and federation review. As of 27 September 2026 the latest final release was still 23.3.4 from the 23.x line.
- Proposal:on the May 2026 roadmap with a July 2026 release-candidate goal
- Implementation:release candidate 29.4.1rc1 tagged on 12 August 2026
- Release:release candidate only; no final 29.x release as of 27 September 2026
- Activation:none confirmed; final release subject to Technology Board and federation review
Sources: ElementsProject (GitHub) — elements-29.4.1rc1 (external site) · ElementsProject (GitHub) — Elements releases (external site) · The Liquid Blog — Blockstream Shares Liquid Development Roadmap: 0-Conf, PQ Readiness, BitVM & More (external site)
-
Base released a hinted-P384 design for onchain AWS Nitro validation
Base published an open-source redesign that moves expensive P-384 inversions offchain as checked calldata hints and reported Base measurements below the per-transaction gas cap. The post says use in the canonical bridge proofs system is planned; this record does not claim that migration has occurred.
- Type:Release
- Proposal:Not applicable
- Release:Open source library released
- Activation:Canonical bridge use planned not observed
Source: Base Engineering Team — Making AWS Nitro Validation feasible onchain (external site)
-
stacks-core 4.0.2 node and signer release
A maintenance release of the Stacks node and signer software that works with existing 4.0.x chainstate. Miners must now name an existing Bitcoin Core wallet in their configuration, a change the notes tie to Bitcoin Core 31 and later. It also cuts Clarity memory use, makes signers reject unknown configuration fields, and carries two contract-rule fixes that apply only from a later Epoch 4.1.
- Implementation:Released
- Release:stable release 4.0.2; optional but recommended
- Activation:no network activation; its Epoch 4.1-gated fixes wait for an activation height the notes do not give
Sources: Stacks core contributors (GitHub) — stacks-core release 4.0.2 (external site) · Stacks core contributors (GitHub) — stacks-core releases (Atom feed) (external site)
-
Akash published a draft plan to leave its sovereign chain
Migration documents for AEP-79 (draft version 0.9) describe winding down akashnet-2 and re-implementing the marketplace on Solana or on an existing Ethereum layer 2, with balances reissued through claims signed by existing keys. The target is to be chosen at a decision gate that includes a community signal vote; no dates are set.
- Proposal:AEP-79 marked final as a request for proposals; migration documents are a draft
- Implementation:only target-neutral preparation is allowed before the first decision gate; no signal proposal on chain through proposal 341
- Release:None
- Activation:no cutover date set
Sources: akash-network/AEP maintainers — AEP-79 migration docs: rollout and cutover (external site) · akash-network/AEP maintainers — AEP-79 migration docs: executive summary (external site) · akash-network/AEP maintainers — AEP-79 migration docs: target selection (external site) · Akash Network — AEP-79: Akash on Shared Security (external site) · Polkachu public Akash REST node — Most recent governance proposals (akashnet-2 chain state) (external site)
-
ICF published its Q3 2026 ATOM delegation selections
The Interchain Foundation published the Q3 adjustment for its ATOM delegation program, including selected validators, ecosystem-growth recipients, and updated qualification criteria. This is a foundation delegation program, not Cosmos Hub consensus or a protocol activation.
- Release:published program update
- Activation:not a Cosmos Hub protocol activation
Sources: Interchain Foundation — ICF Delegation Program: Q3 Selected Validators (external site) · Interchain Foundation — Interchain Foundation Medium RSS (external site)
-
Noble v11.6.0 closes all Noble Swap pools
Release v11.6.0 closed every Noble Swap pool through its upgrade handler, claiming accrued yield and protocol fees, and updated the swap module so that remaining unbondings are processed only by the upgrade. An on-chain query on 27 September 2026 showed the remaining pool with no liquidity shares.
- Implementation:released as v11.6.0
- Release:released 2026-08-10
- Activation:running on a public mainnet node on 2026-09-27; activation height not verified
Sources: noble-assets/noble maintainers — Noble v11.6.0 release notes (external site) · Noble on-chain state via Noble public REST endpoint — Noble Swap pools (on-chain query) (external site) · Noble public REST endpoint — Noble node software version (on-chain query) (external site)
-
Aztec disclosed a critical flaw in the v5 proving system; fix planned for v6
Core contributors found on 27 July 2026, through internal AI-assisted auditing, that an attacker might build a proof that passes verification for a transaction the network should reject. Aztec said v5 funds, apps and contract state are at risk, that it cannot tell whether the flaw was exploited, and that the fix will come in v6 with circuit changes that reject proofs from the affected system. Apps were told to prepare safeguards and pause v5 deployments.
- Implementation:fix planned for v6
- Release:disclosure published; v6.0.0 release-candidate tag dated 23 September 2026, no v6 release published
- Activation:not yet activated
Sources: Aztec — Alpha V5 Proving System Vulnerability (external site) · AztecProtocol on GitHub — aztec-packages releases (external site) · AztecProtocol on GitHub — v6.0.0-rc.1 tag (external site) · Aztec Documentation — Networks (external site) · L2BEAT — Aztec Network (external site)
-
Node patch 9.0.4 fixes gas estimation and Import Sync
Rootstock published version 9.0.4 of RSKj as an optional patch in the Vetiver line. It stops eth_estimateGas from using the gas amount supplied by the caller as the simulation budget, repairs the Import Sync feature, fixes handling of invalid ports and adds logging for monitoring federation (peg signer set) changes, along with security and performance work the notes do not itemize. Rootstock recommends that node operators upgrade.
- Implementation:released as RSKj 9.0.4
- Release:optional patch release; upgrade recommended for node operators
- Activation:no network activation; changes apply when an operator installs the release
Sources: Rootstock — Vetiver 9.0.4: Patch Release (external site) · Rootstock (GitHub) — RSK Vetiver Release 9.0.4 (external site) · Rootstock (GitHub) — Release notes from rskj (external site)
-
v4.4.0 brought Cosmos SDK v0.53.8 security fixes to Babylon through a coordinated upgrade
Node release v4.4.0 moved Babylon to Cosmos SDK v0.53.8 and wasmd v0.60.5, both listed as state-breaking in the change log. Its v4.4 upgrade handler changes no state; the code says it exists to coordinate the binary swap for the SDK security release. The Cosmos SDK team had published v0.53.8 on 27 July 2026 with fixes to transaction signing, signer and multisig checks and public-key validation, and asked chains to adopt it through a coordinated upgrade.
- Proposal:expedited software-upgrade vote in August 2026, per the on-chain proposals list read earlier on 27 September 2026
- Implementation:Cosmos SDK v0.53.8 and wasmd v0.60.5; upgrade handler makes no state changes
- Release:released as v4.4.0 on GitHub on 6 August 2026; latest GitHub release at review
- Activation:mainnet upgrade described in the governance record; activation height not re-checked in this pass
Sources: Babylon Labs — babylon v4.4.0 release (external site) · Babylon Labs — Babylon node CHANGELOG at tag v4.4.0 (external site) · Babylon Labs — v4.4 upgrade handler source (external site) · Babylon Labs — babylon go.mod at tag v4.4.0 (external site) · Cosmos SDK maintainers (cosmos/cosmos-sdk) — Cosmos SDK v0.53.8 release (external site) · Polkachu public REST endpoint for bbn-1 — Babylon governance proposals list (on-chain query) (external site)