DATA

Streamr

status: liquid2/2 checked · 1 liquid · warm
first bridged: 29 h ago
arrived via: polygon_bridge
contracts: 3 on 2 chains
confirmed by a transfer: 3 of 3
liquidity: 2 of 2 chains checked · 1 liquid
checking: warm
already alerted on: nothing yet
pins: 2

Lifecycle

first pin received 2026-09-03 06:07:32 UTC · 2 d ago #8340 via polygon_bridge
token discovered 2026-09-03 18:02:40 UTC · 29 h ago 3 contracts today
first liquid 2026-09-04 22:42:49 UTC · 5 min 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 canonical via polygon_bridge 8

0x8f693ca8d21b157107184d29d398a8d082b38b76 open

liquid103 bps · 1.03% via kyberswap

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

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

polygon mint burn via debridge 10

0x3a9a81d576d83ff21f26f325066054540720fc34 open

illiquidpools hold $46, under the floor

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

derivation	+5	{"via":"rootToChildToken","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"}
registry	+5	{"via":"submission_claim","adapter":"debridge","claimTx":"0x20ac0739d2def15d90d5e62df01ea52156ac750e662de118ec97c141fcc9638a"}

ethereum canonical via debridge shadowed · not checked 3

0xbfb656bdacaabba784f3e9e616414df61d203dfe open

illiquidpools hold $0, under the floor

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

registry

{"tx":"0x1b0191baccecbc7f87ff1d652953d15a78c1430b7ab71f6a8b94f24c92d0f9cd","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 1 of 1 reachable

polygon polygon_bridge, debridge 0x1b0191ba… 25 h ago

from polygon 0 of 1 reachable

No transfer has been seen leaving polygon.

show 1 unreachable hide unreachable

ethereum no transfer seen

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8895	2 d ago	debridgeethereum → polygon	0x1b0191ba…d0f9cd	DISCOVERED	15 h
#8340	2 d ago	polygon_bridgeethereum → polygon	0x4c0918d9…358043	DISCOVERED	11 h

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