RED

Redstone

status: partly reported3/3 checked · 2 liquid · 2 reported · hot
first bridged: 2 d ago
arrived via: portal_bridge
contracts: 4 on 3 chains
confirmed by a transfer: 4 of 4
liquidity: 3 of 3 chains checked · 2 liquid
checking: hot
already alerted on: base, ethereum
pins: 2

Lifecycle

first pin received 2026-09-03 01:56:10 UTC · 2 d ago #4878 via portal_bridge
token discovered 2026-09-03 02:51:35 UTC · 2 d ago 4 contracts today
first liquid 2026-09-04 06:15:02 UTC · 21 h ago a chain quoted liquid
first alert 2026-09-04 06:15:02 UTC · 21 h ago multi_chain_liquid, sent 21 h ago
reported chains base, ethereum — 2 of 3

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.

hyperevm canonical via portal_bridge 8

0x82e1a33100f52d8e4af4f3c0ab2f47799c0447b4 open

illiquidpools hold $0, under the floor

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

registry	+3	{"tx":"0xdd21c26588101f8b684c021eaf509e7cb9e70aefee8462632984a77bd09f2d43","from":"bridge_pin"}
derivation	+5	{"via":"origin_from_index","adapter":"portal_bridge","originChainId":47}

base canonical via portal_bridge 8

0x4eb92702ba4cfbf80561bad64d89c706ac824960 open

liquidlast verified 21 h ago

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

registry	+3	{"tx":"0x0188b279c72938c416ffede3908e905ed3d690c8c3b77d8304dcfaf7d7b1d83d","from":"bridge_pin"}
derivation	+5	{"via":"origin_from_index","adapter":"portal_bridge","originChainId":30}

ethereum mint burn via portal_bridge 10

0xc43c6bfeda065fe2c4c11765bf838789bd0bb5de open

liquidlast verified 21 h ago

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

derivation	+5	{"via":"ntt_peer","adapter":"portal_bridge","manager":"0x441adfb941a2159ce11394fb003297751b74fa0a","wormholeId":2,"peerManager":"0xe9315adf65c8bd4d21d9ba03b4a25b7c8c8500d7"}
derivation	+5	{"via":"ntt_peer","adapter":"portal_bridge","manager":"0x84b4ecc4b936d677b23369708a6577f29206e982","wormholeId":2,"peerManager":"0xe9315adf65c8bd4d21d9ba03b4a25b7c8c8500d7"}

ethereum lock mint wrapper via portal_bridge shadowed · not checked 5

0x10b4cfc70375928d76f38118252fba2a99ae59fe open

liquidlast verified 23 h ago

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

derivation

{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0x3ee18b2214aff97000d974cf647e7c347e8fa585","originChainId":30}

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

ethereum portal_bridge 0x0188b279… 33 h ago

show 1 unreachable hide unreachable

hyperevm no transfer seen

from ethereum 1 of 2 reachable

base portal_bridge 0xaf17a156… 2 d ago

show 1 unreachable hide unreachable

hyperevm no transfer seen

from hyperevm 1 of 2 reachable

ethereum portal_bridge 0xdd21c265… 2 d ago

show 1 unreachable hide unreachable

base no transfer seen

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8266	2 d ago	portal_bridgebase → ethereum	0xe164abf9…73d41c	SKIPPED_DUPLICATE	11 h
#4878	2 d ago	portal_bridgebase → ethereum	0x0188b279…b1d83d	DISCOVERED	3 h 29 min

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	21 h ago	SENT	21 h ago	579

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