# Lumi Tenna Leaderboard — User Guide

This guide is written for general users to understand and use the platform.\
Internal/engineering details (architecture, admin tools, raw APIs) are intentionally excluded.

***

### Introduction

**Lumi Tenna Leaderboard** is a Web3 social leaderboard that visualizes community contribution using Twitter/X activity and on-chain data.

* Gain points by posting about **@lumi\_virtuals** and **@Tenna\_virtuals**
* Complete missions for XP
* Climb the leaderboard and level up your profile

***

### Scoring at a Glance

The platform runs two independent scoring systems with different goals:

#### 1. Twitter Engagement Leaderboard (real-time ranking)

* **Purpose**: Real-time ranking from Twitter/X mentions and engagement
* **Score Type**: Floating values (e.g., 33.8, 14.7)
* **Update Frequency**: Every 8 hours
* **High-level Factors**:
  * Likes, retweets, quotes, replies
  * Tweet type (original, quote, reply, retweet)
  * Content quality (length, hashtags, mentions)
  * Recency
  * Anti-spam volume penalty

💡 **Tip**: Newer tweets score higher. Original/quote tweets weigh more than simple retweets.

#### 2. Mission System (XP)

* **Purpose**: Gamified achievements for community engagement
* **Score Type**: Fixed XP (100 / 500 / 1000, etc.)
* **Update Frequency**: Real-time upon completion
* **Mechanism**: XP is the sum of all completed missions

***

### How Scores Work (Plain English)

* **Engagement**: More likes/retweets/quotes/replies → higher base score
* **Tweet Type Weights**:\
  Original > Quote > Reply > Retweet
* **Content Quality Bonuses**:
  * Adequate length
  * Relevant hashtags (#lumi, #tenna, $lumi, $tenna)
  * Official mentions (@lumi\_virtuals, @Tenna\_virtuals)
* **Recency**: Recent tweets get boosted
* **Volume Penalty**: Posting 10+ tweets/day reduces incremental score

⚠️ **Filtering Rules**

* **Excluded**: Tweets mentioning @LumiterraGame
* **Always Counted**: Tweets mentioning @lumi\_virtuals or @Tenna\_virtuals

***

### Missions & Levels

#### Example Missions

* **First Contact (Common)**: Your first Lumi/Tenna tweet → 100 XP
* **Engagement Master (Rare)**: 100+ total likes → 500 XP
* **Viral Sensation (Epic)**: A single tweet hits 50+ likes → 1000 XP
* **Consistency Champion (Rare)**: Post 7 consecutive days → 750 XP
* **Community Influencer (Legendary)**: Reach Top 10 → 2000 XP
* **Social Butterfly (Rare)**: 25 Lumi/Tenna tweets → 600 XP

**Rarity Tiers**: Common < Rare < Epic < Legendary

#### Leveling Up

* Your **level = cumulative XP** from missions
* Each higher level requires more total XP

***

### What You’ll See

#### Leaderboard

* Updated every **8 hours**
* Handle, followers, verification status
* Total points, tweet count, current rank
* 24-hour trend indicators

#### Mission Dashboard

* Progress bars by mission
* Achievement gallery with unlock timestamps
* Current level and XP to next level
* Totals: XP, achievements, rarity breakdown

#### Wallet Integration

* Connect wallet with **Reown AppKit** (mobile/browser)
* View balances: **LUMI / TENNA**
* Staking ratio and holder stats
* Supported: **Base Chain (Chain ID: 8453)**

#### Update Cadence

* Twitter engagement: **every 8 hours**
* Missions: **real-time**
* Balances/staking/prices: **every 10 minutes**

***

### Getting Started

1. **Connect Wallet**: Click *Connect Wallet* (Reown AppKit)
2. **Link Twitter**: Click *Connect X* and approve access
3. **Start Posting**: Mention @lumi\_virtuals or @Tenna\_virtuals
4. **Track Progress**: Use the Leaderboard & Mission Dashboard
5. **Earn XP**: Complete missions, level up, climb ranks

💡 **Pro Tip**: Original or quote tweets perform best. Add relevant hashtags for bonuses.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://lpc-ai-lumi.gitbook.io/lpc_ai_lumi/lumi-tenna-leaderboard-user-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.