GAIN

name unknown

status: illiquid2/2 checked · 0 liquid · warm
first bridged: 2 d ago
arrived via: layerzero
contracts: 3 on 2 chains
confirmed by a transfer: 3 of 3
liquidity: 2 of 2 chains checked · 0 liquid
checking: warm
already alerted on: nothing yet
pins: 1

Lifecycle

first pin received 2026-09-06 14:00:02 UTC · 21 h ago #9361 via layerzero
token discovered 2026-09-05 12:33:06 UTC · 2 d ago 3 contracts today
first liquid pending not yet
first alert pending not yet
reported chains pending none yet

Where this token lives

More than one contract on ethereum (2). That is allowed — a bridge wrapper and the canonical token are separate contracts and trade in separate pools (§3) — but it is also what a clone reusing the ticker looks like. Compare the evidence below: a contract confirmed by the bridge itself outranks one matched only by symbol.

ethereum canonical via layerzero 9

0xccdbb9c8e43f50407c58f81407a16549e2a475dd open

illiquidpools hold $0, under the floor

2 of 3 sources are protocol-attested — a contract confirmed this link.

discord	+1	{"notes":[],"proven":false,"ticker":"GAIN","source_tx":null,"message_id":"1418718609487958067","message_ts":"2025-09-19T22:01:15","source_url":"https://layerzeroscan.com/address/0x2295692C812a904d132cFCf1560653a6ff927D75","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1418718609487958067","source_kind":"oft_address","curator_liquidity":false}
registry	+3	{"tx":"0x45e58e6a84226d4f80a2f7cb20a79d3a69b84b1247995fbfec40aa95a66b7f68","from":"bridge_pin"}
registry	+5	{"via":"OFTAdapter.token","adapter":"layerzero","oftAdapter":"0x2295692c812a904d132cfcf1560653a6ff927d75"}

binance mint burn via layerzero 6

0xacf5a368ec5bb9e804c8ac0b508daa5a21c92e13 open

illiquidpools hold $0, under the floor

1 of 2 sources are protocol-attested — a contract confirmed this link.

discord	+1	{"notes":[],"proven":false,"ticker":"GAIN","source_tx":null,"message_id":"1418718609487958067","message_ts":"2025-09-19T22:01:15","source_url":"https://layerzeroscan.com/address/0x2295692C812a904d132cFCf1560653a6ff927D75","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1418718609487958067","source_kind":"oft_address","curator_liquidity":false}
peer_map	+5	{"via":{"address":"0x2295692c812a904d132cfcf1560653a6ff927d75","chainSlug":"ethereum"},"adapter":"layerzero"}

ethereum canonical via layerzero 5

0x7a8caffeb11047e90affc9f7527103b0334572e6 open

illiquidpools hold $0, under the floor

1 of 1 sources are protocol-attested — a contract confirmed this link.

peer_map

{"via":{"address":"0xacf5a368ec5bb9e804c8ac0b508daa5a21c92e13","chainSlug":"binance"},"adapter":"layerzero","oftAdapter":"0xba159054636e69080ae7c756319e5c85498efeb0","unwrappedTo":"0x7a8caffeb11047e90affc9f7527103b0334572e6"}

How it moves between chains

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.

from binance 1 of 1 reachable

ethereum layerzero 0xd9023fef… 21 h ago

from ethereum 1 of 1 reachable

binance layerzero 0x45e58e6a… 21 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#9361	21 h ago	layerzeroethereum → binance	0x45e58e6a…6b7f68	DISCOVERED	14 min

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.