# Smart contracts

LoopBurn is powered by a set of carefully designed smart contracts working together to create a fully automated, unstoppable yield and burn machine. This section outlines each component and how they interact.

| **Contract**                 | **Address**                                                                                                            |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| $LBP Token                   | [0x001bFF4b6da770f445A740227224D3c8b48e6fb2](https://sonicscan.org/address/0x001bFF4b6da770f445A740227224D3c8b48e6fb2) |
| Yield Reactor                | [0xDB6A2Fc2Bc6E77D9FDfdFc588BeFDBb9c055bede](https://sonicscan.org/address/0xDB6A2Fc2Bc6E77D9FDfdFc588BeFDBb9c055bede) |
| Liquidity Lock / POL Manager | [0xB20241DFD126E8Db352bF2e19f5f3402Dca265e9](https://sonicscan.org/address/0xB20241DFD126E8Db352bF2e19f5f3402Dca265e9) |

🪙 $LBP Token

* Standard ERC-20 (18 decimals)
* No tax, no mint, no inflation
* Immutable after launch

### 🧱 Liquidity Lock / POL Manager

* Locks protocol owned liquidity forever 🔒
* Controlled access by Yield Reactor

### ⚙️ Yield Reactor

**Function: `burnloop()`**

* Withdraws 1% of protocol-owned liquidity
* Burns $LBP
* Sends $wS to the Yield Reactor
* 8 - Hours cooldown between each cycle execution

**Function: `hyperloop()`**

* Claims trading fees
* Burns $LBP
* Uses $S to buy/sell $LBP 2–10 times per transaction
* Sends trading value back to the pool
* 15-minute cooldown between each cycle execution


---

# 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://loopburn-sonic.gitbook.io/loopburn/basics/smartcontracts.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.