06Jenkins docs
Explore and coin pages
Where the board's data comes from, what the coin page shows, and how holders are counted.
The board
| Tab | Source |
|---|---|
| On Jenkins | Coins launched through Jenkins, from its database, with price and progress read live from each curve |
| All Pons | Every Pons V2 launch in the last 20,000 blocks (about 33 minutes), read from the factory's events; older pages on request |
| Near graduation, My launches | Filters over the same data; My launches reads the connected wallet's launches from the factory |
The coin page
- Chart: market cap in USD, one line built from the curve's trade tape, with buys and sells as dots and ranges of 1 h, 6 h, 24 h or all.
- Curve panel: progress to graduation, supply left on the curve, fees, traders seen, the token and curve addresses, and the collection with its art and, for skins, the live index.
- Trades: the tape, newest first, in USD.
- Holders: holder count, buys and sells, top-10 share, the creator's share, supply sitting in the curve or pool, the largest wallets and a bubble map.
- Your position: what the connected wallet holds and traded on this coin.
How holders are counted
Jenkins reads every Transfer of the token since launch and folds balances from them on the server, once per coin, then keeps the book growing. The curve, the Uniswap pool, the Pons contracts and the router count as venues, not holders. Buys and sells are counted from curve trades plus pool swaps, so a swap routed through an aggregator is one trade, not several transfers. Wallets that sent tokens to each other are linked in the bubble map; addresses with code are labelled as contracts. A busy coin takes a minute to read the first time.