# Everbuild vs Everburn

## <mark style="color:orange;">HOW DOES EVERBUILD RELATE TO EVERBURN?</mark>

<mark style="color:red;">**Everburn**</mark>**&#x20;&&#x20;**<mark style="color:purple;">**Everbuild**</mark> are closely tied together. Everything we do at the Everburn DAO revolves around the Everburn Token. We consider Everbuild to be a Layer 2 to Everburn. Everbuild is the first of multiple Layer 2’s we plan to build around Everburn. These Layer 2’s will be created as HODL – PRINT – BURN - EARN! Whitepaper v2.1-9.22 – everburn.io[^1] self-sustainable businesses owned and operated by the holders to directly benefit stakeholders and participants of Everburn ecosystem.

**Everburn** has provable tokenomics that solely requires a surge of consistent volume to feed the burn mechanics of the project. That is what **Everbuild** is, the push of constant volume that feeds the Everburn engine.&#x20;

One hundred percent (100%) of every transaction fee on **Everbuild** gets pooled and paid out monthly to the ECT holders in EVB. Ultimately, the goal is to inject sustainable volume using a real-world business into the **Everburn** ecosystem, for long-term growth. That is what **Everbuild** sets to achieve, besides filling a much-needed niche in the crypto & blockchain marketplace space, to also be a second layer fuel that powers the **Everburn** growth engine.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><mark style="color:orange;">Low tax to buy - High tax to sell.</mark></td><td><mark style="color:green;">Token burned on every Transaction.</mark></td><td>Limiting circulating supply forever</td><td><a href="/files/zsA4j72NFvdzK6cvnSTt">/files/zsA4j72NFvdzK6cvnSTt</a></td></tr><tr><td><mark style="color:purple;">Crypro Niche</mark></td><td>Job board</td><td><mark style="color:red;">Task marketplace</mark></td><td><a href="/files/luJi4yaP7oE0yzpUV4z3">/files/luJi4yaP7oE0yzpUV4z3</a></td></tr><tr><td></td><td></td><td><mark style="color:orange;">Everburn Smart Contract</mark></td><td><a href="/files/8StsIvrkI2Hl9Fenn7am">/files/8StsIvrkI2Hl9Fenn7am</a></td></tr></tbody></table>

[^1]: <https://everburn.io>


---

# 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://docs.everburn.io/everbuild-vs-everburn.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.