> For the complete documentation index, see [llms.txt](https://docs.escc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.escc.io/core-features-and-technical-aspects-of-escc/core-features-of-escc.md).

# Core Features of ESCC

ESCC boasts several distinctive features that set it apart from other blockchain platforms:

**Optimized for Stablecoin Transactions:** The platform is fine-tuned to handle stablecoin transactions with high efficiency and low costs, making it ideal for both large-scale and everyday transactions.<br>

**Stablecoin as Gas Fee:** A unique feature of ESCC is the use of stablecoins for transaction fees (gas), which brings predictability to transaction costs and mitigates the impact of crypto market volatility.<br>

**High Performance and Scalability:** Drawing from EOS's performance, ESCC offers fast transaction processing and the ability to scale, accommodating growing stablecoin usage.<br>

**Developer-Friendly Environment:** With tools and resources tailored for developers, ESCC fosters an environment conducive to developing a wide range of stablecoin applications, from DeFi to remittances and beyond.<br>


---

# 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.escc.io/core-features-and-technical-aspects-of-escc/core-features-of-escc.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.