> 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/inscription-protocols-and-their-application-in-escc/technical-implementation-of-inscriptions-in-esccage.md).

# Technical Implementation of Inscriptions in ESCCage

On the technical level, the realization of ESCC chain native inscriptions is mainly based on the smart contract technology of EVM (Ether Virtual Machine), and the following are the key technical realization points:<br>

**Combination of smart contracts and inscriptions:** on ESCC, smart contracts are not only capable of executing complex logic and transactions, but can also embed inscriptions. These inscriptions can be text, code, or other types of data that are permanently recorded on the blockchain.

**Immutability and permanence:** once an inscription is written to the blockchain, it becomes part of the blockchain's history and cannot be changed or deleted. This immutability and permanence is one of the core features of ESCC, ensuring the authenticity and long-term value of the data.

**Flexible Data Embedding:** utilizing the flexibility of EVM, ESCC allows various types of data to be embedded into transactions. This can be celebratory messages, commemorative content, or even more controversial or promotional content.\
**Decentralization and Security:** The inscription protocol on ESCC leverages the decentralization and security of the blockchain to ensure that all data is safe and untamperable.


---

# 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/inscription-protocols-and-their-application-in-escc/technical-implementation-of-inscriptions-in-esccage.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.
