That night I was planning to bridge a little DUSK from Dusk Mainnet to BSC, just a light test first to be safe... but looking at the numbers made me realize that “sending as little as possible” can sometimes be a bad test.
I entered 10 DUSK into Dusk Official Bridge. the 1 DUSK Bridge Fee alone was already 10%, not even counting Dusk Network Transaction Fee.
25 DUSK means 4%; 50 DUSK is 2%; 100 DUSK is only 1%.
Net amount received = Amount sent - 1 DUSK - Network transaction fee.
sending 1 DUSK or less means BSC-side Payment = 0; minimum useful amount is 1.000000001 DUSK, Destination Address receives only 0.000000001 DUSK after bridge fee.
truthfully, by this point I changed my mind.
because I wasn’t only testing the money.
I was testing the Cross-chain Process: Mainnet Transaction goes into Official Bridge Account, Memo carries the 0x Address for Routing to the BSC Address, then BEP20 DUSK finally reaches the Final Destination.
sounds simple... only when I cross-checked everything myself did I realize how mentally taxing it was.
Official Web Wallet has Address Format Validation, but Final Address Verification is still my responsibility. Missing Memo, Incorrect Memo, Routing Error or using the wrong BEP20 Deposit Address can all block Automatic Processing; that’s when Asset Recovery becomes the real concern.
BTC Transfer got me used to a direct Receiving Address. but this flow separates Sending Responsibility and Routing Responsibility; being correct on Mainnet doesn’t necessarily mean I can feel at ease on the BSC side.
if the Exchange hasn’t confirmed Support for BEP20 Deposit Address, I won’t send.
Self-custody Wallet first... once I see BEP20 DUSK arrive in the right place, then I’ll move forward.
for me, 1 DUSK may not be the most expensive part; the most expensive moment is when the interface feels so familiar that I assume I already understand the entire flow.
when testing a bridge, would you choose the smallest amount, a reasonable fee ratio, or the ability to control every Routing point?
#dusk $DUSK @Dusk
I entered 10 DUSK into Dusk Official Bridge. the 1 DUSK Bridge Fee alone was already 10%, not even counting Dusk Network Transaction Fee.
25 DUSK means 4%; 50 DUSK is 2%; 100 DUSK is only 1%.
Net amount received = Amount sent - 1 DUSK - Network transaction fee.
sending 1 DUSK or less means BSC-side Payment = 0; minimum useful amount is 1.000000001 DUSK, Destination Address receives only 0.000000001 DUSK after bridge fee.
truthfully, by this point I changed my mind.
because I wasn’t only testing the money.
I was testing the Cross-chain Process: Mainnet Transaction goes into Official Bridge Account, Memo carries the 0x Address for Routing to the BSC Address, then BEP20 DUSK finally reaches the Final Destination.
sounds simple... only when I cross-checked everything myself did I realize how mentally taxing it was.
Official Web Wallet has Address Format Validation, but Final Address Verification is still my responsibility. Missing Memo, Incorrect Memo, Routing Error or using the wrong BEP20 Deposit Address can all block Automatic Processing; that’s when Asset Recovery becomes the real concern.
BTC Transfer got me used to a direct Receiving Address. but this flow separates Sending Responsibility and Routing Responsibility; being correct on Mainnet doesn’t necessarily mean I can feel at ease on the BSC side.
if the Exchange hasn’t confirmed Support for BEP20 Deposit Address, I won’t send.
Self-custody Wallet first... once I see BEP20 DUSK arrive in the right place, then I’ll move forward.
for me, 1 DUSK may not be the most expensive part; the most expensive moment is when the interface feels so familiar that I assume I already understand the entire flow.
when testing a bridge, would you choose the smallest amount, a reasonable fee ratio, or the ability to control every Routing point?
#dusk $DUSK @Dusk