Lookonchain export through 2026-06-11 15:50 UTC / Hyperliquid fills

Trader validation workspace.

Check whether public “smart money” wallet mentions produced repeatable on-chain signal. Start with the chart, then inspect wallet-level P&L, win rate, and grouped entry/exit episodes.

Mixed signal, wallet-specific. The aggregate looks profitable, but the edge concentrates in a few addresses and assets. Treat each wallet as a watchlist candidate, not an automatic copy signal.

Events validated 17

Unique addresses 11

Aggregate post-D1 net -$2.14M

Aggregate post-30d net +$16.15M

01 / Timeline inspector

Wallet P&L, entries, and exits.

Select a wallet, asset, and candle interval. The chart plots grouped Hyperliquid position episodes with the supporting stats beside it.

Loading grouped address timelines.

Position episodes are grouped from Hyperliquid open and close fills. This is a campaign-level view, not every individual fill marker.

02 / Address evidence

Next trades after the public post.

Filter by the next-trade D1 status. “Retention-limited” means the public Hyperliquid API has newer fills, but not the old window we needed.

Address	Post	Tags	Claim Evidence	Post D1 Net	Post 30d Net	Next Open	Next D1 Net	Status

03 / Current read

Wallet-specific, not label-specific.

Best signal 0xf3f...057c produced a strong BTC short after the 2025-03-17 post: +$4.94M D1 realized. The same wallet’s earlier next LINK long was negative, so it is context-sensitive.
Export freshness Re-scanned 8,899 Telegram messages from 9 HTML files. Latest message: 2026-06-11T15:50:39Z. The refreshed export contains 620 Hyperliquid wallet mentions; full 109-candidate revalidation hit Hyperliquid rate limits and needs a paced rerun.
Strong proof, no next trade 0xe4d...2c62 had +$9.70M pre-post realized evidence, but no new opening campaign inside 30 days after the post.
Do not blindly copy The first batch does not justify following all successful-trader mentions. The alert system should require wallet-specific history, recent fill availability, asset context, and size/liquidity checks.

04 / Next validators

Solana and EVM need decoded trades.

The RPCs are available from this conversation, but they should be stored as secrets and read through environment variables. This page intentionally does not print raw RPC URLs.

Solana SOLANA_RPC_URL provided

Ethereum ETHEREUM_RPC_URL provided

Optimism OPTIMISM_RPC_URL provided

Xai XAI_RPC_URL provided

Other EVM {CHAIN}_RPC_URL derive pattern

Next implementation: Solana should use signatures plus parsed transactions and token balance deltas to identify swaps. EVM should use logs, router ABIs, token transfers, and chain-specific RPC env vars. Raw transfers should not be scored as trades.