The primary keyword for this update is Waves 1.6.4 activation. The Waves 1.6.4 release notes describe activation at height 5,400,000 on September 13, 2026 and a feature that adjusts block-reward distribution when activated. The release also states that nodes do not need to rebuild state when upgrading from 1.6.3.
What Happened
The Waves 1.6.4 release notes describe activation at height 5,400,000 on September 13, 2026 and a feature that adjusts block-reward distribution when activated. The release also states that nodes do not need to rebuild state when upgrading from 1.6.3.
The event date comes from the cited announcement or release note. This page was checked against the sources on September 15, 2026 UTC before publishing.
Why It Matters
For Radar, the useful angle is protocol operations and governance: an activation-height feature changes the node, generator and ecosystem checks required around the transition. Exchange transfer pauses add a downstream dependency, but the protocol state and generator behavior remain the primary questions.
The owner fit controls the framing. Exchange events stay on CryptoSigy as route, fee, futures or trading-risk context; protocol events stay on Radar when the useful question is node, governance, chain or ecosystem operations.
What To Watch Next
Watch the activation feature status, generator and node versions, block rewards after height 5,400,000, explorer consistency and any follow-up governance decision.
If the official source changes a deadline, block height, contract specification or transfer status, rebuild the decision from the updated source rather than from a stale headline.
The editorial filter is consensus software release, activation height, governance feature and node readiness.. Treat this as decision context, not as a prediction, recommendation or promotional note.
Date discipline matters: published and updated timestamps are generated at publish time in UTC, while event dates in the body come from the cited source.
Risk reminder: betting and crypto decisions can cause financial loss. Use official sources, keep stakes or position sizes controlled, and avoid treating one update as a complete strategy.
Before acting on the update, compare the official notice with the live product, market or protocol surface. If contract specs, fee terms, route availability, lineup status or governance details differ, the live source should override the older assumption.
The practical output is a watchlist, not a verdict. Readers should know which timestamp, rule, venue field or protocol dependency must be checked next before the update has any operational value.
Continue this cluster
Continue this cluster with related source-backed updates in the same owner lane.
