Token Dashboard
tokens
2788
contracts
8846
confirmed
7203 of 8846
chains seen
14
unmeasured
94
queued
0

INKY

name unknown
status
illiquid4/4 checked · 0 liquid · warm
first bridged
2 d ago
arrived via
layerzero
contracts
5 on 4 chains
confirmed by a transfer
4 of 5
liquidity
4 of 4 chains checked · 0 liquid
checking
warm
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-06 13:59:38 UTC · 21 h ago #9336 via layerzero
  2. token discovered 2026-09-05 12:33:06 UTC · 2 d ago 5 contracts today
  3. first liquid pending not yet
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

More than one contract on binance (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
6
0x2224e03c2ec2586d897a73e838221bb6d1b8c607same 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":"INKY","source_tx":null,"message_id":"1404656246208069664","message_ts":"2025-08-12T02:42:26","source_url":"https://layerzeroscan.com/address/0x2224E03c2ec2586d897A73e838221BB6D1b8C607","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1404656246208069664","source_kind":"oft_address","curator_liquidity":false}
peer_map+5{"via":{"address":"0x776e4eab40263f48b4c107972b69825e9b7d2544","chainSlug":"base"},"adapter":"layerzero","oftAdapter":"0xd0345cc8aee1e487901ee526154a83dba2824c7c","unwrappedTo":"0x2224e03c2ec2586d897a73e838221bb6d1b8c607"}
binance mint burn via layerzero
6
0xd10ddb7de637d08ae1df3654052cdcf4894c69f1 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":"INKY","source_tx":null,"message_id":"1404656246208069664","message_ts":"2025-08-12T02:42:26","source_url":"https://layerzeroscan.com/address/0x2224E03c2ec2586d897A73e838221BB6D1b8C607","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1404656246208069664","source_kind":"oft_address","curator_liquidity":false}
peer_map+5{"via":{"address":"0x776e4eab40263f48b4c107972b69825e9b7d2544","chainSlug":"base"},"adapter":"layerzero"}
polygon mint burn via layerzero
6
0x2224e03c2ec2586d897a73e838221bb6d1b8c607same 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":"INKY","source_tx":null,"message_id":"1404656246208069664","message_ts":"2025-08-12T02:42:26","source_url":"https://layerzeroscan.com/address/0x2224E03c2ec2586d897A73e838221BB6D1b8C607","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1404656246208069664","source_kind":"oft_address","curator_liquidity":false}
peer_map+5{"via":{"address":"0x776e4eab40263f48b4c107972b69825e9b7d2544","chainSlug":"base"},"adapter":"layerzero"}
binance mint burn
potential · no transfer seen 5
0x776e4eab40263f48b4c107972b69825e9b7d2544same open
illiquidpools hold $0, under the floor

Every source here is an inference. A contract on this chain has not confirmed the link itself.

same_address+3{"chain":"binance"}
codehash+2{"codehash":"0xca02b2a07456d984fb02e479a048835b7a1acaa6fd2ca89d54defb2ce7afb429"}
base canonical via layerzero
4
0x776e4eab40263f48b4c107972b69825e9b7d2544same 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":"INKY","source_tx":null,"message_id":"1404656246208069664","message_ts":"2025-08-12T02:42:26","source_url":"https://layerzeroscan.com/address/0x2224E03c2ec2586d897A73e838221BB6D1b8C607","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1404656246208069664","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0xbdc464b8397d9bb461acc9f3dba271b2dce1b5e368276215abfa09497305be22","from":"bridge_pin"}

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 base 2 of 3 reachable
binance layerzero 0xd2c9df4b… 21 h ago
polygon layerzero 0xbdc464b8… 21 h ago
show 1 unreachable hide unreachable
ethereum no transfer seen
from binance 2 of 3 reachable
base layerzero 0x8ed2e53b… 21 h ago
polygon layerzero 0x6f92635c… 21 h ago
show 1 unreachable hide unreachable
ethereum no transfer seen
from ethereum 3 of 3 reachable
base layerzero 0x167b0e29… 21 h ago
binance layerzero 0xbc4ae069… 21 h ago
polygon layerzero 0x511d8d15… 21 h ago
from polygon 3 of 3 reachable
base layerzero 0x36103ee5… 21 h ago
binance layerzero 0xa01490a7… 21 h ago
ethereum layerzero 0xa5562f41… 21 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9336 21 h ago layerzerobase → polygon 0xbdc464b8…05be22 DISCOVERED 11 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.

Exclude this token if it is junk or not worth watching. Liquidity stops being checked and nothing more is searched for it; its contracts, evidence, routes and history stay, its pins are still recorded, and it can be tracked again from the Excluded page.

Every address above came from an on-chain read. The evidence trail shows which read produced it.