USDtb

status: liquid4/4 checked · 1 liquid · warm
first bridged: 2 d ago
arrived via: layerzero
contracts: 5 on 4 chains
confirmed by a transfer: 5 of 5
liquidity: 4 of 4 chains checked · 1 liquid
checking: warm
already alerted on: nothing yet
pins: 0

Lifecycle

first pin received pending no pin linked (added by hand, or before pins were tracked)
token discovered 2026-09-03 00:52:22 UTC · 2 d ago 5 contracts today
first liquid 2026-09-05 06:49:45 UTC · 5 min ago a chain quoted liquid
first alert pending not yet
reported chains pending none yet

Where this token lives

More than one contract on solana (2). That is allowed — a bridge wrapper and the canonical token are separate contracts and trade in separate pools (§3) — but it is also what a clone reusing the ticker looks like. Compare the evidence below: a contract confirmed by the bridge itself outranks one matched only by symbol.

arbitrum mint burn via layerzero 10

0xc708b6887db46005da033501f8aebee72d191a5dsame open

illiquidpools hold $0, under the floor

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

same_address	+3	{"chain":"arbitrum"}
codehash	+2	{"codehash":"0x32cdb8880f05611c50942037a080d621b413c640593abc08503743329d0976a4"}
peer_map	+5	{"via":{"address":"0xc708b6887db46005da033501f8aebee72d191a5d","chainSlug":"ethereum"},"adapter":"layerzero"}

ethereum canonical via layerzero 5

0xc139190f447e929f090edeb554d95abb8b18ac1c open

liquid7 bps · 0.07% via kyberswap

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

peer_map

{"via":{"address":"0xc708b6887db46005da033501f8aebee72d191a5d","chainSlug":"base"},"adapter":"layerzero","oftAdapter":"0xc708b6887db46005da033501f8aebee72d191a5d","unwrappedTo":"0xc139190f447e929f090edeb554d95abb8b18ac1c"}

solana mint burn via layerzero decimals differ from source 5

39DrizvVVntnUhKkyy7Nu8v1YDySA1y4R1uBnv4U7zYy open

illiquidpools hold $0, under the floor

Every source here is an inference. A contract on this chain has not confirmed the link itself.

bridge_transfer

{"tx":"4YWxugNaAtJEd3RP8oZHh6P5HrjJ9HSC2XnGEQtp7YX6h1wkdSuR515P3HAmMce1oarp8uCgHT9SRRWamfFjHj4J","adapter":"layerzero"}

solana mint burn via layerzero decimals differ from source shadowed · not checked 5

5hVfCMHKKcb4rcB9BLYkM3ZRkvvyjaUU1LVcSAQyASbS open

illiquidpools hold $0, under the floor

Every source here is an inference. A contract on this chain has not confirmed the link itself.

bridge_transfer

{"tx":"3waTUCG2jE3zfr6oCvZU183mp9y24SRLQrpGpvcLbdYjy7p8QpP4n72AeuTKMue6gcjqX4o7gDu7riKDRCqxMQC5","adapter":"layerzero"}

base canonical via layerzero 3

0xc708b6887db46005da033501f8aebee72d191a5dsame open

illiquidpools hold $0, under the floor

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

registry

{"tx":"0xaec38d605ced8a41a9079a6a7570dc9fc9f32564b02b62dc77f1901126d80fd2","from":"bridge_pin"}

How it moves between chains

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 arbitrum 3 of 3 reachable

base layerzero 0xda5a8888… 2 d ago

ethereum layerzero 0xd71387b0… 2 d ago

solana layerzero 0x7c6dc587… 2 d ago

from base 3 of 3 reachable

arbitrum layerzero 0x5ef076ea… 2 d ago

ethereum layerzero 0xaec38d60… 2 d ago

solana layerzero 0x26d77801… 2 d ago

from ethereum 3 of 3 reachable

arbitrum layerzero 0xa838750a… 2 d ago

base layerzero 0xdb6ee198… 2 d ago

solana layerzero 0x9c681dc4… 2 d ago

from solana 3 of 3 reachable

arbitrum layerzero 2MsZZ484FT… 2 d ago

base layerzero 3waTUCG2jE… 2 d ago

ethereum layerzero DX55Bb2sCx… 2 d ago

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