Verify non-custody.
Every deposit address on this instance is a BIP32 derivation of the operator's published xpub — a watch-only capability that cannot spend the funds it generates. Paste the xpub and any deposit address, and we'll prove it.
What this proves
The service watches for incoming USDT/USDC at addresses derived
non-hardened from the operator's account-level xpub at the relative
receive path 0/index. An xpub cannot produce the private
keys for these addresses — only the operator's offline wallet can.
We BIP32-derive up to 1000 indices under the xpub you paste, compare each derived address to the one you paste, and report a hit with the proven relative path, or a miss. An xpub does not encode its complete mnemonic path; verify that separately against the source wallet. The endpoint never reads the operator's configured xpub from the database — the xpub comes from you, the verifier, only.