> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/aeternity-developer-tools/protocol/core-protocol-components/smart-contracts/smart-contract-languages/solidity.md).

# Solidity

## The Solidity Language

æternity has limited support for the Solidity language bytecode and ABI. There are a number of test cases and some scaffolding code. However, it is not mature enough to be part of consensus and thus the Solidity ABI is not allowed on chain.

For a full description of Solidity see [The Solidity Specification](https://solidity.readthedocs.io/).

### The Solidity\_01 ABI <a href="#the-solidity_01-abi" id="the-solidity_01-abi"></a>

Note that the Solidity\_01 ABI specifies that the create contract initial call returns the actual bytecode to be stored in the contract state tree to be used for future calls.

See [The Solidity Specification:ABI](https://solidity.readthedocs.io/en/develop/abi-spec.html)

#### Storing the contract state <a href="#storing-the-contract-state" id="storing-the-contract-state"></a>

Contracts store the VM storage map containing 256 bit binaries for both keys and values in the MPT. Undefined keys are treated as having the value 0 and keys bound to the value zero are stored as the empty binary, thus purging them from the tree.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aeternity.com/aeternity-developer-tools/protocol/core-protocol-components/smart-contracts/smart-contract-languages/solidity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.