0x4621b7a9c75199271f773ebd9a499dbd165c3191
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x4092e09a3ae4cdd9a5cbc1e0bda307c800b9ffe91def9aaf7325a39ccdad6ad8","from":"bridge_pin"} |
| derivation | +5 | {"via":"remoteToken","adapter":"base_bridge"} |
0x8ae125e8653821e851f12a49f7765db9a9ce7384
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x88250dcb8a1785d1ec4af351e3c3a52383fb78a9a164c0f606d62a4054506e01","from":"bridge_pin"} |
| derivation | +5 | {"via":"remoteToken","adapter":"optimism_bridge"} |
0x865377367054516e17014ccded1e7d814edc9ce4
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| derivation | +5 | {"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0x4621b7a9c75199271f773ebd9a499dbd165c3191"} |
| derivation | +5 | {"via":"remoteToken","adapter":"optimism_bridge","l2Chain":"optimism","l2Token":"0x8ae125e8653821e851f12a49f7765db9a9ce7384"} |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.
Each chain lists the directions a transfer has actually been seen taking. Directions with no transfer behind them are folded away per card and counted in its header. Derived routes are not shown at all.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #6733 | 4 d ago | optimism_bridgeoptimism → ethereum | 0x88250dcb…506e01 | DISCOVERED | 2 h 44 min |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| resend | 7 h ago | SENT | 7 h ago | 1143 |
| multi_chain_liquid | 3 d ago | SENT | 3 d ago | 701 |
Verdict. Add it if this is the token you want to watch; reject it if any contract is a twin, a clone or junk — a rejected token stays checked but is not alerted on again.
Every address above came from an on-chain read. The evidence trail shows which read produced it.