> For the complete documentation index, see [llms.txt](https://docs.glacislabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glacislabs.com/glacis-core/troubleshooting/integration-checklist.md).

# Integration Checklist

The checklist below is intended to help prepare a project that integrates Glacis.

* Extend your contracts with the latest version of Glacis Labs [client](https://github.com/glacislabs/v1-core/blob/main/contracts/client/GlacisClient.sol).
* Deploy your contracts specifying Glacis Router or Glacis Token Mediator addresses as constructor parameters depending if you want to pass only cross-chain messages or cross-chain tokens along with messages. Addresses for Glacis infrastructure contracts can be obtained in [Supported Chains](/glacis-core/references/supported-chains.md)
* If your project requires token transfers with execution you can deploy your token using XERC20 standard and simply add Glacis XERC20 Extension to it. Otherwise, it is unnecessary to integrate this additional standard.
  * In case that you have a legacy ERC20 you can deploy an XERC20LockBox and migrate your legacy ERC20 tokens to your recently deployed XERC20.

Feel free to reach out to the team on [Telegram](https://t.me/+KJZFSN67crY4ZDJh)!


---

# 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.glacislabs.com/glacis-core/troubleshooting/integration-checklist.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.