xSolvBTC
xSolvBTC
status partly reported 6/6 checked · 2 liquid · 2 reported · hot
first bridged 21 h ago
arrived via ccip
contracts 6 on 6 chains
confirmed by a transfer 5 of 6
liquidity 6 of 6 chains checked · 2 liquid
checking hot
already alerted on binance, ethereum
Lifecycle
first pin received
2026-09-03 06:06:14 UTC · 2 d ago
#6460 via ccip
token discovered
2026-09-03 21:47:12 UTC · 21 h ago
6 contracts today
first liquid
2026-09-04 06:50:45 UTC · 12 h ago
a chain quoted liquid
first alert
2026-09-04 06:50:45 UTC · 12 h ago
multi_chain_liquid, sent 12 h ago
reported chains
binance, ethereum — 2 of 6
Where this token lives
ethereum
mint burn
via ccip
5
0xd9d920aa40f578ab794426f5c90f6c731d159def
copy
open
liquid last verified 12 h ago
Every source here is an inference. A contract on this chain has not confirmed the link itself.
bridge_transfer +5 {"tx":"0xf5f363f6e30695c5c4e053ae2f01f29567777740072cbfcbc0292a629eee76de","adapter":"ccip"}
polygon
mint burn
potential · no transfer seen
5
0xc99f5c922dae05b6e2ff83463ce705ef7c91f077same
copy
open
illiquid pools hold $0, under the floor
Every source here is an inference. A contract on this chain has not confirmed the link itself.
same_address +3 {"chain":"polygon"} codehash +2 {"codehash":"0x69aef468bd58338231ea56861188725f4fdba75f3ee182db5cc93ab0d98ccb12"}
binance
canonical
via ccip
3
0x1346b618dc92810ec74163e4c27004c921d446a5
copy
open
liquid last verified 12 h ago
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0xf5f363f6e30695c5c4e053ae2f01f29567777740072cbfcbc0292a629eee76de","from":"bridge_pin"}
base
canonical
via ccip
3
0xc26c9099bd3789107888c35bb41178079b282561
copy
open
illiquid pools hold $0, under the floor
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0x7c01743c452c8127a69c1b7c0dcd283c78e6f6cb5bb103e068879b2fd7291bbf","from":"bridge_pin"}
arbitrum
canonical
via ccip
3
0x346c574c56e1a4aaa8dc88cda8f7eb12b39947ab
copy
open
illiquid pools hold $0, under the floor
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0x9a4f326dbc56f79a1ef9a03dab205a2203a96af5c273ff65ebd31d8f24e474e5","from":"bridge_pin"}
hyperevm
canonical
via ccip
3
0xc99f5c922dae05b6e2ff83463ce705ef7c91f077same
copy
open
illiquid pools hold $0, under the floor
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0x6a610ef784aba3fdc698111f9447a4fce1ad9a54380747a9afc2fca8ae675b44","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 5 reachable
show 3 unreachable
hide unreachable
→
base
no transfer seen
→
hyperevm
no transfer seen
→
polygon
no transfer seen
from base
1 of 5 reachable
show 4 unreachable
hide unreachable
→
arbitrum
no transfer seen
→
binance
no transfer seen
→
hyperevm
no transfer seen
→
polygon
no transfer seen
from binance
1 of 5 reachable
show 4 unreachable
hide unreachable
→
arbitrum
no transfer seen
→
base
no transfer seen
→
hyperevm
no transfer seen
→
polygon
no transfer seen
from ethereum
1 of 5 reachable
show 4 unreachable
hide unreachable
→
arbitrum
no transfer seen
→
base
no transfer seen
→
hyperevm
no transfer seen
→
polygon
no transfer seen
from hyperevm
2 of 5 reachable
show 3 unreachable
hide unreachable
→
arbitrum
no transfer seen
→
base
no transfer seen
→
polygon
no transfer seen
from polygon
0 of 5 reachable
No transfer has been seen leaving polygon.
show 5 unreachable
hide unreachable
→
arbitrum
no transfer seen
→
base
no transfer seen
→
binance
no transfer seen
→
ethereum
no transfer seen
→
hyperevm
no transfer seen
Pins behind this token
Alerts
Kind Created State Sent Telegram id
multi_chain_liquid 12 h ago
SENT
12 h ago 707
Merge history
When Winner Loser Contracts moved Evidence State
21 h ago
#1920
#1141
4
{"tx":"0x6a610ef784aba3fdc698111f9447a4fce1ad9a54380747a9afc2fca8ae675b44","bridge":"ccip","reason":"a delivered transfer connected contracts held by two assets","endpoint":"ethereum:0xd9d920aa40f578a
active