I expected @Dusk_Foundation bridge to be a simple lock-and-mint flow.

Then I actually walked through it.
The contrast caught my attention:

210M+ DUSK is already staked securing the Live Dusk L1, while DuskEVM is still Testnet.
But the bigger UX question isn’t the network status.

It’s what happens to $DUSK when you bridge.
You’re navigating two different models:

Moonlight → transparent, account-based

Phoenix → shielded, note-based

So bridging isn’t only:

L1 → EVM

It’s also deciding what form of DUSK you want to hold.
That choice can matter for what you do next, especially around privacy and network functionality.

The conversion itself may be seamless.

But after going through the flow, I think there’s a difference between seamless and understandable.

The bridge moves the asset.
The UX still has to explain the choice.
#dusk @Dusk $DUSK