KIP
KIP Protocol
status fully reported 3/3 checked · 3 liquid · 3 reported · hot
first bridged 3 d ago
arrived via axelar
contracts 3 on 3 chains
confirmed by a transfer 3 of 3
liquidity 3 of 3 chains checked · 3 liquid
checking hot
already alerted on arbitrum, binance, ethereum
Lifecycle
first pin received
2026-09-03 06:06:42 UTC · 2 d ago
#7709 via axelar
token discovered
2026-09-02 05:18:33 UTC · 3 d ago
3 contracts today
first liquid
2026-09-02 05:29:59 UTC · 3 d ago
a chain quoted liquid
first alert
2026-09-02 05:29:59 UTC · 3 d ago
multi_chain_liquid, sent 30 h ago
reported chains
arbitrum, binance, ethereum — 3 of 3
Where this token lives
arbitrum
mint burn
via axelar
5
0xf63b14f5ee5574e3f337b2796bbdf6dcfb4e2cb7same
copy
open
liquid last verified 3 d ago
Every source here is an inference. A contract on this chain has not confirmed the link itself.
bridge_transfer +5 {"tx":"0x53e11f8c164b49abb787b89a8210b8a714bf245973f1a7e2e0161b53aafab704","adapter":"axelar"}
binance
mint burn
via axelar
5
0xf63b14f5ee5574e3f337b2796bbdf6dcfb4e2cb7same
copy
open
liquid last verified 3 d ago
Every source here is an inference. A contract on this chain has not confirmed the link itself.
bridge_transfer +5 {"tx":"0x33f82f1bd064497f53c7b67311bf337b2c8beac3dc1b888c97e76f92d46dd2a7","adapter":"axelar"}
ethereum
canonical
via axelar
3
0x946fb08103b400d1c79e07acccdef5cfd26cd374
copy
open
liquid last verified 3 d ago
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0x53e11f8c164b49abb787b89a8210b8a714bf245973f1a7e2e0161b53aafab704","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 arbitrum
2 of 2 reachable
from binance
2 of 2 reachable
from ethereum
2 of 2 reachable
Pins behind this token
Alerts
Kind Created State Sent Telegram id
multi_chain_liquid 3 d ago
SENT
30 h ago 29