# Token Lock/Burn

This has to be the most intriguing aspect of the protocol, as it is associated with the safety and authenticity of the protocol from the end of project owners. The token lock/burn feature grants users an avenue to lock and burn their tokens seamlessly.

When a lock is performed on the protocol, users can share the links associated with the given locked tokens with others to confirm or verify. This is also the case in terms of Burns.

The only difference between both of the features is that token locks are temporary, while token burns are permanent.

What does this all mean? It draws us to the phenomenon of “proof of locked liquidity” and “proof of burnt liquidity”.

**Proof of Locked Liquidity:** This is an avenue in which project owners lock their LP tokens for a scheduled period of time to avoid removal within the timeframe of lock; also having a means by which the community can easily verify the authenticity of the action. You can read more about that in [this article](https://hackernoon.com/why-locking-liquidity-is-important-for-cryptocurrency-qv4d37hd). AndromedaSwap facilitates this process from start to finish in a very fluid manner and experience.\
\
**Proof of Burnt Liquidity:** This is an avenue in which project owners burn (or throw away) their LP tokens forever, to an inaccessible wallet or via arithmetic deductions; also having a means by which the community can easily verify the authenticity of the action. When a token is burned, it leads to an increase in value of the token. But in the case of burnt liquidity, it permanently revokes the project owners or associated individuals from removing liquidity from an associated pool. You can read more about that in [this article](https://academy.swissborg.com/en/learn/token-burning). AndromedaSwap makes it easy to burn tokens as well as show verifiable proof of burnt liquidity tokens.


---

# 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://andromeda-swap.gitbook.io/andromedaswap-documentation/concepts-and-features/token-lock-burn.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.