# Functions

### 1) Protocol-managed liquidity as a strategic lever

A significant portion of the 0Fx maximum supply is allocated to support the **primary liquidity infrastructure** (0Fx / wstETH pool).

This protocol-managed liquidity provides the ecosystem with:

* strong early-stage market accessibility,
* a capital-efficient bootstrapping mechanism,
* and a long-term strategic lever governed by the community.

***

### 2) Liquidity allocation flexibility (governance-controlled)

Because protocol-managed liquidity represents a large supply share, the ecosystem has meaningful flexibility over time.\
Subject to governance decisions, the protocol can:

* reallocate part of the liquidity supply,
* reduce it progressively as external liquidity grows,
* or apply supply adjustments (including partial burns), depending on ecosystem strategy.

All such actions are intended to be governed transparently through community-approved rules.

***

### 3) Progressive transition toward community custody

As the ecosystem matures and liquidity becomes less dependent on protocol bootstrapping, liquidity ownership and control is expected to transition progressively toward:

* community-controlled treasury frameworks,
* or a dedicated strategic liquidity reserve.

***

### 4) Liquidity base asset evolution (long-term)

The current liquidity base asset is **wstETH**, aligning the token structurally with ETH exposure.

Over the long term, governance may choose to evolve the liquidity foundation (base asset / reserve structure) depending on:

* ecosystem growth,
* strategic reserve formation,
* and market infrastructure requirements.


---

# 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://0fx-protocol-1.gitbook.io/0fx-protocol-docs/0fx-token/functions.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.
