How HOPTRAIL works.

1. A token launches. The indexer reads every TokenLaunched event of the Pons V2 factory on Robinhood Chain (chain id 4663) and opens a file within about a minute.
2. First pass. It lists the wallets that bought in the first blocks, follows the ETH that reached each of them shortly before the buy, and groups buyers by the wallet that funded them.
3. Across launches. Funders are compared with every earlier launch. A funder seen before links this token to a ring.
4. Fees. Claims of the Pons creator fee are followed out of the fee escrow, hop by hop, until the ETH reaches an exchange, a bridge, a contract or an old wallet.
5. Written down. Each file is hashed. Once a day, the Merkle root of all files is anchored on-chain, so no file can be edited quietly afterwards.

Reading every file is free. There is no account, no login and no tracking of what you look at.

A file is a list of short, neutral sentences. Each one carries red footnote numbers; the footnotes, in the margin on a wide screen and under the sentence on a phone, name the transaction, address or block that backs it. The same sections appear for every token:

Deployer and creator

Who sent the launch transaction, through which contract (LaunchAndBuy or another launcher), and who funded that wallet.

Early buyers

Wallets that bought in the first blocks and the share of supply they took.

Clusters

Early buyers grouped by funder, with how much they bought and how much they still hold.

Rings

Funders of this token that also funded early buyers of earlier launches.

Creator fee trail

The creator fee recipient, its claims from the Pons escrow and where that ETH went. ETH leaving is drawn in red ink.

Holders and volume

Top holders now, 24 h volume against the number of unique traders.

Change log

On-chain changes (fee recipient proposals, claims) and every correction to the file. Nothing is removed from it.

A file still on its first pass is marked building and refreshes itself every few seconds.

Early buyer

A wallet that received the token from the Pons pool in the launch block or the next few blocks (the file says how many blocks were counted). Transfers between wallets are not buys.

Funder

The wallet that sent an early buyer the ETH it bought with, within a fixed window before the buy (the file shows the window, e.g. “within 22 min”). The funding transaction is always in the footnote, so you can see which transfer was used.

Cluster

Two or more early buyers with the same funder. A cluster is shown with its wallet count, the supply it bought, the supply it holds now and the funding and buy transactions.

Ring

A set of funders whose funded wallets bought early in at least two Pons V2 launches. Rings grow as new launches reuse the same funders or collectors. A ring id (like r-7c41) stays stable.

Collector

A wallet that receives ETH from several funded wallets after they sell (a sweep).

Fee trail

The path of ETH claimed from the Pons creator fee escrow: claim, then each transfer out of the recipient, up to a fixed number of hops or until it reaches a contract, exchange, bridge or old wallet.

Supply %

Tokens divided by total supply at the time stated. Pool and known contracts are labelled and left out of holder shares where the sentence says so.

• On-chain facts are not proof of intent or wrongdoing. A funder may be an exchange hot wallet, a bridge, a market maker or a friend. Wallets can change hands.
• Funding is followed only within the window and hop depth stated in the file. Money that moves through an exchange, a bridge or a mixer is not followed further.
• Clusters can include wallets that are unrelated and miss wallets that are related but funded differently.
• Volume and holder numbers come from on-chain data and the Pons API at the time shown; they change every block.
• An empty section means nothing was found, not that nothing happened.
• HOPTRAIL can be wrong. Corrections are published in the change log and never hidden.

Facts, not opinions. You judge.

1. The same facts for every token. Every Pons V2 launch gets the same sections, built by the same code. No token is singled out or skipped.
2. Only what can be linked. A sentence is published only if every claim in it points to a transaction, an address or a block anyone can check.
3. No scores, no labels. No risk score, no traffic light, no “scam”, “rug” or “insider”. Sentences say what moved, where and when.
4. No personal data. No names, no faces, no social accounts, no guesses about who owns a wallet. Public contract labels (pool, escrow, launcher) are the only labels.
5. Open corrections. Errors are corrected in the open: the change log keeps the old and the new version with the date.
6. Right of reply. The people behind a token can post a signed on-chain note next to any fact. It is shown as written.
7. Not for sale. Nobody can pay to change, delay or remove a fact. Holding $TRAIL does not change any file.
8. Security issues first in private. A live exploit is reported privately to the affected team before it is described in a file.

Every file has a fact hash: keccak256 of its sections in a canonical form. Once per UTC day the leaves keccak256(abi.encodePacked(token, factHash)) of every file published that day form a Merkle tree (sorted pairs; an odd last node is carried up unchanged). Its root is anchored on Robinhood Chain by the TrailRecord contract. A day can be written once; a correction is a public amendment that keeps the old root readable.

On Record you can verify any file in your browser: the leaf and the proof are hashed locally and compared with the root read from the chain.

The TrailReply contract lets a token's launch deployer (when it is a plain wallet) or its current creator fee recipient post a note of up to 560 bytes next to one fact, or on the whole file. The contract checks the Pons V2 factory on every call, so only those wallets can post. Notes live in the event log; there is no admin and no delete. Use Reply to post one.

$TRAIL launches on Pons. Holding it (no lock, no staking) unlocks:

• Radar: a watchlist of tokens and wallets with alerts on Telegram or the web when a cluster sells, a creator fee recipient moves fees, or a ring wallet buys early in a new launch. More $TRAIL, more slots.
• Deeper traces: more hops and wider time windows on demand, and CSV export of a file.

Files stay free and identical for everyone. The $TRAIL creator fee pays for RPC, the indexer and the daily anchor transaction; those payments are visible on-chain like any other fee trail.

Launch

Official links only: this site, X @hoptraildotlive and Telegram @hoptraildotlive. The contract address is published here first.

Is a token with a big cluster a scam?

HOPTRAIL does not say. A cluster is a fact about transfers. Market makers, teams and communities also fund wallets. Read the receipts, read the creator's reply, and decide.

Why no risk score?

A score hides its reasons and invites gaming. A sentence with a transaction behind it can be checked, disputed and corrected.

Which tokens are covered?

Every token launched through the Pons V2 factory on Robinhood Chain, including launches through LaunchAndBuy and third-party launchers (shown as “launched via”).

How fast is a file ready?

Usually within a minute of the launch block. Clusters and rings fill in as the first pass finishes; the page refreshes itself while it says “building”.

A fact about my token is wrong. What now?

Post an on-chain reply on Reply and write to us on Telegram. If the data is wrong we correct it in the open; the change log keeps both versions.

Do you store who reads a file?

No accounts, no tracking. Radar stores only the watchlist you sign for and, if you add it, your Telegram handle.

Is this financial advice?

No. HOPTRAIL publishes on-chain facts. It does not recommend buying or selling anything.