how ranking works and the logs

how the order works, and every fix and mod action we've made.

how ranking works

follow = you'd act on their next launch or call · fade = you'd pass on it, or trade against it · avoid = you'd stay away. one device, one vote. votes set the order: net votes, follow − fade − avoid, with vote bursts left out unless you include them. rank numbers start at a card's first vote. on-chain numbers are reference only and never move a rank.

what are the comments?

comments are users' opinions. the site doesn't write, edit or feature them, and removes only by category. each one is signed anon · and a 4-character tag that stays the same within one thread and can't be linked across threads. there are no links, images or formatting; a tx signature can be attached and is checked to involve the card's wallets. a comment's author can delete it within 10 minutes; nobody can edit one.

the exact formula comments, best: the Wilson lower bound of up / (up + down) with z = 1.281 (80% confidence), 0 with no votes, ties to the newer comment. comments, top: up − down, ties to the newer comment. comments, new: newest first. comments, controversial: 0 if up = 0 or down = 0, otherwise (up + down) ^ (min(up, down) / max(up, down)).

why two parts?

votes are opinions; the on-chain side is a record. in simulations of a public consensus-rating algorithm, a coordinated 5 to 19% of raters could swing results, so votes get their own counts, burst exclusions and integrity line, and the on-chain numbers sit apart, inside each card, as reference. no score mixes the two.

what are the two kinds of candles?

the vote candles are visitors' votes: one per UTC day (14 days on each row, 30 in an opened card), each a day of the card's net votes. it opens where the day before closed, its wick reaches up by that day's follows and down by its fades and avoids, and its body is the day's net: teal and filled when up, amber and hollow when down, on a solid line at zero. the last close is the card's net. they are anonymous clicks, not price data: they can be farmed, and vote bursts count only when you include them. the price candles inside each opened card's on-chain box are on-chain: one per launch or call, from a follower's entry, green above and red below, with a dashed entry line. they are reference only and never move a rank; no number mixes the two.

why anonymous?

the votes are visitors' opinions, counted. nobody connects a wallet or signs anything: one device, one vote, bot-checked. anonymous votes can be brigaded, so vote bursts are marked and left out by default, each card shows how many were left out, and the on-chain side never moves. a cleared browser or a new network gets a new vote, so the counts are a signal of what visitors clicked, not a census of people.

how is the feed ordered?

the rank is net votes: follows minus fades minus avoids, counting only votes outside vote bursts unless you switch bursts on. ties go to the card with more votes, then the one listed earlier, then a fixed id order. a card gets a rank number from its first vote; until then it says 'no votes yet'. the feed has three orders: hot, new and top. none of them changes a rank number. hot: net votes on a log scale plus how recently it was posted, so a new post with a few votes can pass an old one with many. new: newest first. top: most net votes today, in 7 days or all time (UTC days), counting the votes outside vote bursts. there is no operator pinning, featuring or boosting; starter picks start at 0 like everyone. these are the only orders.

the exact formula net votes: counted follow − fade − avoid; with vote bursts included, the votes inside vote bursts are added. hot (log of net plus time): sign(n) · log10(max(|n|, 1)) + the posting time in seconds ÷ 45000, with n the net votes, so 12.5 hours of posting time weigh as much as ten times the net; the starter picks and the cards measured before the board opened share the time they were added together. new: the latest post first. top: the counted net of today's UTC day, of the last 7 UTC days, or of all time. ties in every order follow the rank order. this coin's dev is shown on the feed but left out of the rank. on-chain medians, inside each card, need at least 5 closed past the window and never enter a rank. grades and comment votes inside a vote burst, and comments inside a comment burst, are left out unless you include vote bursts.

what is a starter pick?

one of the devs and KOLs the board started with, picked from public community sources. a starter pick starts at 0 votes and is never pinned. an account is shown next to it only when two independent sources agree or its pump.fun profile names it.

what does posted by a visitor · unverified mean?

anyone can post a dev or kol by typing a name or @handle and pasting a wallet. the checker bot confirms the wallet has pump.fun activity; nobody checks that the name belongs to that wallet. reports for personal info or for pretending to be someone hide a visitor's name quickly.

what is a vote burst?

a stretch of votes on one card that arrives much faster than usual, mostly from new browsers or from one network, is marked as a vote burst. votes past a card's daily cap are marked too, and a moderator can mark or unmark a stretch (each one is logged in the corrections log). votes in a burst stay visible but are left out of the counts and the rank unless you include vote bursts. each opened card shows how many votes were left out, and how many of its votes come from browsers that voted on no other card.

why four windows?

a peer-reviewed study of 35,569 influencer posts (2021-22) found named coins averaged +1.8% after a day and −6.5% after thirty. one window flatters; four show the shape.

why not the peak?

a peak-only number floors everything at 1.0×, so a call can never print a loss. each receipt prints it once, labelled; no figure here uses it.

why clusters?

one creator wallet can hide a launcher who rotates wallets. wallets are linked by funding within 2 hops, with exchange and bridge funders filtered so strangers don't merge. when the filter misses one, the corrections log says so.

what doesn't this show?

why anyone did anything, whether a post was paid, or who owns a wallet. same slot does not prove same owner: bots buy in the create slot too. graduation can be bought, so each one says bought at launch or reached after.

on-chain definitions (19)

method loading · changes go in the corrections log

launches found
coins created by any wallet in the cluster. does not show: intent, or launches from wallets the funding filter missed
dev buy in the launch tx
the cluster's own buy, as a % of supply, inside the create transaction. does not show: intent, or buys by wallets outside the cluster
others' buys in the launch block
% of supply bought by wallets outside the cluster in the same slot as creation. does not show: who owns those wallets. same slot does not prove same owner; bots buy in the create slot too
time until dev wallets hit zero
time from mint until the deployer cluster holds zero of the coin. does not show: intent, or sells from wallets outside the cluster
supply sent out, not sold
% of supply the cluster sent out by transfer instead of sale. does not show: who controls the receiving wallets
graduated
coins that completed the curve, split into bought at launch (50% or more of supply bought in the create slot, or graduated within 2 s of creation) and reached after launch. does not show: demand after graduation
creator fees went to
where the coin's creator fees were pointed at creation. does not show: whether the named recipient agreed. consent is not verifiable on-chain
locks and fast flips (not counted as dev sells)
token locks, and fast sells by non-cluster wallets near launch, each with its own label. does not show: neither is ever counted as a dev sell
other sources, side by side
the same figure as other sources report it, printed next to this board's value and not merged. does not show: which source is right
calls measured
posts naming a coin, matched to the caller's wallet. a post account is matched to a wallet only by two independent sources that agree, or by the wallet's own pump.fun profile link. does not show: posts deleted before capture, calls made somewhere else, or any account-to-wallet link that rests on one source or on guesswork
caller bought before calling
minutes from the caller wallet's first buy on the coin to the post, within the 24 h before the post that is read, and market cap at the call divided by market cap at that buy, both in SOL: the buy at the caller's own fill price, the call at the first trade at or after the post (minute candles). does not show: intent, or a position bought more than 24 h before the post
caller sold 90% or more within 15 min of calling
calls where the caller wallet sold at least 90% of its position on the coin within 15 minutes after the post. does not show: sells on other venues, or what any follower did
follower-entry return
price change from a follower's entry, the open of the first one-minute candle that starts at least 30 s after the post (minute resolution), at +5m, +1h, +24h and +7d. losses print as losses; there is no floor. does not show: the caller's own result, or the fill any real follower got
creator-to-caller transfers, 24 h before a call
SOL or token transfers from the coin's creator or its funders to the caller wallet in the 24 h before the post. does not show: payment for the post
disclosure text in the call
markers such as ad or paid partnership in the post text. does not show: the platform's paid-partnership toggle, which is not checkable
follower count
not collected. does not show: follower count is not used in any figure
account link
a post account is attached to a wallet only when two independent sources agree, or the wallet's own pump.fun profile links it. a profile link is one source: the wallet names the account, and the account has not confirmed the wallet, so it is printed as one source with medium confidence. the basis and confidence are always printed. does not show: who owns the wallet or the account
wallet cluster
wallets linked by SOL funding within 2 hops, with exchange, bridge and high-throughput funders filtered and each funder checked by the operator before it is listed, or listed by the operator and verified by a funding tx. a public reason must cite a tx of the card's own wallet, not a funder. does not show: common ownership. a funding link is coordination evidence, not identity
candle
one candle per call or launch and window (+5m, +1h, +24h, +7d), as % change from the follower's entry, the open of the first one-minute candle starting at least 30 s after the post or the create. o is the entry, h and l the highest and lowest price from the entry to the window's end, and c the price at the window's end. h and l come from 1-minute candles for +5m and +1h, 15-minute candles for +24h and 1-hour candles for +7d, and the candle holding the entry counts in full, so they can include trades from just before the entry. running means the window has not ended and shows the values so far. does not show: what any real follower paid or received; trades on venues the price feed does not list
these are the price candles inside each opened card. the candles on each row are vote candles, visitors' clicks per UTC day, not price data; see "what are the two kinds of candles?" under how ranking works.

the sample size (n) is printed on every row; the date range is on the first row of each card.

corrections log

every change to a measured number or a moderator's correction, newest first. the method is versioned; a recomputed row says what changed.

  • loading.

moderation

what moderators did, as counts: reports, removals by category, appeals, vote bursts and added wallets.

loading.

removed and disputes

what was removed after review, by category, and what is disputed and under review now. a removed item is never named.

  • loading.

how reports and takedowns work: the rules.

bot check

quick check that you're a person.

one vote per post. you can change it for 24 hours.