arbitrum
mint burn · via layerzero
confirmed
0x0f69945a…ea448bsame
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
inferred
0x0f69945a…ea448bsame
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
binance
mint burn · via layerzero
confirmed
0x0f69945a…ea448bsame
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
optimism
mint burn · via layerzero
confirmed
0x0f69945a…ea448bsame
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
base
canonical · via layerzero
confirmed
0x0f694240…7b43a8
open
illiquidpools hold $0, under the floor6
Peer map: the protocol names this contract as a peerstrong +5
solana
mint burn · via layerzero
confirmed
decimals differ
E5K7ZfTRFC…46omni
open
illiquidpools hold $0, under the floor6
Peer map: the protocol names this contract as a peerstrong +5
polygon
canonical · via layerzero
confirmed
0x0f69945a…ea448bsame
open
illiquidpools hold $0, under the floor4
Bridge registry lists itstrong +3