# Tokenomics

Token Name: Lovely Inu Finance

Symbol: LOVELY

Total Supply: 75,000,000,000,000

Decimal: 8

Supported Chains: BSC, ETH

Token Name: Lovely Swap Token

Symbol: LST

Total Supply: 300,000,000

Decimal: 8

Supported Chains: BSC

Strategically consolidating our token ecosystem, we are merging the 75 trillion Lovely tokens and 300 million Lovely Swap tokens into a single, powerful native coin for the Lovely Finance ecosystem. This unification, planned for Q2 2024 per our milestones, aims to streamline operations and provide a cohesive, robust foundation for sustained growth and innovation within Lovely Finance.

{% hint style="info" %}
"Merging 75 trillion Lovely Inu (LOVELY) and 300 million Lovely Swap Token (LST) tokens into a unified native coin for LOVELY. Market capitalization will be calculated at 7.5M USD for LOVELY and 300M USD for LST. This strategic move aligns with our commitment to transparency and efficiency in evolving the LOVELY ecosystem."
{% endhint %}

### <mark style="color:purple;">2024 Q2</mark>

Token Name: Lovely Finance

Symbol: LOVELY

Total Supply: 10,000,000,000

Decimal: 18

Network: Ethereum

***

### This is the Tokenomics for the next upcoming years:

### 2024&#x20;

* 40% of revenue will go to LOVELY Holders
* 40% of revenue will go to Marketing
* 20% of revenue will go to Charity

### 2025

* 30% of revenue will go to LOVELY Holders
* 50% of revenue will go to Marketing
* 20% of revenue will go to Charity

### From 2026 Upward

* 15% of revenue will go to Burn
* 15% of revenue will go to LOVELY Holders
* 20% of revenue will go to Marketing
* 30% of revenue will go to Team
* 20% of revenue will go to Charity


---

# 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://wp.lovely.finance/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.