> For the complete documentation index, see [llms.txt](https://docs.proxima.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proxima.tools/live-settings/lock-supply-via-streamflow.md).

# Lock Supply (Via Streamflow)

### **How Locking Works**

* Locks tokens from the **Deployer wallet** for a set duration
* Requires at least **0.1 SOL** to cover Streamflow fees
* Tokens unlock automatically and return to the Deployer wallet when the timer ends
* Fully on-chain, irreversible, and publicly visible
* Lock link is provided for transparency

<div align="left"><figure><img src="/files/kDe3iF4DpSgi219MwZYl" alt="" width="563"><figcaption></figcaption></figure></div>

### **Steps**

1. Choose the **percentage of supply** you want to lock.
2. Set the **duration** (days, hours, minutes).
3. Confirm the transaction. That’s it.

Tokens are streamed into a Streamflow lock contract and **cannot be accessed** until the lock period expires.

***

### **Notes**

{% hint style="info" %}
Locking is primarily a **community-facing trust signal**, not a security guarantee. It’s best used to boost credibility post-launch or reassure holders pre-launch.
{% endhint %}


---

# 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.proxima.tools/live-settings/lock-supply-via-streamflow.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.