More than one contract on arbitrum (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.
0xb5e18fd63657fb8739a40a582ee0db72c2428030
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| derivation | +5 | {"via":"calculateL2TokenAddress","router":"0x72ce9c846789fdb6fc1f34ac4ad25dd9ef7031ef","adapter":"arbitrum_bridge"} |
0x3106e2e148525b3db36795b04691d444c24972fb
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +5 | {"via":"TokenAdminRegistry","pool":"0xF6403CF6E954a43699097322e0867C63d653C2D0","adapter":"ccip","selector":"4949039107694359620"} |
0x601486c8fdc3ad22745b01c920037d6c036a38b9
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +5 | {"via":"TokenAdminRegistry","pool":"0xF6403CF6E954a43699097322e0867C63d653C2D0","adapter":"ccip","selector":"6433500567565415381"} |
0xc271a17db5ce6f53745a3f466077ec816bc20a9c
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +5 | {"via":"TokenAdminRegistry","pool":"0xF6403CF6E954a43699097322e0867C63d653C2D0","adapter":"ccip","selector":"4051577828743386545"} |
0xf2f7901b7bba5799493b617b06ead1862f771297
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +5 | {"via":"TokenAdminRegistry","pool":"0xF6403CF6E954a43699097322e0867C63d653C2D0","adapter":"ccip","selector":"15971525489660198786"} |
0x911d86c72155c33993d594b0ec7e6206b4c803da
open
3 of 3 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xbd98477316bf54e5438e9d748ecb4caaa901be5dc02c672d2ee222ec8715c187","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"arbitrum_bridge"} |
| registry | +3 | {"tx":"0xc74c10feb66eee2345e9bf886b03d73689adcb167f6a2e57af4b6f65120cac0b","from":"bridge_pin"} |
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.
No transfer has been seen leaving base.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #8284 | 2 d ago | ccipavalanche → ethereum | 0x66da9a14…9371a9 | SKIPPED_DUPLICATE | 11 h |
| #6760 | 2 d ago | ccipethereum → avalanche | 0x5205afb6…9cc9d0 | SKIPPED_DUPLICATE | 2 h 52 min |
| #6444 | 2 d ago | cciparbitrum → avalanche | 0x34077225…c8ac8b | SKIPPED_DUPLICATE | 1 h 53 min |
| #4785 | 2 d ago | ccipethereum → avalanche | 0x1c0b2721…000b06 | SKIPPED_DUPLICATE | 3 h 30 min |
Every address above came from an on-chain read. The evidence trail shows which read produced it.