RBTC
RBTC
status partly reported 4/4 checked · 2 liquid · 2 reported · hot
first bridged 2 d ago
arrived via layerzero
contracts 4 on 4 chains
confirmed by a transfer 4 of 4
liquidity 4 of 4 chains checked · 2 liquid
checking hot
already alerted on arbitrum, base
pins 0
Lifecycle
first pin received
pending
no pin linked (added by hand, or before pins were tracked)
token discovered
2026-09-02 21:52:54 UTC · 2 d ago
4 contracts today
first liquid
2026-09-04 12:48:30 UTC · 11 h ago
a chain quoted liquid
first alert
2026-09-04 12:48:30 UTC · 11 h ago
multi_chain_liquid, sent 11 h ago
reported chains
arbitrum, base — 2 of 4
Where this token lives
base
mint burn
via layerzero
10
0x441fcb23dfe8289cf572126fedcf450974adc891same
copy
open
liquid last verified 11 h ago
1 of 3 sources are protocol-attested — a contract confirmed this link.
same_address +3 {"chain":"base"} codehash +2 {"codehash":"0xfd274085aacb34d190c9a8e3ce80c406b16146a3c6683db1e6bd805826895bc4"} peer_map +5 {"via":{"address":"0x441fcb23dfe8289cf572126fedcf450974adc891","chainSlug":"arbitrum"},"adapter":"layerzero"}
ethereum
mint burn
via layerzero
5
0x1e44f98cc78d505a61f63b26d13b116cf51dbb87
copy
open
illiquid pools hold $0, under the floor
1 of 1 sources are protocol-attested — a contract confirmed this link.
peer_map +5 {"via":{"address":"0x441fcb23dfe8289cf572126fedcf450974adc891","chainSlug":"arbitrum"},"adapter":"layerzero"}
solana
mint burn
via layerzero
decimals differ from source
5
8yev7nLen2PFN2uYGhzsUbu243wMa9z4ZrCwuXs6DEQw
copy
open
illiquid pools hold $0, under the floor
1 of 1 sources are protocol-attested — a contract confirmed this link.
peer_map +5 {"via":{"address":"0x441fcb23dfe8289cf572126fedcf450974adc891","chainSlug":"arbitrum"},"adapter":"layerzero","oftStore":"9kNJtqujAadCDxaQg5SB2pzRKiMThUe1VTreJNQovQ4E","resolvedMint":"8yev7nLen2PFN2uYGhzsUbu243wMa9z4ZrCwuXs6DEQw"}
arbitrum
canonical
via layerzero
3
0x441fcb23dfe8289cf572126fedcf450974adc891same
copy
open
liquid last verified 11 h ago
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0xf04e08691171ed470f5d22a1feeda7ab75e60aa2706c0e13720eabd40faf5700","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
3 of 3 reachable
from base
3 of 3 reachable
from ethereum
3 of 3 reachable
from solana
2 of 3 reachable
show 1 unreachable
hide unreachable
→
arbitrum
no transfer seen
Alerts
Kind Created State Sent Telegram id
multi_chain_liquid 11 h ago
SENT 11 h ago 758