> For the complete documentation index, see [llms.txt](https://incomelayer.gitbook.io/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://incomelayer.gitbook.io/introduction/whitepaper/2.-income-layer.md).

# 2. INCOME Layer

Income Layer™ is an innovative blockchain protocol designed to bridge Decentralized Finance (DeFi) with traditional finance, aiming to deliver a sustainable **Universal Basic Income (UBI)**. Its core is driven by the proprietary **Economic Harmony (EH)™** algorithm, which manages key economic variables in real time, ensuring long-term stability and scalability. This protocol creates a robust, secure infrastructure for participants, allowing them to benefit from a balanced and self-sustaining ecosystem.

At the center of the platform are **INCOME Nodes**, operated by **Node Champions** who play a critical role in UBI distribution, liquidity management, and governance. These nodes work in tandem with the **EH™** algorithm to maintain an optimal economic balance, adjusting token supply, liquidity, and participation in governance in real time. The 10% transaction tax supports this balance, ensuring consistent liquidity growth, reducing token supply through burning, and funding marketing and governance efforts.

#### Key Ingredients of the Income Layer Ecosystem:

* **Economic Harmony (EH)™ Algorithm**
  * Real-time monitoring and adjustment of supply, liquidity, and market conditions to maintain system stability.
  * Dynamic balancing of deflationary mechanisms and liquidity to ensure long-term ecosystem health.
  * Ensures optimal economic conditions, safeguarding the ecosystem from inflation and instability.
* **INCOME Nodes**
  * Central to UBI distribution and governance, managed by **Node Champions**.
  * Nodes contribute to liquidity, participate in governance decisions, and receive rewards for their active role.
  * Balances participation with rewards through the **EH™** algorithm, ensuring a steady flow of value.
* **10% Transaction Tax**
  * **4% to Liquidity**: Provides liquidity growth and market stability.
  * **2% Burn Mechanism**: Reduces total supply, creating a deflationary effect and increasing token scarcity.
  * **2% UBI Distribution**: Ensures sustainable income distribution to node operators.
  * **1% Marketing**: Funds efforts to grow the platform’s user base and ecosystem visibility.
  * **1% Treasury/Governance**: Supports system upgrades and ensures smooth operation of the ecosystem.
* **Deflationary Model**
  * Token burning reduces supply over time, enhancing scarcity and preserving long-term value.
  * Pegged token supply to global debt creates a sustainable deflationary economic model.
* **Liquidity Growth**
  * Continuous allocation of transaction taxes to liquidity reserves.
  * Ensures smooth market operations and scalability, supporting long-term platform growth.

These components work in harmony to deliver a **transformative financial infrastructure** where participants receive consistent income, and the system remains secure and sustainable. By leveraging **Economic Harmony™** and a multi-layered economic model, Income Layer fosters long-term wealth redistribution, minimizes inflationary risks, and provides a platform for future financial growth and innovation.


---

# 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, and the optional `goal` query parameter:

```
GET https://incomelayer.gitbook.io/introduction/whitepaper/2.-income-layer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.