CSWAP

CrossSwap.com

status: illiquid2/2 checked · 0 liquid · warm
first bridged: 3 d ago
arrived via: portal_bridge
contracts: 3 on 2 chains
confirmed by a transfer: 2 of 3
liquidity: 2 of 2 chains checked · 0 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-02 04:12:46 UTC · 3 d ago 3 contracts today
first liquid pending not yet
first alert pending not yet
reported chains pending none yet

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.

ethereum canonical via portal_bridge 8

0xe0b0c16038845bed3fcf70304d3e167df81ce225same open

illiquidpools hold $0, under the floor

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

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

binance mint burn potential · no transfer seen 5

0xe0b0c16038845bed3fcf70304d3e167df81ce225same open

illiquidtradeable but costly — 549 bps · 5.49%

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

same_address	+3	{"chain":"binance"}
codehash	+2	{"codehash":"0x9422ca24fcb2af438ff5937ea2afa7f3eaf253f1a7244309c7b7012a1ce2a373"}

binance lock mint wrapper via portal_bridge shadowed · not checked 5

0xf40cfbe4c13c8c6465911cb9cfdbe36ae1e546ef open

illiquidpools hold $0, under the floor

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

derivation

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

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 binance 0 of 1 reachable

No transfer has been seen leaving binance.

show 1 unreachable hide unreachable

ethereum no transfer seen

from ethereum 1 of 1 reachable

binance portal_bridge 0xacf1c7a7… 3 d ago

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