> For the complete documentation index, see [llms.txt](https://team57.gitbook.io/lighthouse-exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://team57.gitbook.io/lighthouse-exchange/overview/tokenomics.md).

# Tokenomics

Initial supply of $LIGHT will be set at 400 million.

Weekly emissions started at 15M (3.75% of the initial supply) and decay at 1% per week (epoch). Ensuring for a more sustainable project by having the emissions decay.

***

Lighthouse Exchange uses two tokens to manage its utility and governance:

$LIGHT — BEP-20 utility token of the protocol&#x20;

$veLIGHT — a governance token that comes in the form of an NFT. Lock $LIGHT to receive this token.&#x20;

$LIGHT tokens are given to those who provide liquidity, a process known as emissions.

For governance purposes, $veLIGHT is used. Holders of $LIGHT can choose to lock (vote-escrow) their tokens. In return, they receive $veLIGHT, which is also referred to as Lock or veNFT. It's possible to add more tokens to your $veLIGHT NFT whenever you want.

The length of time you lock your tokens for can vary up to 4 years. This period is known as the vote-escrowed period, which is why it has the 've' prefix. The way it works is simple: if you lock 100 $LIGHT for 4 years, you get 100 $veLIGHT. But if you lock them for just 1 year, you only get 25 $veLIGHT. Essentially, the longer you lock your tokens, the more $veLIGHT you get, which means greater voting power.

With the updated version, LIGHT v2, you can opt for a permanent lock on your veNFT. This means the protocol will always consider these Locks (veNFTs) as being locked for the full 4 years, so their voting power remains strong and doesn't decrease over time.


---

# 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://team57.gitbook.io/lighthouse-exchange/overview/tokenomics.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.
