VANRY

status: unmeasured2/2 checked · 0 liquid · warm
first bridged: 22 h ago
arrived via: debridge
contracts: 3 on 2 chains
confirmed by a transfer: 2 of 3
liquidity: 2 of 2 chains checked · 0 liquid · 1 unmeasured
checking: warm
already alerted on: nothing yet
pins: 1

Lifecycle

first pin received 2026-09-03 06:07:54 UTC · 2 d ago #8777 via debridge
token discovered 2026-09-03 21:23:22 UTC · 22 h ago 3 contracts today
first liquid 2026-09-03 23:06:17 UTC · 20 h ago a chain quoted liquid
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 lock mint wrapper via debridge 10

0xa92e6aad4c7b8418e4daf203970c3fc9c4259753 open

illiquidpools hold $0, under the floor

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

registry	+5	{"via":"submission_claim","adapter":"debridge","claimTx":"0x80d24a959a577ccde98d0a851e0ccbd775b451f7fa2b3d854a9029346b38e903"}
derivation	+5	{"via":"Gate.getDebridge","gate":"0x43de2d77bf8027e25dbd179b491e8d64f38398aa","adapter":"debridge","debridgeId":"0xe78a13ae662697d333c57f5e425d9bd273f97b00c8c4c6b77774dc59fce40b68"}

ethereum canonical via debridge shadowed · not checked potential · no transfer seen 5

0x8de5b80a0c1b02fe4976851d030b36122dbb8624same open

unknownBALANCE_READ_FAILED — not a negative result

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

same_address	+3	{"chain":"ethereum"}
offchain_list	+2	{"via":"token-list","symbol":"VANRY","adapter":"debridge","decimals":18,"debridgeChainId":1,"decimalsDiffersFromSource":false}

polygon canonical via debridge 3

0x8de5b80a0c1b02fe4976851d030b36122dbb8624same open

illiquidpools hold $0, under the floor

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

registry

{"tx":"0x83ab8c43f15e6eee5d8fef43bc8a3a905e00c13b374b997b042935c57ad177d3","from":"bridge_pin"}

How it moves between chains

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 ethereum 0 of 1 reachable

No transfer has been seen leaving ethereum.

show 1 unreachable hide unreachable

polygon no transfer seen

from polygon 1 of 1 reachable

ethereum debridge 0x83ab8c43… 22 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8777	2 d ago	debridgepolygon → ethereum	0x83ab8c43…d177d3	DISCOVERED	15 h

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