avalanche
mint burn · via layerzero
confirmed
0x48090109…96d75dsame
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
0x48090109…96d75dsame
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
sonic
mint burn · via layerzero
confirmed
0x48090109…96d75dsame
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
unichain
mint burn · via layerzero
confirmed
0x48090109…96d75dsame
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
mint burn · via layerzero
confirmed
0x62344be8…6900b1
open
illiquidpools hold $0, under the floor5
Peer map: the protocol names this contract as a peerstrong +5
bera
mint burn · via layerzero
confirmed
0x316cd396…f64514
open
illiquidpools hold $0, under the floor5
Peer map: the protocol names this contract as a peerstrong +5
ethereum
canonical · via layerzero
confirmed
0xd3fd6320…be3094
open
illiquidpools hold $0, under the floor5
Peer map: the protocol names this contract as a peerstrong +5
hyperevm
mint burn · via layerzero
confirmed
0x04716db6…d07720
open
illiquidpools hold $0, under the floor5
Peer map: the protocol names this contract as a peerstrong +5
solana
mint burn · via layerzero
inferred
decimals differ
7bxM8cRFZp…VyBmqE
open
illiquidpools hold $0, under the floor5
Peer map: the protocol names this contract as a peerstrong +5
arbitrum
canonical · via layerzero
confirmed
0x48090109…96d75dsame
open
illiquidpools hold $0, under the floor3
Bridge registry lists itstrong +3