Altcoins
Canton freezes topology changes ahead of its synchronizer switchover
The freeze was reported in progress from November 6 at 14:00 UTC, with an expected end on November 7 at the same time. Blockdaemon says ordinary transactions continue during this phase, while some deployments and validator onboarding must wait.

A preparation window opened on November 6
At 14:00 UTC on November 6, 2026, Blockdaemon reported the start of a freeze on topology changes on Canton mainnet. The notice, originally published on October 19, describes an operation coordinated by the Canton Foundation ahead of a logical synchronizer upgrade, or LSU. The announced window runs until November 7 at 14:00 UTC. Its end depends on the switchover being completed and may come a little later, according to the notice.
Topology here means the configuration that allows participants and applications to operate on the network. During the freeze, Blockdaemon says ordinary transactions continue, while operations that change that configuration do not go through. The notice lists new contract deployments, validator onboarding, and DAR archive uploads. An application already in service and a team looking to add a network component can therefore face different conditions at the same time.
The service keeps its identity as its infrastructure changes
Technical proposal CIP-0117, approved in June, describes how the logical synchronizer works. A validator uses a stable identity to reach the synchronization service even as the nodes doing the work behind that identity change. In an upgrade of this kind, super validators deploy the new set of nodes alongside the old one. They can thus prepare the replacement while the existing service continues to process exchanges.
The freeze stabilizes the configuration while it is transferred. Under the procedure described in the proposal, operators initialize the successor from the existing topology and identity state, then test its ability to order events before the transition. Validators running compatible software detect the successor and prepare to switch connections. The mechanism is designed to retain local history and avoid a data export followed by an import for each validator.
The freeze and the switchover have different effects
The transaction continuity announced by Blockdaemon applies to the freeze phase. The technical proposal describes a different situation at the switchover itself. Daml transactions still in flight on the old physical synchronizer can then time out, and new transactions are handled by the successor. For applications, the document describes a noticeable pause of seconds to minutes during this transition. This is how the mechanism is expected to behave, and its execution needs to be observed separately.
For teams operating services on Canton, the distinction helps interpret a failure during the window. A rejected topology change does not necessarily indicate that all transactions have stopped. Blockdaemon says it will update the notice when the freeze is lifted. Until that confirmation, the announced end time remains an estimate, and configuration operations should be distinguished from actual resumption after the switchover.
