> For the complete documentation index, see [llms.txt](https://docs.toucan.earth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toucan.earth/developers/smart-contracts.md).

# Smart contracts

This section will walk you through the functions of the core smart contracts you're likely to interact with.

If you need to see where the contract are deployed, you can find addresses and ABIs [here ->](https://app.toucan.earth/contracts)

If you'd like to see the source code of the contracts, you can find it [here ->](https://github.com/ToucanProtocol/contracts). You'll also find `.json` artifacts in this repository. Do keep in mind that our contracts actually live in a different (private) repository — the linked repo is a delayed mirror of it.

{% hint style="success" %}
In the EVM, Ether and token amounts are often converted into (much) smaller standard units, to allow the use of sub-integer amounts.

Toucan's token contracts use 18 decimals, which means whenever a number of tokens is referenced, the value is converted by multiplying the quantity by 1e+18. This standard unit helps in dealing with very small amounts and avoids floating point operations. Always remember to convert for accuracy in transactions.
{% 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 by asking a question.

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

```
GET https://docs.toucan.earth/developers/smart-contracts.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.