$DUSK Bridging Isn’t as Simple as It Looks
Bridging DUSK sounds simple until you actually go through the CreatorPad flow.
I expected the usual routine: connect wallet, move tokens, wait a bit, done. Instead, I realized I was making a bigger choice than just moving DUSK from one place to another.
Dusk’s native L1 is already live, with more than 210M DUSK staked. DuskEVM, meanwhile, is still on testnet. So you’re moving between a live settlement network and an execution environment that’s still being tested. That distinction matters.
Then there’s the part most people probably won’t notice at first: Moonlight vs Phoenix.
Moonlight is account-based and transparent. Phoenix uses shielded, note-based transactions. Same DUSK, completely different privacy and balance model.
And that choice can affect what you do next.
The frustrating part isn’t that the system is complicated. It’s that the interface doesn’t make the important decision obvious enough. You can complete the bridge successfully while still being unsure what type of DUSK you actually received.
That’s the real UX issue.
A bridge shouldn’t just make the transaction work. It should make the outcome impossible to misunderstand.
So if you’re bridging @Dusk_Foundation don’t think of it as a simple transfer. Think of it as choosing between two paths: transparent or shielded.
The technology may be working exactly as designed. The question is whether the user is being given enough information to understand what they’re choosing.
#dusk $DUSK @Dusk
Bridging DUSK sounds simple until you actually go through the CreatorPad flow.
I expected the usual routine: connect wallet, move tokens, wait a bit, done. Instead, I realized I was making a bigger choice than just moving DUSK from one place to another.
Dusk’s native L1 is already live, with more than 210M DUSK staked. DuskEVM, meanwhile, is still on testnet. So you’re moving between a live settlement network and an execution environment that’s still being tested. That distinction matters.
Then there’s the part most people probably won’t notice at first: Moonlight vs Phoenix.
Moonlight is account-based and transparent. Phoenix uses shielded, note-based transactions. Same DUSK, completely different privacy and balance model.
And that choice can affect what you do next.
The frustrating part isn’t that the system is complicated. It’s that the interface doesn’t make the important decision obvious enough. You can complete the bridge successfully while still being unsure what type of DUSK you actually received.
That’s the real UX issue.
A bridge shouldn’t just make the transaction work. It should make the outcome impossible to misunderstand.
So if you’re bridging @Dusk_Foundation don’t think of it as a simple transfer. Think of it as choosing between two paths: transparent or shielded.
The technology may be working exactly as designed. The question is whether the user is being given enough information to understand what they’re choosing.
#dusk $DUSK @Dusk