FCANARY
Forge Canary
status illiquid 2/2 checked · 0 liquid · cold
first bridged 2 d ago
arrived via layerzero
contracts 2 on 2 chains
confirmed by a transfer 2 of 2
liquidity 2 of 2 chains checked · 0 liquid
checking cold
already alerted on nothing yet
pins 0
Lifecycle
first pin received
pending
no pin linked (added by hand, or before pins were tracked)
token discovered
2026-09-02 20:54:17 UTC · 2 d ago
2 contracts today
first liquid
pending
not yet
first alert
pending
not yet
reported chains
pending
none yet
Where this token lives
binance
mint burn
via layerzero
10
0x292257fa9503486ab16aa23a535ea784993ad763same
copy
open
illiquid pools hold $0, under the floor
1 of 3 sources are protocol-attested — a contract confirmed this link.
same_address +3 {"chain":"binance"} codehash +2 {"codehash":"0x6d650ef7d052dcd4f517b1e2764417bbc16390ef995a74c2710d9ee6c8367663"} peer_map +5 {"via":{"address":"0x292257fa9503486ab16aa23a535ea784993ad763","chainSlug":"base"},"adapter":"layerzero"}
base
canonical
via layerzero
3
0x292257fa9503486ab16aa23a535ea784993ad763same
copy
open
illiquid pools hold $0, under the floor
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0x830eb6b43b8088d2b49d57a6e3b31771279db7f5ec251f7f003e6723a12032cc","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
1 of 1 reachable
from binance
1 of 1 reachable