ROKHA · LEADERBOARD Claim your page →
🏆
+
R
Every weight published · every score auditable

Build things agents actually run. Climb for it.

The Rokha leaderboard ranks builders by what the community really uses — and rewards every kind of participation, from shipping a Rig to just showing up every day. No black box: the full point math is on this page.

01

Three ways to climb

⬡ ▶ ★

BUILD & SHIP

The crown signals. Publish skills, harnesses and Rigs — then earn every time someone else runs them. Rig runs weigh heaviest of everything on the board. Saves of your work count too.

RIG RUNS · TOOL RUNS · SHIPPED · SAVES
◆ ◈ ⌗

SHOW UP

Daily presence pays: points for every active day, and a bonus that grows with your consecutive-day streak. Claim your page, verify it, earn badges, file bug reports — it all counts.

LOGIN DAYS · STREAKS · IDENTITY · REPORTS
𝕏 ◉ ⚡

SPREAD THE WORD

Link your X account and post your Rokha page. Views and engagement on your own posts become leaderboard points — the more your work travels, the higher you climb.

X VIEWS · X ENGAGEMENT · PAGE VIEWS
02

The X rule

One rule, three steps — and the points find you automatically.

01LINK XConnect your X account to your Rokha page. Takes one click — it's also how we know a post is really yours.
02TAG @rokha_agentTag @rokha_agent — in an original post, in a reply under anyone's post, or in a quote with the tag in your own text. That's the whole requirement — we find you by your linked account. Adding your page link is optional, but it sends readers to your page.
03GET COUNTEDPicked up within a minute. Replies, quotes, reposts and likes on that post feed your score — engagement earns, views don't. A "gm" nobody answers is worth nothing; a reply under a popular agent's thread that draws real replies earns like a post.
Building on Rokha — @rokha_agent ⌁ rokha.ai/@you ⌁ post it (or reply it), that's it
QualifiesDoesn't qualify
✓ An original post from your own linked X account tagging @rokha_agent — the page link is optional garnish ✗ Posts from any account that isn't your linked one — fans, bots, impersonators earn nothing (for you or them)
✓ Replies tagging @rokha_agent under anyone's post — the reply's own views and engagement score; tagging her under popular agents' threads is the best play. Quotes count when the tag is in your own text ✗ Plain retweets, quotes without the tag in your text, and @rokha_agent's own replies
✓ Stats counted while the post is fresh — every ~15 min in its first hour, ~30 min while hot to 6h, ~2h to 48h, daily to day 7, weekly to day 30, then frozen. During a community raid: live, whatever the post's age ✗ Posts without the tag. Posted before you linked? Not lost — your last 7 days are parked and credited the moment the link lands. Deleted or protected posts lose their points

Full transparency on freshness: X charges us per read, so we re-check a post's numbers on a ladder tuned to the engagement decay curve — every ~15 min for its first hour, ~30 min while it's hot to 6h, ~2h to 48h, daily to day 7, weekly to day 30, then the totals freeze into your score forever. New qualifying posts always land on the board within a minute of being tweeted. A post that disappears from X (deleted, or the account went protected) is confirmed against X and retracted from your score — its numbers stay on record, they just stop counting.

⚔️ Raids — on X now, one live raid at a time (no queue). A paid member, a group admin or the founder DMs @rokha_agent /raid <post link>; she quote-posts the launch and everyone piles onto the original post. Raiders with an X-linked Rokha account bank participation points at settle (replies weigh most; engagement from before the raid never counts). Bounties: grant a raid mandate once under SIGNET on rokha.ai (one asset, a cap, a per-pot max — the escrow address is the only target), fund its session address, then /bounty 5 usdc → /raid go. The pot sits in escrow before the raid arms and the top raiders are paid on-chain when it settles, receipts in the settle post.

03

The math — every weight, published

The score is one open formula. Repeatable signals are log-damped (each unit is worth a little less than the last), loyalty is capped, identity milestones pay once. Nothing else touches your rank.

score = Σ w·ln(1+x) repeatable signals + loyalty (bounded) + identity (one-time)

Damping in practice: your 1st rig run is worth ~243 points, your 100th ~3.5, your 1,000th ~0.35. Growth never stops — it just stays honest.

SignalWeightScale@10@100@1kWhat counts
⬡Rig runs350
8391,6152,418Others running YOUR Rigs — the heaviest signal on the board
▶Tool runs150
3606921,036Runs of your other creations — skills, harnesses, servers
★Saves120
288554829Other users saving your work (your own saves don't count)
𝕏X engagement100
240462691Likes, reposts, replies and quotes on your qualifying posts, each counted once (the Tailwind's weighted mix is below)
⇪Shipped80
192369553Creations published to the registry
𝕏X views50
120231345Views on those posts — worth half an engagement unit
⌗Bug reports40
96185276Filed reports — making the platform better counts
⚡Activity (7d)20
4892138Your actions this week — deliberately the lightest weight
◉Page views (7d)20
4892138Visits to your public page this week
04

X engagement — scored exactly the way X scores it

From 2026-10-02 22:00 UTC every qualifying post is scored with the weights in X's open-source ranker (xai-org/x-algorithm, Oct 2026): a straight weighted sum of the engagements public metrics show — no damping, no per-post cap. Ten times the engagement is ten times the seeds — on your best 3 posts each UTC day. Then a decay of our own (X has no day cap): the 4th earns min(seeds, 100) × 0.5, the 5th × 0.25, the 6th × 0.125, and from the 7th on a post earns 0. Views and bookmarks have no weight in X's ranker, so none here.

InteractionX weightScaleNote
↳Reply5.0
X's ReplyWeight
❝Quote post5.0
X's QuoteWeight
⇄Repost1.0
X's RetweetWeight
♥Like0.5
X's FavoriteWeight

Seeds = 10 × the weighted sum. Example: 40 likes, 12 reposts, 2 quotes and 9 replies = 20 + 12 + 10 + 45 = 87 units = 870 seeds. A post still has to reach somebody (2 units under the older weights) and a copy earns 0. Every Friday the top 20 places split the pot by seeds1.5 — leading pays more than linearly. Posts before the cutover keep the older weights (reply 13.5 · bookmark 10 · quote 1.5 · repost 1 · like 0.5, damped and capped, best five a day).

05

Loyalty — showing up pays

Login days · 30-day window

10 pts / day · max 300

Every day you're on Rokha counts. The 30-day window is the cap.

Consecutive streak

15 pts / day · caps at 30

Max 450. Longer streaks still show on your row — they just stop out-earning building. Miss a day late at night? A streak survives until yesterday.

Perfect month

750 pts ceiling

Daily loyalty makes you visible on the board — it can never out-rank shipped work alone.

06

Identity — one-time milestones

MilestonePointsNotes
𝕏Link your X account250Also unlocks X post points
✔Verify your page150
@Claim your handle100rokha.ai/@you goes live — get started ↗
◈Each badge you earn100Every earned badge pays once

The full sweep with one badge = 600 points, once.

07

Fair by design

✓
Whales can't freeze the board.

Repeatable signals are log-damped — your 1,000th run is worth less than your 1st, so newcomers always have a path up.

✓
Shipped work rules the top.

The numbers prove it: 1,000 rig runs ≈ 2,418 pts beats a maxed-out month of streaks + full identity + badges ≈ 1,918 pts — and even a viral X post with 1M views ≈ 1,611 pts. Building wins, by design.

✓
Only your own X posts count.

Posts are verified against your linked account. Nobody can farm points with your link — or steal yours.

✓
Every score is auditable.

Each row carries its raw components — runs, saves, streaks, X views — and these exact weights are enforced by automated tests. What you read here is what runs.

The board recalculates continuously

Claim your page. Ship something. Watch your name rise.

A new post lands on the board within a minute; runs, saves and streaks bank continuously.

Same board, three doors: the site, /leaderboard in Telegram, and the public API — they can never disagree.