When I rechecked the latest network upgrade records for @Dusk , I found a more important change than a typical version update: after the Boreas upgrade, the Dusk mainnet has stopped receiving and executing new Phoenix transactions.
Boreas shipped alongside Rusk 1.7, and the mainnet reboot boundary was set on June 10, 2026 at block 4,414,095. Phoenix was disabled when the mainnet restarted; the testnet stopped after reaching height 4,000,000 on August 7. Current new transactions mainly use the Moonlight model.
But “stopping new transactions” doesn’t mean Phoenix is deleted. Nodes still retain the ability to decode old Phoenix transactions, replay their historical execution, and synchronize chain state, because an Archive Node must be able to replay old blocks. Put plainly: when a bank stops opening a certain type of old account, it doesn’t mean past transaction history can be removed from the ledger.
Boreas also introduced versioned transaction handling, deterministic VM charging rules, a Reverted Event marker, and adjusted the Slash execution order to occur before ordinary transactions. This shows the upgrade focus is not merely swapping the transfer model, but tightening the boundary of how different nodes interpret the same transaction.
The real question to follow up is: what will Dusk’s privacy route be handed to next? Moonlight is a public-account model, while DuskEVM positions Hedger as the future privacy path. Going forward, we should focus on Hedger delivery, wallet migration, handling of old Phoenix balances, and whether the documentation is updated consistently.
The most dangerous thing about studying privacy projects is not the technical changes, but the continued use of the old architecture to explain the new network. #dusk $DUSK
Boreas shipped alongside Rusk 1.7, and the mainnet reboot boundary was set on June 10, 2026 at block 4,414,095. Phoenix was disabled when the mainnet restarted; the testnet stopped after reaching height 4,000,000 on August 7. Current new transactions mainly use the Moonlight model.
But “stopping new transactions” doesn’t mean Phoenix is deleted. Nodes still retain the ability to decode old Phoenix transactions, replay their historical execution, and synchronize chain state, because an Archive Node must be able to replay old blocks. Put plainly: when a bank stops opening a certain type of old account, it doesn’t mean past transaction history can be removed from the ledger.
Boreas also introduced versioned transaction handling, deterministic VM charging rules, a Reverted Event marker, and adjusted the Slash execution order to occur before ordinary transactions. This shows the upgrade focus is not merely swapping the transfer model, but tightening the boundary of how different nodes interpret the same transaction.
The real question to follow up is: what will Dusk’s privacy route be handed to next? Moonlight is a public-account model, while DuskEVM positions Hedger as the future privacy path. Going forward, we should focus on Hedger delivery, wallet migration, handling of old Phoenix balances, and whether the documentation is updated consistently.
The most dangerous thing about studying privacy projects is not the technical changes, but the continued use of the old architecture to explain the new network. #dusk $DUSK