> For the complete documentation index, see [llms.txt](https://docs.gbm.auction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gbm.auction/gbm-tokens/staking/staking-score.md).

# Staking Score

Staking and unstaking in the GBM Protocol are instant, with **no bonding or unbonding delays**.&#x20;

Your share of any governance-approved reward distribution **is based on your total staking score**, which combines two factors:

### ⏳ 1. Accumulated Score

The **Accumulated Score** rewards loyalty. It increases every second your tokens remain staked and represents your long-term staking contribution.

**Formula:**\
Accumulated Score = Time staked × Tokens staked × Stake Coefficient

**Example:**\
You stake **100 GBM tokens** for **90 days** (7,776,000 seconds) with a **Stake Coefficient of 2**.\
Accumulated Score = 7,776,000 × 100 × 2 = **1,555,200,000 points**

Unstaking stops your score from growing, but your earned points remain intact.\
\
The Stake Coefficient starts at **2** and can be updated by governance.

### ⚡ 2. Instant Score

The **Instant Score** is a **bonus awarded for presence**. It rewards anyone **still staked at the final snapshot**, even if they joined late in the period.

**Formula:**\
Instant Score = Time elapsed × Tokens staked

**Example:**\
You stake **100 GBM tokens** for the **last 10 days** of a **90-day reward period**.\
Time elapsed = 7,776,000 seconds\
Instant Score = 7,776,000 × 100 = **777,600,000**

This ensures that even short-term stakers earn a share for being active when the final snapshot is taken.

### 🧮 Total Score

Your **Total Score** determines your proportional share of the reward pool.&#x20;

It combines both **long-term loyalty (Accumulated Score)** and **presence (Instant Score)**.

**Formula:**\
Total Score = (Accumulated Score + Instant Score) ÷ (Time elapsed × (1 + Stake Coefficient))

### 🧠 Example: Comparing Stakers

Imagine a 90-day reward period with a Stake Coefficient of 2.

Alice stakes 100 tokens from day 1 and remains staked for the full 90 days.\
Bob stakes 100 tokens for the final 10 days of the period.

**Alice’s Accumulated Score:**\
7,776,000 × 100 × 2 = **1,555,200,000**

**Bob’s Accumulated Score:**\
864,000 × 100 × 2 = **172,800,000**

**Alice’s Instant Score:**\
7,776,000 × 100 = **777,600,000**

**Bob’s Instant Score:**\
7,776,000 × 100 = **777,600,000**

**Total Score (using full 90-day period = 7,776,000 seconds):**\
Alice → (1,555,200,000 + 777,600,000) ÷ (7,776,000 × 3) = **2,332,800,000** \
Bob → (172,800,000 + 777,600,000) ÷ (7,776,000 × 3) = **950,400,000**&#x20;

Alice earns roughly **2.45 times more total points** than Bob because she staked for longer, but Bob still receives a small bonus for being active at the end.

### What This System Ensures

* **Long-term stakers** build higher scores
* **Late joiners** still receive fair credit
* **Unstaking early** stops score growth, but does **not erase** what you’ve earned


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.gbm.auction/gbm-tokens/staking/staking-score.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
