PYR

PYR Token

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

Lifecycle

first pin received 2026-09-03 06:06:14 UTC · 2 d ago #6467 via portal_bridge
token discovered 2026-09-03 08:05:01 UTC · 35 h 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 lock mint wrapper via portal_bridge 8

0x36612dcf8a8bf0755bd33a955fda55000595e917 open

illiquidpools hold $0, under the floor

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

registry	+3	{"tx":"0x95442f06229d1b8a535a0caa4b203c807f4328edec79c6e5b6e8fdba0a2bb2d0","from":"bridge_pin"}
derivation	+5	{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0x3ee18b2214aff97000d974cf647e7c347e8fa585","originChainId":5}

polygon mint burn via polygon_bridge 13

0x430ef9263e76dae63c84292c3409d61c598e9682same open

illiquidloses 2257 bps · 22.57% round-trip

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

derivation	+5	{"via":"origin_from_index","adapter":"portal_bridge","originChainId":5}
same_address	+3	{"chain":"polygon"}
derivation	+5	{"via":"rootToChildToken","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}

ethereum canonical via polygon_bridge shadowed · not checked 8

0x430ef9263e76dae63c84292c3409d61c598e9682same open

unknownBALANCE_READ_FAILED — not a negative result

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

registry	+3	{"tx":"0x0e9303eb98d93390f177d4f47c3aabd0319a3d6c322759b4872f27325afd8541","from":"bridge_pin"}
derivation	+5	{"via":"pin_source","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}

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

polygon portal_bridge, polygon_bridge 0x0e9303eb… 27 h ago

from polygon 1 of 1 reachable

ethereum portal_bridge 0x0d33ffaa… 35 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7420	2 d ago	polygon_bridgeethereum → polygon	0x0e9303eb…fd8541	DISCOVERED	9 h
#6498	2 d ago	portal_bridgepolygon → ethereum	0x440e4c9b…5a1f86	SKIPPED_DUPLICATE	2 h 6 min
#6467	2 d ago	portal_bridgeethereum → polygon	0x95442f06…2bb2d0	DISCOVERED	1 h 59 min

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