BID

CreatorBid

status: fully reported2/2 checked · 2 liquid · 2 reported · hot
first bridged: 2 d ago
arrived via: portal_bridge
contracts: 3 on 2 chains
confirmed by a transfer: 3 of 3
liquidity: 2 of 2 chains checked · 2 liquid
checking: hot
already alerted on: base, binance
pins: 3

Lifecycle

first pin received 2026-09-03 01:19:29 UTC · 2 d ago #4564 via portal_bridge
token discovered 2026-09-03 05:07:30 UTC · 2 d ago 3 contracts today
first liquid 2026-09-04 05:33:53 UTC · 21 h ago a chain quoted liquid
first alert 2026-09-04 05:33:53 UTC · 21 h ago multi_chain_liquid, sent 21 h ago
reported chains base, binance — 2 of 2

Where this token lives

More than one contract on binance (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.

binance mint burn via portal_bridge 10

0xa1832f7f4e534ae557f9b5ab76de54b1873e498bsame open

liquidlast verified 21 h ago

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

same_address	+3	{"chain":"binance"}
codehash	+2	{"codehash":"0xb4b59e371d3a1e512e6182652b8e7e9535c3cee09179ee1acd6fcd9cb567e9da"}
derivation	+5	{"via":"ntt_peer","adapter":"portal_bridge","manager":"0xc5103069c3a0b52cddea0f565a4589d54452114c","wormholeId":4,"peerManager":"0xc5103069c3a0b52cddea0f565a4589d54452114c"}

base canonical via portal_bridge 8

0xa1832f7f4e534ae557f9b5ab76de54b1873e498bsame open

liquidlast verified 21 h ago

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

registry	+3	{"tx":"0x8502b2424fe6c87610077223690d4ea68447370319dbb09c579c154b4d7e475d","from":"bridge_pin"}
derivation	+5	{"via":"origin_from_index","adapter":"portal_bridge","originChainId":30}

binance lock mint wrapper via portal_bridge shadowed · not checked 5

0x5d7c6ebd253ca7c96603ded6ed35bcf61342ad9a open

liquidlast verified 23 h ago

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

derivation

{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0xb6f6d86a8f9879a9c87f643768d9efc38c1da6e7","originChainId":30}

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 base 1 of 1 reachable

binance portal_bridge 0x8502b242… 34 h ago

from binance 1 of 1 reachable

base portal_bridge 0x0cea2842… 34 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7753	2 d ago	portal_bridgebinance → base	0x0cea2842…cdff3f	SKIPPED_DUPLICATE	10 h
#7752	2 d ago	portal_bridgebase → binance	0x5072b632…525a34	SKIPPED_DUPLICATE	10 h
#4564	2 d ago	portal_bridgebase → binance	0x8502b242…7e475d	DISCOVERED	3 h 48 min

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	21 h ago	SENT	21 h ago	426

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