> For the complete documentation index, see [llms.txt](https://docs.cryptolegacy.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptolegacy.app/detailed-flows/detailed-cross-chain-contract-copy-flow.md).

# Detailed Cross-chain Contract Copy Flow

Create and replicate CryptoLegacy contracts across chains with identical settings, and set up Guardians and Recovery per chain.

* **Create Contracts:**\
  On each supported chain, you can create any number of CryptoLegacy contracts for each owner with a unique address.
* **Replicate Contracts:**\
  You can replicate each contract on other chains using the same address, beneficiaries, shares, delay, and distribution settings.
* **Setup Guardians and Recovery:**\
  On each new chain, you must set up Guardians and Recovery settings.


---

# 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.cryptolegacy.app/detailed-flows/detailed-cross-chain-contract-copy-flow.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.