BCTS

SwissDLT

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

Lifecycle

first pin received 2026-09-03 06:06:13 UTC · 2 d ago #6306 via axelar
token discovered 2026-09-03 09:41:55 UTC · 2 d ago 4 contracts today
first liquid 2026-09-04 04:41:14 UTC · 19 h ago a chain quoted liquid
first alert pending not yet
reported chains pending none yet

Where this token lives

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

base mint burn via axelar 10

0x09a1ad50ac7b8ddd40bafa819847ab1ea6974a4fsame open

illiquidpools hold $0, under the floor

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

same_address	+3	{"chain":"base"}
codehash	+2	{"codehash":"0xe0321dc637627c350e8eae75389341c71189a33cacbff75dfd6aef09cf14b8a9"}
registry	+5	{"its":"0xb5fb4be02232b1bba4dc8f81dc24c26980de9e3c","adapter":"axelar","tokenId":"0xa036b788d7f585c871de1d9a8fef532cc917ecd5cdf8c1bf544c043cdab908bc"}

polygon mint burn via axelar 5

0xfbb6620e7dab8dfcd9f058c49bb37071cfd9983e 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":"0x59004883d2a488f5749e97105345a3182593769827c0a0472231f0f45a15664c","adapter":"axelar"}

binance canonical via axelar 3

0x09a1ad50ac7b8ddd40bafa819847ab1ea6974a4fsame open

illiquidpools hold $0, under the floor

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

registry

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

polygon canonical via axelar shadowed · not checked 3

0xce4d3160705febb069617a9ad919753055b56e49 open

liquid26 bps · 0.26% via kyberswap

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

registry

{"tx":"0xed190db8ae7a1e1d8d57407a0de0b396948eca9043e7b1ec52cebb4a65331ff8","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 base 2 of 2 reachable

binance axelar 0x1e289bed… 2 d ago

polygon axelar 0x362eb193… 2 d ago

from binance 1 of 2 reachable

polygon axelar 0xabc2ea2f… 2 d ago

show 1 unreachable hide unreachable

base no transfer seen

from polygon 2 of 2 reachable

base axelar 0xa60449b0… 2 d ago

binance axelar 0x19f8e4fb… 2 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#6970	2 d ago	axelarpolygon → binance	0xed190db8…331ff8	DISCOVERED	3 h 36 min
#6306	2 d ago	axelarbinance → polygon	0x59004883…15664c	DISCOVERED	46 min

Merge history

When	Winner	Loser	Contracts moved	Evidence	State
2 d ago	#1358	#1071	3	{"tx":"0x19f8e4fb74a294d50d0e54a7e3a6d7deb83ec9f80a05b86978abdc5c9fe84586","bridge":"axelar","reason":"a delivered transfer connected contracts held by two assets","endpoint":"binance:0x09a1ad50ac7b8d	active

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