A Dusk bridge transfer can succeed on L1 and still produce no BEP20 DUSK at the destination.

The number I would guard is 1 DUSK. The mainnet-to-BSC bridge deducts a fixed 1 DUSK bridge fee from the amount sent. So if I send exactly 1 DUSK, the source transaction can be valid and confirmed, but there is no amount left to pay out on BSC.

The actual minimum useful transfer is 1.000000001 DUSK. That extra one LUX is the difference between “fee fully consumed the transfer” and “something can arrive.”

That makes the review screen more important than it looks. I would not validate only that the amount is positive or that the wallet has enough for the network fee. I would calculate the net bridge output before signature and block anything at or below 1 DUSK.

Because the ugly user consequence is not a reverted transaction. It is a successful Dusk transaction followed by an empty destination, which looks exactly like a bridge delay to someone who does not know the fee boundary.

For me, the safe question is not “did it send?” It is “what survives the 1 DUSK bridge fee?”

#dusk $DUSK @Dusk