> For the complete documentation index, see [llms.txt](https://docs.aethra.work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aethra.work/appendices/glossary.md).

# Glossary

**AETHRA Token ($AETHRA)**\
The utility token of the AETHRA ecosystem, used for staking, governance, and access to platform services.

**MVP (Minimum Viable Product)**\
The first public release of the AETHRA platform, launching on October 13, 2025.

**Closed Beta**\
A private pilot program with 20 testers (June–August 2025) that validated core features.

**LBP (Liquidity Bootstrapping Pool)**\
The mechanism used for the $AETHRA token launch on January 6, 2025, enabling fair price discovery and broad distribution.

**Credential Anchoring**\
Recording cryptographic proofs of worker credentials on-chain without exposing personal data.

**Governance**\
Participation of token holders in protocol decision-making, including proposals and updates.

**Staking**\
Locking $AETHRA in a smart contract to earn protocol-defined rewards.

<figure><img src="/files/k15AwXxUmjEHpgndRRVB" alt=""><figcaption></figcaption></figure>


---

# 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.aethra.work/appendices/glossary.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.