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 6 of 14.
One chain's developments, A to Z
-
Consensus node release v0.75 reached Hedera mainnet
Hedera's release notes record v0.75 on mainnet on 22 July 2026, after testnet on 25 June 2026. The notes list work on moving node output to block streams, including block-stream cutover logic and wrapped record blocks, alongside record-file alignment changes.
- Proposal:HIP-1056 block streams approved
- Implementation:cutover logic included in v0.75
- Release:released; testnet 2026-06-25, mainnet 2026-07-22
- Activation:effect on downstream stream consumers not confirmed
Sources: Hedera documentation — Consensus node release notes (external site) · Hiero improvement proposals — HIP-1056: Block streams (external site)
-
Ink's sequencer operations moved from Gelato to the Optimism Foundation
An OP Labs proposal on Optimism's governance forum said Ink was moving its sequencer operations from Gelato to the Optimism Foundation as chain servicer through OP Enterprise, a service OP Labs operates, with cutover targeted for 28 July 2026, and asked approval for two follow-up changes: rotating a fallback proposer key and redirecting two fee vaults. L2BEAT's change log shows the batcher and block-signing keys rotating on 30 July and the proposer key on 10 August 2026.
- Proposal:maintenance upgrade proposal posted 2026-07-22 under the standard veto period
- Implementation:operator keys rotated, per L2BEAT
- Release:not a software release
- Activation:cutover targeted for 2026-07-28; batcher and block-signing keys rotated 2026-07-30 and proposer key 2026-08-10, per L2BEAT
Sources: Optimism Collective governance forum — Maintenance Upgrade Proposal: Ink Mainnet Fee Vault Config Update and Proposer Rotation (external site) · L2BEAT — Ink (external site)
-
Blockstream's 0-conf visibility service for Liquid announced as available
Blockstream described a hosted service that reports how widely an unconfirmed Liquid transaction has spread across observing nodes, so merchants and apps can decide whether to accept a payment before it confirms. The service reports visibility only and does not guarantee confirmation.
- Implementation:hosted service operated by Blockstream
- Release:available after a beta with federation members
- Activation:not a consensus change
Sources: The Liquid Blog — 0-Conf for Elements and Liquid: A Technical Explainer (external site) · Liquid Developer Documentation (Blockstream) — 0-Conf Service (external site)
-
Qtum Core v30.2 released
Qtum Core v30.2 rebased the node on Bitcoin Core 30.2. The notes list faster start-up by loading and verifying snapshots of the unspent-output set, encrypted peer connections as an option, the move to Qt 6 and wallets that must use the newer descriptor format. The release is not labelled a hard fork.
- Implementation:Released
- Release:released 2026-07-22
- Activation:no activation height stated
Source: Qtum project — Qtum Core v30.2 - Upgrade to bitcoin core v30.2 (external site)
-
Aztec's v5 upgrade went live after a token-holder vote, as a hard fork with new addresses
The v5 upgrade (AZUP-2) passed sequencer signalling and a token-holder vote and became the canonical rollup. Aztec reported private transfers proving about twice as fast, transaction costs roughly halved, and average block time cut from about 14 to 6 seconds. It was a hard fork with no state migration: every account and contract address changed, and users had to move funds and create new accounts. The first wave of apps launched with it.
- Proposal:AZUP-2 approved by sequencer signalling and token-holder vote
- Implementation:v5.0.0 released 13 July 2026
- Release:stable release; latest maintenance release v5.2.0 on 17 August 2026
- Activation:canonical on mainnet from 14 July 2026 per Aztec Labs' incident report; Aztec's blog post gives 21 July
Sources: Aztec — Introducing Alpha V5 (external site) · Aztec Forum (Aztec Labs) — AZUP-2 is Ready for Proposal (external site) · AztecProtocol on GitHub — v5.0.0 release notes (external site) · Aztec Forum (Aztec Labs) — Incident report: inactivity slashes following the v5 upgrade (external site) · AztecProtocol on GitHub — v5.2.0 maintenance release notes (external site)
-
v4.3.1 fixed a block-size miscount that could crash the validator proposing a checkpoint block
Node release v4.3.1 fixed security advisory GHSA-692h-272j-rvgc. When the block proposer packed an epoch checkpoint into its proposal, the node counted transactions by raw size, while CometBFT checks the slightly larger encoded size. A full block at a checkpoint boundary could therefore pass Babylon's check but exceed CometBFT's limit, and CometBFT would then crash the proposer. The fix counts encoded sizes and drops trailing ordinary transactions if a proposal still fails the size check.
- Implementation:proposal size accounting fixed in the checkpointing module
- Release:released as v4.3.1 on GitHub on 21 July 2026
- Activation:per node on install; no coordinated upgrade found; operator adoption not checked
Sources: Babylon Labs — babylon v4.3.1 release (external site) · Babylon Labs — Checkpoint proposal size accounting fix (GHSA-692h-272j-rvgc) (external site) · Babylon Labs — Babylon node CHANGELOG at tag v4.4.0 (external site) · Babylon Labs — Release notes from babylon (Atom feed) (external site)
-
Monero GUI v0.18.5.2 released
The official GUI wallet release fixed wallet generation during first use, warned when adjusting KDF rounds, fixed precision loss in large payment requests and created wallets in memory in the setup wizard. It is an ecosystem-project wallet release, not a consensus change.
- Stage:Stable release
- Activation:Not claimed
Source: Monero community — Monero GUI 0.18.5.2 'Fluorine Fermi' released (external site)
-
Across bridge stopped supporting Blast
Across, a cross-chain bridge, posted a notice that it was deprecating Blast support and that once disabled, targeting 20 July 2026, its routes to and from Blast would stop returning quotes. On review day its swap API chain list no longer included Blast.
- Implementation:Blast removed from the Across swap API chain list
- Release:deprecation notice published on the Across docs
- Activation:in effect on review day
Sources: Across — Chains and Contracts (Blast deprecation notice) (external site) · Across — Swap API chain list (external site)
-
PulseChain adds a Docker Compose setup for running a local node
PulseChain's mainnet repository added a Docker Compose setup that starts a local full node and exposes JSON-RPC at 127.0.0.1:8545, with setup scripts and a rewritten node guide. Commits two days later added agent skills for node setup, sync status and client upgrades, plus a prompt users can paste into an AI agent.
- Implementation:merged into the pulsechain-mainnet repository
- Release:available on the repository's master branch
- Activation:not a network change; applies to users who adopt the setup
Sources: PulseChain (GitLab, pulsechain-mainnet) — Add Docker Compose setup for running a local PulseChain node (commit e0577ab9) (external site) · PulseChain (GitLab, pulsechain-mainnet) — Running a PulseChain Node (external site) · PulseChain (GitLab, pulsechain-mainnet) — PulseChain Mainnet: master commits (Atom feed) (external site)
-
Era node software core v31.3.0 fixed an external node crash and several API issues
Matter Labs published release core v31.3.0 of the zksync-era node software. Its bug fixes stop the external node from crashing in its sync state updater task, correct handling of the 'to' field in the API, make state overrides iterate in a fixed order, fix three correctness issues in the Ethereum proof manager, and change how storage logs are read from the database. Its features adapt the Airbender prover server to the v31 verifier wire format and let it fetch jobs from several chains' job servers in turn.
- Implementation:API, external node, proof manager and Airbender prover server changes merged into the core node code
- Release:core v31.3.0 published on GitHub on 2026-07-20
- Activation:takes effect on each node when its operator installs it; no network-wide activation
Sources: Matter Labs (GitHub) — core: v31.3.0 (external site) · Matter Labs (GitHub) — matter-labs/zksync-era releases (external site) · ZKsync Docs — ZKsync OS overview (external site) · ZK Nation Forum — [ZIP-16] ZKsync v31 Upgrade (external site)
-
van Rossem hard fork enacted at Epoch 644
Intersect reported that the hard-fork governance action was enacted on Cardano mainnet at the Epoch 644 boundary on 2026-07-18 21:44:51 UTC.
- Proposal:ratified before enactment
- Implementation:coordinated and tested before mainnet
- Release:mainnet protocol upgrade
- Activation:enacted at Epoch 644 on 2026-07-18
Source: Intersect — Intersect weekly update #121 July 24, 2026 (external site)
-
initiad v1.4.9 updated the node's state-storage library with race-condition fixes
Initia Labs published v1.4.9 on 2026-07-18, and GitHub marks it as the latest release. Its one listed change moves the IAVL storage library from Initia's fork v1.2.6-initia.1 to v1.2.8-initia.1. That brings in the upstream IAVL fix for a race between updating the fast-node cache and committing to the database, plus an Initia commit titled as a fix for a race condition in storage-version tracking. The release notes do not describe symptoms.
- Implementation:dependency bump merged in pull request 533 on the release/v1.4.x branch
- Release:released 2026-07-18 as v1.4.9, marked Latest
- 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.9 (external site) · initia-labs on GitHub — initia go.mod at tag v1.4.9 (external site) · initia-labs on GitHub — initia go.mod at tag v1.4.8 (external site) · initia-labs on GitHub — Initia IAVL fork: commit history at v1.2.8-initia.1 (external site) · cosmos/iavl on GitHub — IAVL changelog, release/v1.2.x branch (external site) · Initia Labs public REST endpoint — Live node info (initiad and CometBFT versions) (external site)
-
Chia 2.7.3 released with wallet and GUI fixes
Protocol/reference-client release: Chia 2.7.3 added a read-only WalletConnect confirmation exception and fixed Plot NFT key assignment, Linux confirmation dialogs, log viewing and NFT offer confirmation. This client release is not evidence of a consensus-rule activation.
- Claim:Released
Sources: Chia Network Inc. — Chia 2.7.3 (external site) · Chia Network Inc. — chia-blockchain 2.7.3 release (external site)
-
ibc-go v11.2.0 released
ibc-go v11.2.0 added rate-limiting middleware with configurable per-channel and per-denomination quotas for IBC v1 and v2.
- Release:Released
- Activation:chain adoption not inferred
Source: cosmos/ibc-go maintainers — ibc-go v11.2.0 release notes (external site)
-
Contribution Reward replaces the equal proposer reward, with unearned rewards set to be burned
Under GP-21, which the governance forum marks as passed, the per-block reward that every council member shared equally is replaced by Contribution Reward: 0.96 KAIA per block goes to the Kaia Performance Fund and is paid for measured contribution or burned. The first mission counts USDT deposited in designated protocols, capped at one USDT per 10 KAIA staked or delegated. The first epoch report (9 September 2026) paid out 36,421 KAIA of a 2,500,000 KAIA monthly budget and calculated the remaining 98.5% as the amount to burn; the operation guide says unpaid rewards are burned in a batch after three epochs.
- Proposal:GP-21 marked passed on the governance forum
- Implementation:Mission-1 operated by the Kaia Foundation
- Release:operating parameters published; no separate node release confirmed
- Activation:first epoch ran from about 23 July to 22 August 2026; claims opened on 7 September 2026, with rewards released over six months; the calculated burn happens in a batch after three epochs
Sources: Kaia Governance Forum — [GP-21] Contribution Reward Operation Guide (English) (external site) · Kaia Governance Forum — [CR] Contribution Reward Monthly Report - Epoch 1 (external site) · Kaia Docs — Kaia Governance (external site) · Kaia Docs (Kaia Foundation) — Kaia Blockchain White Paper v1.3 (external site)
-
Taiko scheduled the Unzen fork, making a zero-knowledge proof mandatory
The taiko-alethia-client v2.6.0 release set Unzen's mainnet activation for 2026-08-06 13:00 UTC. Under Unzen every proof pair that finalizes a range must include an SP1 or RISC Zero proof, a proving-cost budget (zk gas) limits each block, and forced-inclusion support is restored.
- Proposal:postmortem says it was proposed 2026-07-07 and approved by the Security Council 2026-07-14
- Implementation:client support released in taiko-alethia-client v2.6.0
- Release:Released
- Activation:Taiko's docs describe Unzen as the current mainnet fork at review time
Sources: Taiko contributors (GitHub) — taiko-alethia-client v2.6.0 (external site) · Taiko Documentation — Unzen Fork (external site) · Taiko Labs — Taiko Security Incident: A Postmortem and Next Steps (external site) · L2BEAT — Taiko Alethia (external site)
-
Node release v2026.06 brings global version 15, enabled on mainnet on 23 July 2026
TON's v2026.06 node release added global version 15, a set of protocol rule changes, along with sync and networking changes for nodes. TON's global-versions document says version 15 was enabled on mainnet on 23 July 2026. Under it, only governance contracts can change libraries, private libraries can no longer be added or used, accounts cannot be deployed with a library dictionary, a failed action phase also charges action fines for the messages that succeeded, and a transaction's outgoing messages are capped at 5,242,880 bits and 20,480 cells in total.
- Implementation:global version 15 rules implemented in node release v2026.06
- Release:released 2026-07-15
- Activation:enabled on mainnet 2026-07-23, per TON's global-versions document
Sources: ton-blockchain maintainers — TON v2026.06 release notes (external site) · ton-blockchain maintainers — Global versions (external site) · ton-blockchain maintainers — TON releases (external site)
-
java-tron GreatVoyage-v4.8.2 (Pyrrho) adds Osaka- and Pectra-era virtual machine features
GreatVoyage-v4.8.2 (Pyrrho) was released as a mandatory upgrade with a deadline of 23:59 Singapore time on 16 August 2026. It adds a count-leading-zeros opcode, a secp256r1 (P-256) signature-check precompile, bounds and new pricing for the MODEXP precompile and historical block hashes served from state, alongside a resource-window change (TIP-833), a switch from Fastjson to Jackson, removal of InfluxDB metrics reporting in favour of Prometheus, and a required Event Plugin v3.0.0. A non-mandatory 4.8.2.1 followed on 31 July.
- Proposal:TIP-7939, TIP-7823, TIP-7883, TIP-7951, TIP-2935 and TIP-833 referenced in the release notes
- Implementation:shipped in java-tron v4.8.2
- Release:mandatory release; upgrade deadline 2026-08-16 23:59 SGT
- Activation:Osaka and Prague gates shown enabled on mainnet in a 2026-09-27 parameter query; activation dates not verified
Sources: tronprotocol (GitHub) — GreatVoyage-v4.8.2 (Pyrrho) release notes (external site) · TRON Developer Hub — Release Announcements (external site) · TronGrid — Chain parameters (public API response) (external site) · TRON Core Devs (TRON on Medium) — Mainnet Pyrrho Announcement (external site)
-
Thor v2.4.4 limits deep paging in the node's log-query APIs and fixes how finality weighs stake
Thor v2.4.4 is an optional maintenance release that the maintainers highly recommend. The node's events and transfers filter APIs now refuse any request whose offset is above 100,000 with an HTTP 403 error; operators can change the cap with the --api-logs-max-offset flag, and the notes say to page through large result sets by block range instead. The release also changes the finality gadget to compute its proof-of-stake threshold from the staking state after the client's housekeeping step, reworks transaction-pool pricing, adds transaction-pool and database metrics, and lets operators switch some features at runtime through the admin server.
- Implementation:shipped in Thor v2.4.4 (pull requests #1619 to #1633); the offset flag is still present at the v2.5.0 tag
- Release:optional, highly recommended maintenance release published 2026-07-15; later superseded by the mandatory v2.5.0 of 2026-09-03
- Activation:no fork height named; takes effect on each node that installs v2.4.4 or later; adoption not measured
Sources: vechain/thor maintainers — Thor v2.4.4 release notes (external site) · vechain/thor maintainers — Thor command-line flags at tag v2.5.0 (cmd/thor/flags.go) (external site) · vechain/thor maintainers — Thor releases (Atom feed) (external site)
-
Rollup contract upgrade added forced-transaction support, which is not yet live
On 14 July 2026 the Security Council upgraded Linea's rollup contract on Ethereum from version 7.1 to 8.0, adding support for future forced transactions and setting a forced-transaction fee of 0.001 ETH. Forced transactions would let a user submit a Linea transaction through Ethereum with a processing deadline, after which a batch that skipped it could not be finalized. Linea's docs still say the feature is not yet live.
- Implementation:contract support deployed in rollup contract version 8.0
- Release:rollup contract version 8.0
- Activation:not live, per Linea's forced-transactions page
Sources: Linea Documentation — Linea Security Council transaction record (external site) · Linea Documentation — Forced transactions (external site) · L2BEAT — Linea (external site)
-
Bitcoin Core 29.4 released
Bitcoin Core 29.4 is a maintenance release for the 29.x line. Its release notes include a fix for excessive chainstate database rewrites and other implementation fixes; it does not represent a new consensus-rule activation.
- Stage:Release
Source: Bitcoin Core contributors — Bitcoin Core 29.4 release notes (external site)
-
Draft proposal for WLD-staked validators on World Chain
WIP-1008 proposes an overlay of up to 128 WLD-staked validators that would attest to recent blocks and contribute transaction lists at the start of each block, giving recent blocks a stake-backed confirmation before Ethereum finality. The sequencer would remain the only block producer.
- Proposal:Draft
- Implementation:not implemented on mainnet
- Release:None
- Activation:not active
Sources: Worldcoin on GitHub — WIP-1008: Staked Subblocks and Unsafe-Head BFT (external site) · Worldcoin on GitHub — World Chain Improvement Proposals (WIPs) (external site)
-
Zebra 6.0.0 added mainnet NU6.3 activation support
Zebra 6.0.0 configured NU6.3 activation at height 3,428,143 and incorporated the released NU6.3 protocol dependencies.
- Stage:Release
Sources: Zcash Foundation — Zebra 6.0.0 release (external site) · Zcash ZIP editors — ZIP 258: Deployment of NU6.3 (external site)
-
Chia 2.7.2 released with security and pre-3.0 features
Protocol/reference-client release: Chia 2.7.2 continued security hardening and added Weight Proof v2, PlotNFT v2 drivers, Python 3.14 support and new RPCs. The publisher described some features as intended for use after the Chia 3.0 fork; this record does not claim they were activated.
- Claim:Released
Sources: Chia Network Inc. — Chia 2.7.2 (external site) · Chia Network Inc. — chia-blockchain 2.7.2 release (external site)
-
Loopring's exchange contract gained batch NFT sending
A further upgrade added a function for sending NFTs held by the exchange back to many recipients in one transaction. L2BEAT notes that ERC-20 tokens still have to be sent out manually.
- Implementation:upgrade executed on Ethereum; batch NFT function present in the verified source
- Release:revised admin executor contract
- Activation:active since 9 July 2026
Sources: L2BEAT — Loopring (external site) · L2BEAT (GitHub) — Loopring contract diff history (external site) · Sourcify — ProxyAdminExecutor verified source (9 July 2026 version) (external site) · Etherscan — Loopring: Exchange v2 (external site)
-
nearcore 2.13.0 shipped protocol-upgrade and operator-breaking changes
nearcore 2.13.0 shipped protocol changes including ML-DSA-65 transaction/access keys, Gas Keys and DelegateV2, dynamic resharding, and a direct protocol-version move from 84 to 86. It also removed centralized ExternalStorage state sync and included DB migration 48 to 49 for continuous epoch sync. Mainnet RPC later observed version 86 on 2026-09-25; that dated observation supports activation of version-gated features but is not a functional transaction, gas-key, or resharding test.
- Proposal:Mixed draft documents
- Implementation:Released
- Release:Stable
- Activation:mainnet-protocol-86-observed-2026-09-25; feature behavior not directly exercised
Sources: NEAR nearcore — nearcore 2.13.0 (external site) · NEAR NEPs — NEP-639: Dynamic Resharding (external site) · NEAR NEPs — NEP-645: Post-Quantum Transactions (external site)
-
Neo-CLI v3.10.1 scheduled the Gorgon hard fork on Neo N3
Neo announced Neo-CLI v3.10.1 as a mandatory upgrade because it activates the Gorgon hard fork, at mainnet block 12,020,000 (expected around the morning of 1 August 2026 UTC) and TestNet block 17,960,000. The fork brings a fix to NeoVM's SHL and SHR shift instructions, a refactored instruction jump table and updated cryptographic verification. The June 2026 v3.10.0 release had said it did not activate Gorgon. Neo's time estimates assumed 3-second blocks.
- Implementation:released in Neo-CLI v3.10.1
- Release:released July 2026
- Activation:scheduled for mainnet block 12,020,000 around 1 August 2026; activation was not observed in this review
Sources: Neo — Neo-CLI v3.10.1 TestNet and MainNet Upgrade Notice (external site) · Neo — Neo-CLI v3.10.0 TestNet and MainNet Upgrade Notice (external site) · neo-project/neo maintainers — neo releases (external site) · neo-project/neo-node maintainers — Neo-CLI mainnet configuration (external site) · neo-project/neo maintainers — neo v3.10.1 release (external site) · neo-project/neo-node maintainers — Neo CLI v3.10.1 (external site)
-
Node 7.2.2 limits dry-run contract calls to 3 seconds by default
Node 7.2.2, a maintenance release on the stable branch, sets a default 3-second execution limit on the dry-run endpoint that wallets and apps use to simulate contract calls, where previously there was no limit, and lets operators disable more external endpoints in configuration.
- Implementation:Implemented
- Release:released 2026-07-08
- Activation:applies to nodes that upgrade
Source: aeternity/aeternity releases on GitHub — Aeternity node v7.2.2 (external site)
-
PoL Next replaced BGT with fixed WBERA issuance alongside the Fusaka fork
Berachain's PoL Next upgrade deployed about 24 hours before the Fusaka hard fork, which activated on 8 July 2026 at 16:00 UTC. It deprecated BGT, removed the boost curve and BGT governance, and fixed issuance at 0.4 WBERA per block to the proposer's operator and 1.305 WBERA to reward vaults. Incentives net of validator commission now accrue to BERA stakers through sWBERA. Fusaka brought Ethereum's Osaka changes to Berachain's execution layer.
- Implementation:audit reports by Zenith and Cantina are linked from the changelog
- Release:Released
- Activation:deployed about 24 hours before Fusaka, which activated 2026-07-08 16:00 UTC; BGT deprecated 2026-07-08
Sources: Berachain docs — BGT Token (external site) · Berachain docs — What's New (Proof of Liquidity changelog) (external site) · Berachain docs — Protocol Features (upgrade timeline) (external site) · Berachain (GitHub) — bera-reth v1.4.1 (Fusaka) (external site) · Berachain (GitHub) — BeaconKit mainnet spec.toml (chain 80094) (external site)
-
Bitcoin Core 30.3 released
Bitcoin Core 30.3 is a maintenance release for the 30.x line. Its release notes include a fix for excessive chainstate database rewrites and other validation, wallet, P2P, build, and test fixes; this is client-software maintenance, not a Bitcoin protocol activation.
- Stage:Release
Source: Bitcoin Core contributors — Bitcoin Core 30.3 release notes (external site)
-
Bitcoin Core 31.1 released
Bitcoin Core 31.1 is a maintenance release that fixes excessive chainstate database rewrites and an IP-address leak affecting the PrivateBroadcast feature, along with validation, wallet, P2P, build, and test fixes.
- Stage:Release
Source: Bitcoin Core contributors — Bitcoin Core 31.1 release notes (external site)
-
Bloom hard fork brings newer Ethereum features to Harmony
Release v2026.1.0 scheduled the Bloom hard fork for epoch 2964 (shard 0 block 91,488,255). It enabled several Ethereum improvements, including transient storage (EIP-1153), BLS12-381 precompiles (EIP-2537), PUSH0 (EIP-3855), MCOPY (EIP-5656), limits on SELFDESTRUCT (EIP-6780) and block-hash history (EIP-2935), together with a second version of leader rotation, block timestamp checks and tighter cross-shard proof handling. Validators had to run accurate time synchronization.
- Implementation:Released
- Release:v2026.1.0 published 2026-07-08
- Activation:activated at epoch 2964 in mid-July 2026
Sources: Harmony (GitHub) — Mainnet Release 2026.1.0 (Bloom hard fork) (external site) · Harmony — Harmony shard 0 public RPC (external site) · Harmony — Q3 2025: London & Berlin Forks, Stream Sync Dashboards, LP Bots, Beta Governance (external site)
-
Karst hard fork activated on Ink
The Karst upgrade activated on Ink Mainnet on 8 July 2026. It made the Rust-based Kona program the main fault-proof program for withdrawals, added a mechanism for upgrading Ink's built-in contracts through network upgrades, brought several Ethereum Osaka changes to the chain including a per-transaction gas cap, and required node operators to run op-reth instead of op-geth.
- Proposal:approved through Optimism governance
- Implementation:shipped in op-reth and kona-client releases
- Release:Released
- Activation:active on Ink Mainnet since 2026-07-08
Sources: Optimism Docs — Upgrade 19: Karst hard fork (external site) · Optimism (ethereum-optimism/superchain-registry) — Superchain Registry: mainnet/ink.toml (external site) · Ink on GitHub — inkonchain/node (external site) · Optimism Docs — End of Support for op-geth and op-program (external site)
-
Juno Agents DAO allowed to distribute tokens to stakers
Governance proposal 375 passed and added the Juno Agents DAO contract to the drip module's allow list, so the DAO can send native or token-factory tokens it already holds to JUNO stakers. The proposal states this grants no minting power, treasury access, module control or permission to change the drip module's settings.
- Proposal:proposal 375 passed
- Implementation:allow list updated by the proposal
- Release:no software release needed
- Activation:active: drip parameters listed the DAO address on 2026-09-27; no distribution was checked
Sources: Juno on-chain state via PublicNode REST endpoint — Juno proposal 375: Authorize Juno Agents DAO for x/drip distributions (external site) · Juno documentation — Juno Agents DAO (external site) · Juno on-chain state via PublicNode REST endpoint — Juno drip module parameters (external site)
-
Karst hard fork (OP Stack Upgrade 19) activated on Mode
Mode was among the OP Stack chains named for the Karst upgrade. Karst added a subset of Ethereum's Osaka changes on the L2, including a per-transaction gas cap of about 16.8 million gas and higher costs for some precompiles, introduced a new way to upgrade L2 system contracts, and required node operators to move from op-geth to op-reth.
- Proposal:Optimism governance upgrade proposal
- Implementation:shipped in OP Stack releases
- Release:op-node and op-reth releases named in the notice
- Activation:active on Mode since 2026-07-08
Sources: Optimism Docs — Upgrade 19: Karst hard fork (external site) · Optimism Docs — Notice archive (external site) · Optimism (ethereum-optimism/superchain-registry) — Superchain Registry: mainnet/mode.toml (external site) · L2BEAT — Mode Network (external site)
-
Monero v0.18.5.1 released
The recommended core software point release contains bug fixes, restricted-mode privacy filtering, wallet hardening against malicious remote nodes and RandomX v1.2.2. This is software-release evidence, not evidence of a new consensus-rule activation.
- Stage:Stable release
- Activation:Not claimed
Sources: Monero community — Monero 0.18.5.1 'Fluorine Fermi' released (external site) · The Monero Project contributors — Monero v0.18.5.1 release (external site)
-
Noble v11.5.0 recovers the expired IBC client for Coreum
Release v11.5.0, a minor release in the v11 Flux line, lists one change: it recovers the expired IBC light client that Noble uses to track the Coreum mainnet (coreum-mainnet-1). The release notes list no other module or dependency change and give no upgrade height.
- Implementation:released as v11.5.0; the only listed change is the Coreum client recovery
- Release:released 2026-07-08 (not a pre-release)
- Activation:not verified; Noble's mainnet upgrade table lists no height for v11.5.0, and a public node reported the later v11.6.0 on 2026-09-27
Sources: noble-assets/noble maintainers — Noble v11.5.0 release notes (external site) · noble-assets/noble maintainers — noble-assets/noble releases (Atom feed) (external site) · Noble documentation — Mainnet Chain Upgrades (external site) · Noble public REST endpoint — Noble node software version (on-chain query) (external site)
-
Karst activation recorded for OP Mainnet
The reviewed OP Mainnet registry configuration records Karst at 2026-07-08T16:00:01Z.
- Type:Upgrade
- Proposal:Approved before registry activation
- Release:Activation config recorded
- Activation:Activated mainnet
Source: OP Labs — OP Mainnet registry configuration (external site)
-
Karst hard fork (OP Stack Upgrade 19) activated on Unichain
Unichain was among the OP Stack chains named for Karst. The upgrade brought a subset of Ethereum's Osaka changes to the L2, including a per-transaction gas cap of 16,777,216 gas and higher costs for some precompiles, added a governed mechanism for upgrading L2 system contracts, moved withdrawals to the Kona-based fault-proof program, and required node operators to run op-reth.
- Proposal:Optimism governance upgrade proposal
- Implementation:shipped in op-node and op-reth releases named in the notice
- Release:released before activation
- Activation:active on Unichain since 2026-07-08
Sources: Optimism Docs — Upgrade 19: Karst hard fork (external site) · Optimism Docs — Karst (external site) · Optimism (ethereum-optimism/superchain-registry) — Superchain Registry: mainnet/unichain.toml (external site)
-
Karst hard fork (OP Stack Upgrade 19) activated on Zora Network
Zora was among the OP Stack chains named for the Karst upgrade. Karst added a subset of Ethereum's Osaka changes on the L2, including a per-transaction gas cap of 16,777,216 gas and a tighter limit on one cryptographic precompile, and required node operators to move from op-geth to op-reth. Karst also promoted a new fault-proof game type on OP Stack chains, but L2BEAT records that Zora stayed on its permissioned dispute game.
- Proposal:Optimism governance upgrade proposal
- Implementation:shipped in OP Stack releases
- Release:op-node and op-reth releases named in the notice
- Activation:active on Zora Network since 2026-07-08
Sources: Optimism Docs — Upgrade 19: Karst hard fork (external site) · Optimism (ethereum-optimism/superchain-registry) — Superchain Registry: mainnet/zora.toml (external site) · L2BEAT — Zora Network (external site)
-
Moonriver's MOVR set to migrate to Base on the same deadline
The sister network on Kusama announced a one-for-one move of MOVR to an ERC-20 token on Base by 2026-07-31, routed through Moonbeam because the bridge contract lived there.
- Implementation:migration route published
- Release:MOVR contract announced on Base
- Activation:standard migration closed 2026-07-31 23:59 UTC
Sources: Moonbeam — Moonriver Strategic Update: MOVR is Migrating to Base (external site) · Moonbeam Foundation — GLMR and MOVR migration portal (external site) · Subscan — Moonbeam explorer (external site)
-
HIP 149 approved: Proof-of-Coverage retired, Mobile target minimum, supplement mint and Advisory Council
veHNT holders approved HIP 149, which bundles four decisions: Mobile deployers earn HNT for rewardable data within a band of half to three times the carrier rate; a supplement mint of about 141 million HNT over 36 months goes to a vault administered by Nova Labs; Proof-of-Coverage retires on both Mobile and IoT; and a 7-seat Advisory Council oversees the supplement. Helium's docs mark Proof-of-Coverage removed as of 6 July 2026.
- Proposal:HIP 149 approved by veHNT vote (two-thirds supermajority, 100,000,000 veHNT quorum); marked Approved in the HIP repository on 6 July 2026
- Implementation:oracle releases 4.0.0 (2026-07-02, HIP-149 tracking) and 4.1.0 (2026-07-29, Mobile Proof-of-Coverage reward path removed)
- Release:Helium's docs mark Proof-of-Coverage removed as of 6 July 2026; Helium's 7 August post describes the target minimum as live
- Activation:live per Helium's docs and blog; the HIP index still says Approved, and the supplement mint start was not checked at the vault on chain
Sources: Helium (HIP repository) — HIP 149: Helium Utility and Emissions Realignment (external site) · Helium (HIP repository) — HIP 149 file history (commit feed) (external site) · Helium Documentation — Helium Oracle Data (external site) · Helium (GitHub) — helium/oracles release 4.0.0 (HIP-149 tracking) (external site) · Helium (GitHub) — helium/oracles release 4.1.0 (external site) · Helium blog — New Earnings Safety Net for Helium Deployers (external site)
-
Nominators made unslashable with a two-era unbonding period
Referendum 1910 disabled nominator slashing and cut the nominator unbonding period from 28 days to 2 eras. It followed Referendum 1890, executed on 2026-06-12, which requires validators to hold at least 10,000 DOT of their own slashable stake.
- Proposal:Referendum 1910 executed
- Implementation:staking configuration change on Polkadot Hub
- Release:parameter change by referendum; no separate release reviewed
- Activation:active since 2026-07-06
Sources: Subsquare (Polkadot OpenGov) — Referendum 1910: Staking Configuration Update: Nominator Slashing & Unbonding Parameters (external site) · Subsquare (Polkadot OpenGov) — Referendum 1890: Staking: set min validator bond to 10K DOT (external site) · Polkadot Forum — Changes on Polkadot in March 2026 (external site) · Polkadot Wiki — Chain State Values (external site)
-
The v31 protocol upgrade for Era was proposed, then delayed for review
ZIP-16 proposed the v31 upgrade, which would take Era directly from v29 to v31 and remove contract patterns incompatible with ZKsync OS, keeping Era and ZKsync OS support in the same codebase. The rescoped proposal left the earlier interop-fee mechanics out of this upgrade; a Matter Labs reply said that code stays in the codebase, inactive. Its target date for Era moved from 4 August to 24 August 2026, and on 24 August a Matter Labs reply said v31 had been delayed and was under review.
- Proposal:ZIP-16 posted 2026-07-06 and linked to an onchain vote; vote result not confirmed here
- Implementation:under review after delay
- Release:upgrade not executed on Era mainnet
- Activation:not active; no new date announced at review time
Source: ZK Nation Forum — [ZIP-16] ZKsync v31 Upgrade (external site)
-
ICF published its June 2026 treasury snapshot
The Interchain Foundation published a treasury snapshot reporting its fiat and cryptocurrency holdings as of June 30, 2026. This is foundation transparency reporting, not Cosmos Hub chain state, consensus, or governance execution.
- Release:published transparency report
- Activation:not a Cosmos Hub protocol activation
Sources: Interchain Foundation — ICF Treasury Snapshot: June 2026 (external site) · Interchain Foundation — Interchain Foundation Medium RSS (external site)
-
Gnosis Pay published a post-mortem of the June 2026 card safe exploit
Gnosis Pay reported that on 1 June 2026 attackers abused a signature-validation flaw in the Zodiac Delay and Roles modules used by its card safes, taking about 1.5 million dollars and leaving about 300 thousand dollars inaccessible across 5,281 wallets. Gnosis absorbed the losses and restored user funds. The flaw sat in module code, not in Gnosis Chain consensus.
- Implementation:fix and additional security reviews described by the operator
- Release:post-mortem published
- Activation:services restored in phases between 3 and 7 June 2026 per the post-mortem
Source: Gnosis Pay — Post-Mortem: Gnosis Pay Vulnerability Exploit (external site)
-
Moonbeam announced GLMR's move to Base and the end of its Polkadot parachain
Moonbeam said GLMR would migrate one-for-one to an ERC-20 token on Base, asked holders to bridge by 2026-07-31 and to withdraw funds from on-chain applications first, and said the parachain would run only through the transition. It also announced Moonbeam Protocol for AI-agent settlement on Base.
- Implementation:migration bridge opened with the announcement
- Release:GLMR contract live on Base
- Activation:standard migration closed 2026-07-31 23:59 UTC
Sources: Moonbeam — Moonbeam Strategic Update: Moonbeam Network Relaunches on Base (external site) · Moonbeam Foundation — GLMR and MOVR migration portal (external site) · BaseScan — Moonbeam (GLMR) token on Base (external site)
-
Polygon zkEVM sequencer switched off; claims move to Ethereum
Polygon's sunset page says that as of 3 July 2026 the Polygon zkEVM Mainnet Beta sequencer has been sunset, the network no longer produces blocks, and the bridge can no longer process withdrawals from it. Wallet balances are recoverable on Ethereum through a claims interface opening no earlier than 13 July 2026 and available through 31 December 2027. Assets held in smart contracts are not recoverable through it.
- Implementation:sequencer switched off
- Release:claims interface live, per Polygon's sunset page
- Activation:chain halted; claims open until 31 December 2027
Sources: Polygon Labs — Polygon zkEVM: Mainnet Beta Sunset and Fund Claims (external site) · Polygon Community Forum — Polygon zkEVM Mainnet Beta Sunset: Claim Your Funds (external site) · Polygon Labs — zkEVM Exit Claim (external site) · Alchemy — Polygon zkEVM Deprecation Notice (external site)
-
Bridged USDC went live on Astar through Swapper
Astar announced bridged USDC deployed by Swapper under Circle's bridged-USDC standard: USDC is locked on the source chain and minted on Astar through Chainlink CCIP, with no liquidity pool. Astar says it replaces Celer-bridged USDC and other older variants as the standard route, and that bridged USDC is not Circle-issued USDC.
- Implementation:deployed by Swapper
- Release:announced as live
- Activation:live per Astar's post; the contract and supply were not checked on chain
Sources: Astar blog — Bridged USDC Is Now Live on Astar via the Swapper Stablecoin Payment Layer (external site) · Circle — USDC contract addresses (external site)
-
Testnet-only client builds carry reward, penalty and gas-price changes not yet scheduled on mainnet
XinFinOrg published v2.8.2-testnet on 2 July 2026 and v2.9.1-testnet on 29 September 2026, both marked not for mainnet. From block 83,600,000 on the Apothem testnet they switch on Reward 2.0 (fixed rewards per node), a revised consensus penalty (Consensus Penalty V2) and a dynamic gas limit, and v2.9.1-testnet adds a gas tier that its code prices at 2,500 times the original 0.25 gwei floor. v2.9.1-testnet says the Prague and Osaka changes it implements are not scheduled. A community guide on XDC's forum says mainnet rollout is planned for October after an audit.
- Proposal:reward upgrade proposed on XDC's developer forum in April 2025
- Implementation:implemented in testnet-only builds v2.8.2-testnet and v2.9.1-testnet
- Release:testnet only; release notes say not to deploy to mainnet
- Activation:active on Apothem after block 83,600,000; no mainnet activation block at review
Sources: XinFinOrg (GitHub) — XDPoSChain v2.8.2-testnet release notes (external site) · XinFinOrg (GitHub) — XDPoSChain v2.9.1-testnet release notes (external site) · Developers Forum for XinFin XDC Network — Proposal: XDC Network Reward Mechanism Upgrade (external site) · Developers Forum for XinFin XDC Network — XDC Masternode, Protector & Observer Nodes Explained (external site) · XinFinOrg (GitHub) — params/config_networks.go (external site) · XinFinOrg (GitHub) — params/gas.go at v2.9.1-testnet (external site)