JCT

JANCTION

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

Lifecycle

first pin received 2026-09-03 06:06:44 UTC · 2 d ago #7999 via ccip
token discovered 2026-09-03 03:39:24 UTC · 2 d ago 2 contracts today
first liquid 2026-09-04 12:46:18 UTC · 16 h ago a chain quoted liquid
first alert 2026-09-04 12:46:19 UTC · 16 h ago multi_chain_liquid, sent 16 h ago
reported chains binance, ethereum — 2 of 2

Where this token lives

ethereum mint burn via ccip 5

0xc477b6dfd26ec2460b3b92de18837fd476ea7549 open

liquidlast verified 16 h ago

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

bridge_transfer

{"tx":"0x57de977a85b252f47217b5373f5b8eb865292ab806a1263faf166e566d0d050b","adapter":"ccip"}

binance canonical via ccip 3

0xea37a8de1de2d9d10772eeb569e28bfa5cb17707 open

liquidlast verified 16 h ago

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

registry

{"tx":"0x57de977a85b252f47217b5373f5b8eb865292ab806a1263faf166e566d0d050b","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 binance 1 of 1 reachable

ethereum ccip 0x57de977a… 36 h ago

from ethereum 1 of 1 reachable

binance ccip 0xfad83739… 33 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8389	2 d ago	ccipethereum → binance	0x04614042…4d6f36	SKIPPED_DUPLICATE	13 h
#7999	2 d ago	ccipbinance → ethereum	0x97287400…5c8a05	SKIPPED_DUPLICATE	11 h

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	16 h ago	SENT	16 h ago	754

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