eATH

eigenATH

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

Lifecycle

first pin received 2026-09-03 06:06:39 UTC · 2 d ago #7266 via layerzero
token discovered 2026-09-03 15:25:37 UTC · 2 d ago 2 contracts today
first liquid pending not yet
first alert pending not yet
reported chains pending none yet

Where this token lives

ethereum mint burn via layerzero 5

0x68ff002b30360d3c613c2d6bc7e8c3e1f94883b9 open

illiquidloses 1590 bps · 15.90% round-trip

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

peer_map

{"via":{"address":"0x1903aa5b603819b9debd2f4b202b686e9e393aff","chainSlug":"arbitrum"},"adapter":"layerzero"}

arbitrum canonical via layerzero 3

0x1903aa5b603819b9debd2f4b202b686e9e393aff open

illiquidpools hold $0, under the floor

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

registry

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

ethereum layerzero 0x290cc5c4… 2 d ago

from ethereum 1 of 1 reachable

arbitrum layerzero 0x962691bf… 2 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7266	2 d ago	layerzeroarbitrum → ethereum	0x290cc5c4…e9463e	DISCOVERED	9 h

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