2
3 contracts on 2 chains · 3 routes via LZLayerZero2 contracts on solana. A wrapper beside the canonical is normal; a clone reusing the ticker looks the same. The one a transfer confirmed outranks the one matched by symbol. Compare below ↓
binance
canonical · via layerzero
critical
confirmed
added
0x000ae314…4f556a
open
solana
canonical · via layerzero
confirmed
2 on this chain
added
ASTERYpc2E…YVw45Z
open
0x1dcfafba…c930a3strong +5solana
canonical
confirmed
2 on this chain
FTB3qfwrXL…XRrrrx
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
solana ASTERYpc2E…YVw45Z → binance 0x000ae314…4f556a |
LZLayerZero | confirmed | 2zpjjRFzhm…QeDGt9 | 14 d ago |
binance 0x000ae314…4f556a → solana ASTERYpc2E…YVw45Z |
LZLayerZero | confirmed | 0x1dcfafba…c930a3 | 14 d ago |
binance 0x000ae314…4f556a → solana FTB3qfwrXL…XRrrrx |
LZLayerZero | confirmed | 0x1dcfafba…c930a3 | 14 d ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.
| Kind | Created | State | Sent | Rechecks | Outcome | Telegram |
|---|---|---|---|---|---|---|
| multi_chain_liquid | 14 d ago | SENT | 14 d ago | 0 | decided | 2229 |