Skip to main content
Ekiden points are XP ledger balances. They should be earned through measurable trading, referral, competition, or campaign activity and recorded with auditable ledger reasons.

​
Implemented XP Model

The backend rewards formula is rewards_xp_mvp_v1. Each allocation run distributes a fixed weekly XP pool pro rata by power score: 
base_power_score = volume * (1 + roi) * drawdown_factor
final_power_score = base_power_score + referral_bonus_power_score
weekly_xp = weekly_pool_xp * final_power_score / sum(final_power_score)
The default referral bonus rates are:
Referral LevelBonus
Level 115%
Level 210%
Level 35%
XP is persisted through allocation runs, ledger entries, and balances. Public/user-facing APIs expose trading XP, referral XP, total XP, referral summary, rewards summary, and leaderboard XP fields.

​
Earning Sources

Core XP sources:
  • Eligible trading volume and performance.
  • Referral bonuses from active referred traders.
  • Competition rewards and projected XP.
  • Operator-approved manual grants or adjustments.
KOL campaign sources should use the same ledger model:
  • Referred active traders that pass eligibility checks.
  • Referred trading volume or fee contribution.
  • Competition participation driven by a campaign.
  • Campaign-specific quests with verifiable completion.
  • Verified content deliverables that are reviewed and capped.
  • Manual operator grants or clawbacks for edge cases.
Avoid uncapped raw impressions, follower counts, or screenshots as automatic point sources. They are easy to manipulate and should only influence manually reviewed campaign adjustments.

​
KOL Campaign Rules

KOL campaigns should be configured before launch and should not depend on ad hoc UI-only balances. Every campaign grant or correction should map to a ledger reason, an operator decision, or a deterministic backend allocation. Minimum campaign configuration:
  • Campaign identifier and active window.
  • Eligible referral code or attribution rule.
  • Minimum referred-user activity threshold.
  • Per-user, per-KOL, and campaign-wide caps.
  • Reward reasons used in the ledger.
  • Review and clawback policy.
Recommended default thresholds:
RuleDefault
Active referred traderReferred account completes at least one eligible trade and meets the campaign minimum volume.
Eligible referred volumeCount filled notional from non-abusive perpetual trades during the campaign window.
Eligible referred feesCount net trading fees from eligible fills, excluding rebates, reversals, and clawed-back activity.
AttributionFirst valid referral binding wins unless operations approve a correction.
Content deliverablesManual review required before points are granted.
Campaign capsApply per referred user, per KOL, and globally before granting manual campaign points.
Recommended KOL ledger reasons:
ReasonUse
weekly_allocationCore weekly trading and referral XP allocation generated by the rewards service.
kol_referral_active_traderReferred user reaches the active-trader threshold.
kol_referral_volumeReferred eligible volume or fee contribution.
kol_competition_participationReferred user joins or completes a campaign competition.
kol_content_deliverableManually reviewed content milestone.
operator_adjustmentManual grant or correction.
operator_clawbackNegative ledger entry for disqualified or reversed rewards.
Campaign metadata should include enough detail to audit the grant later: 
{
  "campaign_id": "kol_s1",
  "source": "operator",
  "referral_code": "PARTNER42",
  "referred_user_id": "user_abc",
  "basis": "active_trader",
  "window_start": "2026-06-01T00:00:00Z",
  "window_end": "2026-06-30T23:59:59Z",
  "operator": "ops@example.com"
}
Use negative delta_xp entries for clawbacks instead of rewriting history.

​
Abuse Policy

The following activity should be excluded or clawed back:
  • Self-referral or circular referral chains.
  • Wash trading, spoofing, or economically meaningless volume.
  • Multi-account farming.
  • Referral attribution manipulation.
  • Campaign activity outside the eligibility window.
  • Any activity tied to sanctioned, banned, or otherwise ineligible accounts.

​
User Visibility

Users should be able to inspect:
  • Current referral code and referral tree summary.
  • Trading XP, referral XP, and total XP.
  • Recent ledger entries or allocation history.
  • Leaderboard placement with XP fields.
  • Campaign-specific caps and eligibility status when participating in a KOL campaign.