# What we do

<figure><img src="/files/5Ss5i4W0SBMGUc1qLWEN" alt=""><figcaption></figcaption></figure>

Lighthouse Exchange is looking to become the next central marketplace for liquidity on the BNB chain. Bringing together various projects to create a positive feedback loop for all parties involved.

Lighthouse Protocol: Simplifying Token Swaps with Liquidity Incentives

The Lighthouse protocol streamlines token swapping by incentivizing liquidity provision. Here's a straightforward breakdown of how it works:

1. **Attracting Liquidity**: The protocol draws in liquidity, essential for smooth token swaps (refer to the diagram below for a simplified view).
2. **Rewarding Liquidity Providers**: Those who supply liquidity, known as Liquidity Providers (LPs), are rewarded with LIGHT tokens. These tokens are generated by the Minter.
3. **Distribution Based on Votes**: The distribution of LIGHT tokens to various liquidity pools is determined by votes. These votes are cast weekly by Voters.
4. **Staking for Rewards**: To be eligible for LIGHT token rewards, Liquidity Providers must stake their deposited liquidity in a Gauge.
5. **Voting Power for LIGHT Holders**: If you hold LIGHT tokens, you have the option to lock them. Doing so grants you the power to vote on how the LIGHT token emissions are distributed across pools.

This structure not only makes token swapping more efficient but also actively rewards participation and investment in the ecosystem.


---

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