> For the complete documentation index, see [llms.txt](https://solocker.gitbook.io/solocker-spl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solocker.gitbook.io/solocker-spl/services/token-locks/team-token-locks.md).

# Team Token Locks

### **What are Team Token Locks?**&#x20;

Locking team tokens allow projects to lock their team-allocated tokens in a time-locked decentralized smart contract vault. The project team or founders allocated to the team tokens cannot withdraw or change these tokens until the end of the locked period(s). This way, the community and investors are at less risk of scams. \
\
Using a third-party locking service is a crucial innovation compared to most token offerings, where projects may avoid fulfilling their promises and maliciously sell off all their tokens, leaving holders, stakers and investors with a close to $0 token price.&#x20;

Crypto projects may use SOL Locker Team Token Locks to show proof of vesting schedule and interest in the project, build credibility and reduce the risk of scams to benefit the community and investors.

### **How should you allocate your token supply?**

When it comes to allocating your token supply, it is important to consider the various stakeholders and how to distribute the tokens among them. \
\
One key factor to consider is the circulating supply or the number of tokens that will be actively traded on the market. This can impact the liquidity of your project or the ease with which its tokens can be bought and sold. Make sure to consider the percentage breakdown of your tokens in circulation, like team tokens, lp (liquidity pool) tokens, and more.&#x20;


---

# 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:

```
GET https://solocker.gitbook.io/solocker-spl/services/token-locks/team-token-locks.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.
