# $STXL Tokenomics Structure

## SESTRA TOKENOMICS STRUCTURE

### Locked Allocation Overview (15%)

> To ensure long-term protocol sustainability and disciplined supply management, **15% of total $STXL supply** is allocated under structured, time-based locking mechanisms.

#### Allocation Objectives

| Objective        | Description                                                     |
| ---------------- | --------------------------------------------------------------- |
| Core Development | core protocol development                                       |
| Infrastructure   | infrastructure scaling                                          |
| Stability        | operational stability                                           |
| Participation    | flexible participation in protocol security and access capacity |

> All allocations are governed by gradual release schedules, avoiding short-term supply pressure.

***

### Locked Allocation Breakdown

| Allocation                           | Percentage | Lock Mechanism |
| ------------------------------------ | ---------- | -------------- |
| Treasury & Protocol Operations       | 5%         | Sablier        |
| Core Protocol Development            | 5%         | Streamflow     |
| Infrastructure & Ecosystem Expansion | 5%         | Streamflow     |

***

### Treasury & Protocol Operations ( 5% )

**Lock Mechanism:** Sablier

#### Purpose

> This allocation is reserved for long-term protocol-level needs, including:

* treasury operations and runway management
* protocol sustainability mechanisms (including burn or supply balancing actions, when applicable)
* operational support for the session layer
* funding flexible staking infrastructure and maintenance

#### Flexible Staking Relation

> A portion of this allocation may be used to:

* bootstrap flexible staking programs
* support protocol-owned liquidity or staking-related tooling
* maintain system stability without enforcing rigid lock-ups

#### Rationale

> Streaming via Sablier ensures treasury actions remain:

* predictable
* gradual
* aligned with long-term protocol health

***

### Core Protocol Development ( 5% )

**Lock Mechanism:** Streamflow

#### Focus Areas

> This allocation supports continued development of Sestra’s core systems:

* session orchestration engine
* policy and access control logic
* verifier and runtime improvements
* security hardening and protocol evolution

#### Flexible Staking Relation

> Core development includes:

* designing staking logic tied to session capacity and access limits
* ensuring staking remains utility-driven, not yield-driven
* maintaining clean separation between protocol usage and speculative incentives

#### Rationale

> Time-based vesting aligns contributors with long-term delivery and prevents short-term extraction.

***

### Infrastructure & Ecosystem Expansion ( 5% )

**Lock Mechanism:** Streamflow

#### Focus Areas

> This allocation is dedicated to scaling protocol usage through:

* session infrastructure expansion
* event and webhook systems
* enterprise and ecosystem integrations
* developer tooling and SDK improvements

#### Flexible Staking Relation

> Infrastructure expansion enables flexible staking to:

* act as an optional participation layer for developers and operators
* unlock higher throughput, priority, or advanced policy features
* scale alongside real protocol demand rather than emissions

#### Rationale

> Vesting ensures infrastructure and staking-related extensions are deployed steadily as adoption grows.


---

# 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://sestra.gitbook.io/sestra-whitepaper/tokenomics/usdstxl-tokenomics-structure.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.