> For the complete documentation index, see [llms.txt](https://docs.21x.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.21x.eu/order-book.md).

# Smart Contract ABI

To interact with the smart contract, users must utilize the **ABI (Application Binary Interface)**, which defines the contract’s functions, input/output types, and how they are encoded for low-level interaction with the Ethereum Virtual Machine (EVM). The ABI is essential for constructing valid function calls and decoding returned data.

Access to the smart contract is **permissioned via a whitelist**. Only wallet addresses that have been explicitly authorized (i.e., added to the contract’s whitelist) are able to execute transactions or call restricted functions. Any attempt to interact from a non-whitelisted address will be rejected by the contract.

Please ensure that your wallet address is submitted for whitelisting before attempting any interaction with the contract.\
 

<figure><img src="https://1882050719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNZgTlpImxlgPXZmqZUcB%2Fuploads%2FUS8ydefaPFvzvYle4lxd%2FSmart-Contract-Map.png?alt=media&amp;token=12ae67b0-2474-40e1-81dd-40e38767e74f" alt=""><figcaption></figcaption></figure>


---

# 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.21x.eu/order-book.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.