Token Dashboard
tokens
2788
contracts
8845
confirmed
7202 of 8845
chains seen
14
unmeasured
92
queued
0

UDS

name unknown
status
liquid2/2 checked · 1 liquid · hot
first bridged
2 d ago
arrived via
layerzero
contracts
2 on 2 chains
confirmed by a transfer
2 of 2
liquidity
2 of 2 chains checked · 1 liquid
checking
hot
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-06 14:00:10 UTC · 20 h ago #9372 via layerzero
  2. token discovered 2026-09-05 12:33:06 UTC · 2 d ago 2 contracts today
  3. first liquid 2026-09-07 10:21:27 UTC · 2 min ago a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

ethereum canonical via layerzero
9
0x712bd4beb54c6b958267d9db0259abdbb0bff606 open
liquid142 bps · 1.42% via kyberswap

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

discord+1{"notes":[],"proven":false,"ticker":"UDS","source_tx":null,"message_id":"1421151591343456328","message_ts":"2025-09-26T15:09:03","source_url":"https://layerzeroscan.com/address/0x3629A58aa1F2a5CbAc7926befAe6E076Ae53C39b","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1421151591343456328","source_kind":"oft_address","curator_liquidity":true}
registry+3{"tx":"0x62f7feba9e4e3daa4fe61bcb7ceffa6c2e8c4ee382a73466131531311f2b5e08","from":"bridge_pin"}
registry+5{"via":"OFTAdapter.token","adapter":"layerzero","oftAdapter":"0x3629a58aa1f2a5cbac7926befae6e076ae53c39b"}
binance mint burn via layerzero
6
0x317a9fd718d472f7f78a305d37f0bf154bb430c4 open
illiquidpools hold $0, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"UDS","source_tx":null,"message_id":"1421151591343456328","message_ts":"2025-09-26T15:09:03","source_url":"https://layerzeroscan.com/address/0x3629A58aa1F2a5CbAc7926befAe6E076Ae53C39b","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1421151591343456328","source_kind":"oft_address","curator_liquidity":false}
peer_map+5{"via":{"address":"0x3629a58aa1f2a5cbac7926befae6e076ae53c39b","chainSlug":"ethereum"},"adapter":"layerzero"}

How it moves between chains

Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.

Each chain lists the directions a transfer has actually been seen taking. Directions with no transfer behind them are folded away per card and counted in its header. Derived routes are not shown at all.

from binance 1 of 1 reachable
ethereum layerzero 0xfa628104… 20 h ago
from ethereum 1 of 1 reachable
binance layerzero 0x62f7feba… 20 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9372 20 h ago layerzeroethereum → binance 0x62f7feba…2b5e08 DISCOVERED 18 min

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.