As blockchain ecosystems mature, native assets matter more than ever. For Dusk Network, the transition from BEP20/ERC20 DUSK to native DUSK on mainnet is not just a technical upgrade — it’s a foundational step toward decentralization, security, and long-term scalability.
If you’re still holding DUSK on Ethereum or Binance Smart Chain, this article explains why the migration matters, how it works, and what you gain by moving to native DUSK.
🚀 Why Native DUSK Matters
BEP20 and ERC20 DUSK tokens were essential during Dusk’s early growth phase, providing liquidity and accessibility across major chains. But they come with limitations:
Dependency on external networks (ETH / BSC)
Smart contract risk
Higher and unpredictable gas fees
Limited integration with Dusk’s core protocol features
Native DUSK, on the other hand, is issued directly on the Dusk mainnet, unlocking the full power of the network:
🔐 Protocol-level security
🌘 Native staking and governance
⚙️ Seamless integration with DuskDS and DuskEVM
🧩 Future-proof compatibility with privacy-preserving applications
Migrating is not optional for long-term users — it’s the gateway to Dusk’s real utility.
🔁 How the Migration Works (High-Level)
The migration process is designed to be secure, transparent, and user-friendly.
Your BEP20 / ERC20 DUSK is locked in a smart contract on Ethereum or BSC
A migration event is emitted and verified
Native DUSK is issued directly to your Dusk mainnet wallet
The process completes in approximately 15 minutes
No swaps. No bridges between chains. No liquidity risk.
This is a 1:1 protocol-level issuance, not a market conversion.
🧭 Step-by-Step Migration Flow
1️⃣ Access the Dusk Web Wallet
Start by opening the official Dusk Web Wallet. You can either:
Import an existing wallet, or
Create a new Dusk mainnet wallet
This wallet will be the destination for your native DUSK.
2️⃣ Initiate Migration
Once inside the wallet:
You’ll be prompted to start the migration
Carefully review the information shown
Confirm that you’re ready to proceed
3️⃣ Connect Your Web3 Wallet
Use WalletConnect to link your Web3 wallet that holds BEP20 or ERC20 DUSK.
Supported environments:
Ethereum Mainnet (ERC20)
Binance Smart Chain (BEP20)
Your Web3 wallet will:
Trigger the migration function
Pass your Dusk mainnet wallet address as the target
4️⃣ Confirm the Transaction
Approve the transaction in your Web3 wallet.
At this point:
Your BEP20/ERC20 DUSK is locked
The migration process begins
Security timers and validations are applied
5️⃣ Receive Native DUSK
After finalization (usually within ~15 minutes):
Native DUSK is issued to your Dusk wallet
The original ETH/BSC transaction hash is recorded in the memo field
Migration is complete 🎉
⏱ How Long Does It Take?
Typically around 15 minutes, depending on:
Ethereum / BSC network congestion
Block confirmation speed
Finalization checks for security
This delay is intentional and designed to protect users.
🔍 Tracking Your Migration
You can track the process in two ways:
On ETH/BSC:
Monitor the transaction in your Web3 wallet
On Dusk Mainnet:
Once complete, the Dusk transaction will include the original ETH/BSC hash for full traceability
Transparency is built into every step.
⚠️ Important Rules to Know
✅ Minimum Migration Amount
Minimum is 1 LUX
1 LUX = 1,000,000,000 DUSK wei
Anything below this will be rejected by the contract.
🔢 Decimal Difference Explained
BEP20 / ERC20 DUSK → 18 decimals
Native DUSK → 9 decimals
Because of this:
Migration amounts are rounded down
Example:
1.234567890 DUSK (ERC20) → 1.0 DUSK native
This ensures precision and consistency on mainnet.
🌘 What You Can Do After Migration
Once you hold native DUSK, you’re fully aligned with the network’s future:
Stake and participate in consensus
Use DUSK across DuskDS and DuskEVM
Interact with upcoming privacy-first DeFi and RWAs
Prepare for long-term ecosystem growth
Native DUSK is not just a token — it’s network ownership.
✨ Final Thoughts
The BEP20 / ERC20 → Native DUSK migration marks a major milestone for the Dusk ecosystem. It represents the transition from dependency to sovereignty, from wrappers to protocol-native value.
If you believe in Dusk’s vision of privacy, compliance, and real-world adoption, migrating to native DUSK is not just a technical step — it’s a strategic one.
🌘 Move to native.
🌘 Move to mainnet.
🌘 Move with Dusk.
