#dusk $DUSK
There’s a small trap in the DUSK migration flow that I could easily see myself falling into.
You connect a wallet, choose your ERC-20 or BEP-20 $DUSK, approve the migration — and it feels like you’re done.
You’re not.
The approval only gives the migration contract permission to use the tokens. The actual move to native DUSK starts only after you hit Execute migration and confirm that transaction.
That sounds like a minor UX detail, but it matters.
If you stop after approval, your native DUSK simply isn’t on its way yet. You’ve authorized the next step without actually taking it.
It’s the kind of thing I like checking before moving assets between networks:
approval ≠ execution.
Small distinction. Very different outcome.
@Dusk
There’s a small trap in the DUSK migration flow that I could easily see myself falling into.
You connect a wallet, choose your ERC-20 or BEP-20 $DUSK, approve the migration — and it feels like you’re done.
You’re not.
The approval only gives the migration contract permission to use the tokens. The actual move to native DUSK starts only after you hit Execute migration and confirm that transaction.
That sounds like a minor UX detail, but it matters.
If you stop after approval, your native DUSK simply isn’t on its way yet. You’ve authorized the next step without actually taking it.
It’s the kind of thing I like checking before moving assets between networks:
approval ≠ execution.
Small distinction. Very different outcome.
@Dusk