arbitrum
mint burn · via layerzero
confirmed
0x69ccc672…777777same
open
illiquidpools hold $0, under the floor11
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
avalanche
mint burn · via layerzero
confirmed
0x69ccc672…777777same
open
illiquidpools hold $0, under the floor11
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
binance
mint burn · via layerzero
confirmed
0x69ccc672…777777same
open
illiquidpools hold $0, under the floor11
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
ethereum
mint burn · via layerzero
confirmed
0x69ccc672…777777same
open
illiquidpools hold $0, under the floor11
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
hyperevm
mint burn · via layerzero
confirmed
0x69ccc672…777777same
open
illiquidpools hold $0, under the floor9
Same address as on another chainweak +3 Peer map: the protocol names this contract as a peerstrong +5
sonic
mint burn · via layerzero
confirmed
0x69ccc672…777777same
open
illiquidpools hold $0, under the floor9
Same address as on another chainweak +3 Peer map: the protocol names this contract as a peerstrong +5
unichain
mint burn · via layerzero
inferred
0x69ccc672…777777same
open
illiquidpools hold $0, under the floor8
Same address as on another chainweak +3 Peer map: the protocol names this contract as a peerstrong +5
base
canonical · via layerzero
confirmed
0x69ccc672…777777same
open
illiquidpools hold $0, under the floor4
Bridge registry lists itstrong +3