BDXN

Bondex Token

status: liquid2/2 checked · 1 liquid · warm
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 · 1 liquid · 1 unmeasured
checking: warm
already alerted on: nothing yet
pins: 1

Lifecycle

first pin received 2026-09-03 06:07:30 UTC · 2 d ago #8170 via portal_bridge
token discovered 2026-09-03 02:58:46 UTC · 2 d ago 3 contracts today
first liquid 2026-09-05 05:45:09 UTC · just now a chain quoted liquid
first alert pending not yet
reported chains pending none yet

Where this token lives

More than one contract on ethereum (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 canonical via portal_bridge 8

0x1036b2379f506761f237fba7463857924ef21ce3 open

liquid45 bps · 0.45% via kyberswap

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

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

ethereum lock mint wrapper via portal_bridge 5

0xc811dfcda1adaa5178c5854f8e94a6111ac948cd 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":"0x3ee18b2214aff97000d974cf647e7c347e8fa585","originChainId":4}

ethereum mint burn via portal_bridge shadowed · not checked 5

0xbdbdbdd0c22888e63cb9098ad6d68439197cb091 open

unknownBALANCE_READ_FAILED — not a negative result

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

derivation

{"via":"ntt_peer","adapter":"portal_bridge","manager":"0x2b6edb94df814a95103373ffcad0e47f19edb96f","wormholeId":2,"peerManager":"0x2b6edb94df814a95103373ffcad0e47f19edb96f"}

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

ethereum portal_bridge 0x1302d4b8… 2 d ago

from ethereum 1 of 1 reachable

binance portal_bridge 0x50becbdb… 2 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8170	2 d ago	portal_bridgebinance → ethereum	0xc4cac16f…9b345b	SKIPPED_DUPLICATE	11 h

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