-
Notifications
You must be signed in to change notification settings - Fork 5
Add BEP20 DUSK bridge article #58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,56 +1,10 @@ | ||
| --- | ||
| title: Dusk BEP2 Migration | ||
| description: Step-by-step guide to migrating your BEP2 DUSK tokens to the BEP20 standard. | ||
| title: Dusk BEP2 Migration (Closed) | ||
| description: The BEP2 to BEP20 DUSK migration has ended. This page is kept for transparency. | ||
| --- | ||
|
|
||
| As the <a href="https://www.bnbchain.org/en/blog/final-sunset-plan-of-bnb-beacon-chain" target="_blank">Binance Beacon Chain is sunsetting</a>, there have been multiple communications over the past months to facilitate the migration of BEP2 DUSK tokens to BEP20 DUSK. | ||
| The DUSK BEP2 to BEP20 migration has officially concluded. The final deadline for users to submit their BEP2 tokens was **November 1st, 2024**, after which no further submissions were accepted. All valid migrations were processed, and the final distribution of BEP20 DUSK tokens was completed. | ||
|
|
||
| This guide provides a step-by-step process for BEP2 DUSK token holders to successfully migrate their tokens. | ||
| The migration wallet used during this period — `bnb1dfls6c8y39l7qq4gj2479wkehg85pt5m07y94g` — is no longer active and should not be used for any further transactions. | ||
|
|
||
|
|
||
| :::note[Important] | ||
| Users will have up to **November 1st** to migrate their BEP2 DUSK. We will no longer process any BEP2 afterwards! | ||
|
|
||
| All BEP2 DUSK migrated before that deadline will be processed after said date. | ||
| ::: | ||
|
|
||
| ## Why Migrate? | ||
|
|
||
| The migration to BEP20 is crucial due to the sunsetting of the Binance Beacon Chain. Migrating ensures that your DUSK tokens remain usable, and can be bridge to mainnet in the future. | ||
|
|
||
| ## What You Will Need | ||
|
|
||
| Before starting the migration process, please ensure you have: | ||
|
|
||
| * A wallet holding your BEP2 DUSK tokens, with a small amount of BNB | ||
| * A Binance Smart Chain-compatible wallet for receiving your BEP20 DUSK tokens (for example [BNB Chain Wallet](https://www.bnbchain.org/en/binance-wallet) or [Trust Wallet](https://trustwallet.com/). | ||
|
|
||
| ## Migration Process | ||
|
|
||
| ### Step 1: Gas | ||
|
|
||
| Ensure that you have a small amount of BNB in your wallet to cover the network fees for the transaction. | ||
|
|
||
| ### Step 2: Sending BEP2 DUSK Tokens | ||
|
|
||
| 1. Access your wallet holding the BEP2 DUSK tokens. This can be done through the [BNB Chain Wallet](https://www.bnbchain.org/en/binance-wallet) or [Trust Wallet](https://trustwallet.com/). | ||
|
|
||
| 2. Initiate a transfer to our Dusk controlled migration wallet: `bnb1dfls6c8y39l7qq4gj2479wkehg85pt5m07y94g` | ||
|
|
||
| :::danger | ||
| **IMPORTANT**: In the MEMO field of the transaction, enter the receiving address of your BEP20-compatible wallet. **The address should be in a `0x` format**. This step is **crucial** to ensure your BEP20 DUSK tokens are sent to a correct address. | ||
| ::: | ||
|
|
||
|  | ||
|
|
||
| ### Step 3: Receiving BEP20 DUSK Tokens | ||
|
|
||
| The Dusk team will process migrations in batches. Your BEP20 DUSK tokens will be distributed to the provided BEP20 wallet address on May the 1st 2024. | ||
|
|
||
| ## After Migration | ||
|
|
||
| Dusk will make an announcement when the payout has been completed. Once you receive your BEP20, verify the receipt in your BEP20-compatible wallet. | ||
|
|
||
| ## Need Help? | ||
|
|
||
| if you encounter any issues or have questions during the migration process, please reach out to us on our official [Telegram](https://t.me/DuskNetwork) or [Discord channel](https://discord.com/channels/847466263064346624/1223314872834588865). | ||
| This page remains online for archival and transparency purposes only. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| --- | ||
| title: Native DUSK to BEP20 Bridge | ||
| description: How to bridge your native DUSK tokens to BEP20 DUSK on Binance Smart Chain. | ||
| --- | ||
|
|
||
| This guide explains how to bridge your **native DUSK** tokens to **BEP20 DUSK** on Binance Smart Chain (BSC). This operation is handled through the official **BEP20 bridge** and facilitated via the [Dusk Web Wallet](https://apps.dusk.network/wallet/). | ||
|
|
||
| When bridging, your native DUSK tokens are locked on the Dusk network. Once locked, a mint operation is initiated on Binance Smart Chain, issuing an equivalent amount of BEP20 DUSK to your specified address. The full bridging process typically completes within 15 minutes. | ||
|
|
||
| :::note[Note] | ||
| Want to **bridge from BEP20 DUSK to native DUSK** instead? Check our [Migration Guide](/learn/guides/mainnet-migration/) for the complete walkthrough. | ||
| ::: | ||
|
|
||
| ## Bridging Steps | ||
|
|
||
| 1. Open the [Web Wallet](https://apps.dusk.network/wallet/). | ||
| 2. Open or import your native Dusk wallet. | ||
| 3. Navigate to the **Send** tab. | ||
| 4. Enter the official **Bridge Address** as the recipient: | ||
| ``` | ||
| mFqH6RVxCoWQfjQ23H9YVr8JhQ697M5DD4ob76kcuoEYqqYA6H9cxHrxjvnZ6z4PQKsBd3PBpRYLN9M3FgkQQVywREzkzgeme4ersJgLaxYaQzZSAzkd1QBJ4ByTe9NrhXp | ||
| ``` | ||
| 5. In the **Memo** field, enter your **BEP20 compatible address** (your BSC wallet address). | ||
| 6. Specify the amount of native DUSK to bridge. The minimum is 1.000000001 DUSK. | ||
| 7. Review and confirm the transaction. | ||
|
|
||
| Your DUSK will be locked on the Dusk network, and an equivalent amount will be minted on BSC shortly after. | ||
|
|
||
| ## FAQ | ||
|
|
||
| **How long does the bridge process take?** | ||
| Typically within 15 minutes. Network congestion or confirmations may slightly affect the timing. | ||
|
|
||
| **Where do the BEP20 tokens go?** | ||
| They are sent to the EVM address specified in the memo field. | ||
|
|
||
| **What happens if I omit the memo or use an invalid address?** | ||
| The bridge will ignore your transaction, and funds will not be bridged. Always double-check the memo field before confirming. | ||
|
HDauven marked this conversation as resolved.
Outdated
|
||
|
|
||
| **Can I use this bridge for ERC20 DUSK?** | ||
| No. This bridge only supports native DUSK to **BEP20 DUSK** on Binance Smart Chain. | ||
|
|
||
| **Is there a fee?** | ||
| Yes, the bridge charges a flat fee of 1 DUSK per transaction. Your bridged amount will be **original amount - 1 DUSK**. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.