Token Dashboard
tokens
3706
contracts
11650
confirmed
9885of 11650
chains
15
unmeasured
50
queued
0

FCANARY Forge Canary

2 contracts on 2 chains · 2 routes via LayerZero
status
illiquid2/2 checked · 0 liquid · cold
first bridged
2 mo ago2026-09-02 20:54
confirmed by a transfer
2 of 2every contract seen in a tx
already alerted
nothing yet
pins
0

Contracts

binance mint burn · via layerzero confirmed
0x292257fa…3ad763same open
illiquidpools hold $0, under the floor10
Same address as on another chainweak +3
Same bytecode as a known contractweak +2
Peer map: the protocol names this contract as a peerstrong +5
…
base canonical · via layerzero confirmed
0x292257fa…3ad763same open
illiquidpools hold $0, under the floor3
Bridge registry lists itstrong +3
…

Routes

2 confirmed · 0 possible
LaneBridgeEvidenceProofLast seen
binance 0x292257fa…3ad763 → base 0x292257fa…3ad763 LayerZero confirmed 0x4f3d1e72…0aa226 2 mo ago
base 0x292257fa…3ad763 → binance 0x292257fa…3ad763 LayerZero confirmed 0x830eb6b4…2032cc 2 mo ago

How it moves

LZ · 2 tx baseilliquid binanceilliquid
transfer seen (moving)peer map onlyring = liquidity on that chain

Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.

from from the index ▾

Source chain

bridge LayerZero ▾

Bridge

Lifecycle

Token discovered
2026-09-02 20:54 UTC · 2 mo ago · 2 contracts today
First pin received
no pin linked (added by hand, or before pins were tracked)
First liquid
not yet
First alert
no chain is liquid yet
All chains reported
none yet