I expected moving testnet @Dusk_Foundation between Dusk L1 and DuskEVM to feel the same in both directions. But It doesn’t.

Deposit (L1 → DuskEVM)
• Submit once on Dusk L1
• Wait for it to appear in your DuskEVM account simple.

Withdrawal (DuskEVM → L1)
• Initiate on DuskEVM
• Prove the withdrawal on Dusk L1
• Finalize on Dusk L1

That means source fee with two extra L1 fees. And you can’t just wait a fixed amount of time.

Withdrawal readiness depends on:
• Published network state
• Proof maturity
• Dispute-game checks

Dusk’s official guide is clear: follow the Web Wallet status, not the clock.

Funds are leaving the execution environment and returning to the settlement layer. The protocol needs cryptographic evidence before the withdrawal becomes final. That design prioritizes security and correct settlement.

The cost is UX and liveness dependency a valid withdrawal isn’t necessarily actionable when the user expects it, and it requires multiple deliberate actions.

Does the prove and finalize path give the right level of settlement assurance for a bridge, or does it make withdrawals too dependent on status tracking and extra user steps? Is Dusk’s approach worth the friction?

$DUSK
$TUT
$EDEN
#dusk #EthereumFoundationLaunchesGlamsterdamTestnet #DollarFallsTo10WeekLow #Layer1 #DollarHits3MonthLow