#dusk $DUSK @Dusk I completed the CreatorPad task by interacting directly with the Dusk bridge rather than relying solely on the documentation.
One notable detail is that Dusk L1 is already live, with over 210M $DUSK staked, while DuskEVM is still designated as a testnet.
The bridge also differentiates between two versions of DUSK: Moonlight, which is transparent and account-based, and Phoenix, which is privacy-focused and note-based.
I initially expected a straightforward lock-and-mint process, but I found myself revisiting the explanations of Moonlight and Phoenix multiple times to fully understand the distinction.
The choice between these two models is significant, as it can influence how users later interact with their DUSK, including staking and privacy-related use cases.
While the bridge functions smoothly from a technical standpoint, I am not fully convinced it is immediately intuitive for new users. Although transferring DUSK is simple, it is not always clear which version of the asset users ultimately receive.
One notable detail is that Dusk L1 is already live, with over 210M $DUSK staked, while DuskEVM is still designated as a testnet.
The bridge also differentiates between two versions of DUSK: Moonlight, which is transparent and account-based, and Phoenix, which is privacy-focused and note-based.
I initially expected a straightforward lock-and-mint process, but I found myself revisiting the explanations of Moonlight and Phoenix multiple times to fully understand the distinction.
The choice between these two models is significant, as it can influence how users later interact with their DUSK, including staking and privacy-related use cases.
While the bridge functions smoothly from a technical standpoint, I am not fully convinced it is immediately intuitive for new users. Although transferring DUSK is simple, it is not always clear which version of the asset users ultimately receive.