> For the complete documentation index, see [llms.txt](https://docs.artis.eco/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artis.eco/artis-2.0-whitepaper/challenges-and-solutions/effortless.md).

# Effortless

Public blockchains typically use a volatile coin to pay transaction fees - e.g. ETH for Ethereum or AVAX for Avalanche. While transaction fees are typically low as long as the limited block space is not filled, transaction fees become outrageously high, once blocks are filled - e.g. in Ethereum simple transactions can easily cost 5 EUR. 

Real-world applications can't handle that and need transaction cost < 0.01 EUR.&#x20;

ARTIS ∑2 uses sEUR as its coin and therefore there will be no volatility for the price of the coin. Additionally the available block space will only have to be paid if it exceeds 20% of total capacity:&#x20;

* 0 sEUR transaction fee for 20% of the block space
* \~0.0002 sEUR transaction fee for simple transactions (Gas price: 10 Gwei)&#x20;

{% hint style="success" %}
ARTIS ∑2 will have 0€ or very low, predictable transaction fees.
{% endhint %}


---

# 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://docs.artis.eco/artis-2.0-whitepaper/challenges-and-solutions/effortless.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.