Token Dashboard
tokens
2782
contracts
8803
confirmed
7159 of 8803
chains seen
14
unmeasured
93
queued
0

BYUSD

BYUSD
status
liquid1/1 checked · 1 liquid · dormant
first bridged
4 d ago
arrived via
layerzero
contracts
1 on 1 chains
confirmed by a transfer
0 of 1
liquidity
1 of 1 chains checked · 1 liquid
checking
dormant
already alerted on
nothing yet
pins
0

Lifecycle

  1. first pin received pending no pin linked (added by hand, or before pins were tracked)
  2. token discovered 2026-09-02 22:35:09 UTC · 4 d ago 1 contracts today
  3. first liquid 2026-09-06 18:46:25 UTC · 3 h ago a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

bera canonical via layerzero
potential · no transfer seen 3
0x688e72142674041f8f6af4c808a4045ca1d6ac82 open
liquid29 bps · 0.29% via kyberswap

1 of 1 sources are protocol-attested — a contract confirmed this link.

registry+3{"tx":"0x36947240ebf0654b77d6e3fd4e82c2ca1b304712abfed5d2bc0b1577776c3b82","from":"bridge_pin"}

How it moves between chains

No bridge transaction yet. These contracts are inferred, not confirmed by a transfer. Paste a bridge transaction that moved this token and discovery re-checks every contract and maps its routes.

Only one chainA token on a single chain has nowhere to bridge to, so there is no route to find yet.

Verdict. Add it if this is the token you want to watch; reject it if any contract is a twin, a clone or junk — a rejected token stays checked but is not alerted on again.

Exclude this token if it is junk or not worth watching. Liquidity stops being checked and nothing more is searched for it; its contracts, evidence, routes and history stay, its pins are still recorded, and it can be tracked again from the Excluded page.

Every address above came from an on-chain read. The evidence trail shows which read produced it.