Skip to content

bug: usdt receive doesn't warn that only arbitrum one deposits arrive #996

Open

Description

@ovitrif

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

  1. added this to the 3.0.5 milestone on Oct 16, 2026
  2. ovitrif commented on Oct 16, 2026

    @ovitrif
    CollaboratorAuthor

    Design input from the release thread:

    • Users expect one USDT address to work on any network (thread), so the network should be clear on the default receive screen, not only in the picker.
    • Option A: force an explicit network choice before showing an address, as most EVM wallets do (thread); design input pending from Aldert.
    • Option B: default to the most widely used network (thread).
  3. ovitrif commented on Oct 16, 2026

    @ovitrif
    CollaboratorAuthor

    More design input from the release thread:

    • Exodus is a reference for presenting stablecoin networks (thread).
    • Why Arbitrum is the hub and other networks are routed through deposit addresses: @ben-kaufman's explanation (thread).
  4. ovitrif commented on Oct 17, 2026

    @ovitrif
    CollaboratorAuthor

    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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions