A Dusk client can still understand Phoenix perfectly and be completely wrong about whether it can use Phoenix today.That is the Boreas edge I would test first in any old signer. Mainnet disabled new Phoenix transactions at block 4,414,095 on June 10. Testnet followed at block 4,000,000 on August 7. But Rusk still keeps Phoenix decoders and historical execution support because old blocks must remain replayable.
So “I can decode Phoenix” is not a capability check anymore.
A custom wallet or custody service can restore old Phoenix history, parse shielded transactions, and look healthy right up until it tries to submit a new spend. The historical path still works. Live admission does not.
That is the failure I care about because it hides behind compatibility. Nothing looks obviously broken in the database or replay layer. The break only appears when a user expects fresh shielded movement.
I would gate transaction options against the active network rules, not against whatever formats the node can still read from history.
After Boreas, backward compatibility can preserve the past without preserving the action.
#dusk $DUSK @Dusk
So “I can decode Phoenix” is not a capability check anymore.
A custom wallet or custody service can restore old Phoenix history, parse shielded transactions, and look healthy right up until it tries to submit a new spend. The historical path still works. Live admission does not.
That is the failure I care about because it hides behind compatibility. Nothing looks obviously broken in the database or replay layer. The break only appears when a user expects fresh shielded movement.
I would gate transaction options against the active network rules, not against whatever formats the node can still read from history.
After Boreas, backward compatibility can preserve the past without preserving the action.
#dusk $DUSK @Dusk