Repository navigation
bug: usdt receive doesn't warn that only arbitrum one deposits arrive #996
Description
Refs: Release 3.0.0 thread
What happened?
A tester sent USDT to their Bitkit USDT receive address on Ethereum mainnet instead of Arbitrum One. Bitkit receives USDT on Arbitrum One only, so the deposit never showed up. The address is an EOA, so the funds are recoverable with the wallet's key, but the app gave no clear warning about the network. Copying the address from the main receive view also copied the payment link rather than the address (#995), which pushes users to type or pick the network themselves.
Expected behavior
The USDT receive screen states plainly, next to the address and in the copied/shared text, that only USDT on Arbitrum One is supported and that USDT sent on other networks will not appear in Bitkit.
Bitkit Version
3.0.0 RC2.
Activity
ovitrif commentedon Oct 16, 2026
Design input from the release thread:
ovitrif commentedon Oct 16, 2026
More design input from the release thread:
ovitrif commentedon Oct 17, 2026
Also from the release thread: the warning must say only USDT is supported, so other stablecoins sent to this address won't arrive either (thread).
ben-kaufman commentedon Oct 20, 2026
Aldert proposed this copy warning in Figma thread #982, and Ben has approved implementing the copy-message portion now:
Show it after successfully copying the USDT receive address. Keep the visible network label and copy the address for that network: Arbitrum One for direct receives, or the selected network’s deposit address for bridge receives.
The copy-warning change can proceed independently. Mandatory network selection before revealing the address and warning behavior before sharing remain unconfirmed design details.