Leaderboard, XP, Tiers, Badges & Squads

The leaderboard is where everything your community does shows up as rank. Every verified quest completion awards XP; XP rolls up per campaign to drive rank and a tier ladder; badges recognise milestones; and squads let members team up for collective bonuses. This page explains how each piece works and what you, as an admin, control.

Leaderboard

The leaderboard ranks participants within a campaign by their campaign XP, highest first. Each row shows the member, their XP, rank and tier. A signed-in end user always sees their own "sticky" row even when they're far down the list.

Time windows

The public leaderboard accepts a window parameter so members can see ranking over different time spans:

The legacy aliases week (→ 7d) and month (→ 30d) are still accepted for backward compatibility.

Screenshot

Campaign site → Leaderboard with the 7d / 30d / all-time / campaign window tabs

slot: leaderboard-xp.leaderboard-view

How rank is computed and cached

Rank is the count of members with more campaign XP, ordered consistently so ties never shuffle between page loads (XP descending, then a stable tiebreak). To keep the "your rank" lookup fast on large campaigns, each member's rank is cached and refreshed continuously, with a nightly correction pass. The leaderboard is read-only for admins — it reflects whatever XP your quests have awarded.

XP

There are two XP figures, and the distinction matters:

• Total XP — a member's lifetime XP across everything in your project.
• Campaign XP — XP earned within a single campaign. This is the number the leaderboard ranks on, and the number the tier ladder reads.

XP is only ever awarded through a verified quest completion — never edited by hand on the leaderboard. (Admins can still make manual XP adjustments from a user's detail page; those flow through the same award path.)

Tiers

Each campaign has a four-rung tier ladder driven by campaign XP. Tiers are per campaign — a member can be Gold in one campaign and unranked in another. Hitting a threshold exactly grants that tier.

The defaults written into every new campaign:

Thresholds are stored per campaign, so you can raise or lower them to fit a shorter or longer campaign. A member's tier recomputes automatically whenever their campaign XP changes; lowering thresholds later can promote members on the next recompute, raising them can demote.

Screenshot

Admin → Campaigns → (campaign) → Settings → tier thresholds

slot: leaderboard-xp.tier-config

Badges

Badges are persistent recognitions on a member's profile. Each badge has a tier — STANDARD, RARE, EPIC or LEGENDARY — used for display. Badges also feed the reputation score (see below).

Built-in badges

Seven built-in badges ship with every project and are granted automatically by a daily evaluation worker. You don't configure these — they're awarded the moment a member qualifies:

Custom badges

You can define your own badge types from Badge management — set a slug, display name, description, icon and tier. Custom badges can then be granted to members manually from a user's detail page.

Screenshot

Admin → Badges → built-in + custom badge types with the custom-badge quota

slot: leaderboard-xp.badge-management

Revoking a badge is a soft action — the badge is tombstoned, history is retained, and reputation stops counting it.

Squads

Squads let members band together within a campaign and earn collective rewards. A squad has a leader, a roster, a join policy (OPEN, INVITE_ONLY or CLOSED), and progresses through a short lifecycle.

Lifecycle: FORMING → ACTIVE → ARCHIVED

Size limits

Screenshot

Admin → Squads → directory with status, member count, total XP and sybil density

slot: leaderboard-xp.squad-list

The anti-sybil density gate

When a squad tries to go ACTIVE, Onsend checks its sybil density — the fraction of members flagged SUSPICIOUS or BLOCKED (or otherwise blocked / banned) out of the whole roster. If density is at or below 0.3 (30%), the squad promotes. Above that, promotion is blocked — this stops a farmer from spinning up a squad of sock-puppet accounts to harvest collective bonuses.

Squad XP rollup

A daily worker sums each ACTIVE squad's member XP per window (7-day, 30-day, all-time), ranks squads against each other, and sets the squad's total XP and tier. Blocked members' XP is excluded from the rollup so a compromised member can't inflate a squad's standing.

The squad collective quest

squad_collective is a special quest connector that rewards a whole squad for acting together. You configure:

• a referenced quest squad members must complete,
• a required member count, and
• a time window (default 24 hours, configurable from 1 to 168 hours).

When enough squad members complete the referenced quest inside the window, every qualifying member is awarded a per-member bonus. The member who triggers verification is rewarded immediately; a worker (every 15 minutes) fans the same bonus out to the other qualifying members. Blocked members never count toward the required count and never receive the bonus. The bonus is awarded as base XP, so members' personal multipliers compound on it the same as any other quest.

Reputation tiers

Separately from per-campaign tiers, Onsend computes a project-wide reputation score per member from their XP, quest activity, referrals, wallet age, on-chain history, cross-tenant signals and badges, minus any sybil penalty. The score maps to a five-rung ladder:

Reputation is what powers the Squad founder and other built-in badges, drives the optional soulbound reputation token, and can gate reputation-restricted quests. The default thresholds above are tunable per project. Reputation is a longer-horizon trust signal — distinct from the per-campaign tier a member earns by grinding a single campaign's quests.