> For the complete documentation index, see [llms.txt](https://docs.t-rex.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.t-rex.network/guides/cross-chain.md).

# Cross-chain

These guides cover an asset that is active on satellite chains: opening a satellite, moving positions to it and back, transferring there, and operating the validations that authorize those transfers. In every one of them the reference chain decides and the satellite executes.

| Order | ID | Guide                                                                                                           | What it does                                                           | Who                      |
| ----- | -- | --------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | ------------------------ |
| 1     | 33 | [Open an asset on a satellite](/guides/cross-chain/33.-open-an-asset-on-a-satellite.md)                         | Sets the route, the peer and the windows for one satellite.            | Issuer                   |
| 2     | 30 | [Delegate a position out to a satellite](/guides/cross-chain/30.-delegate-a-position-out-to-a-satellite.md)     | Makes a holder's position active on a satellite, for the same owner.   | Investor                 |
| 3     | 31 | [Transfer on a satellite](/guides/cross-chain/31.-transfer-on-a-satellite.md)                                   | Authorizes, executes and settles a transfer out of a satellite wallet. | Investor                 |
| 4     | 34 | [Transfer between two satellites](/guides/cross-chain/34.-transfer-between-two-satellites.md)                   | The same, when the recipient is on another satellite: two reports.     | Investor                 |
| 5     | 32 | [Recall a position to the reference chain](/guides/cross-chain/32.-recall-a-position-to-the-reference-chain.md) | Returns a position to the reference chain, for the same owner.         | Investor, or Token Agent |
| 6     | 35 | [Discard or resolve a validation](/guides/cross-chain/35.-discard-or-resolve-a-validation.md)                   | Releases the reservation of a validation that will not settle.         | Validation Keeper        |
| 7     | 36 | [Handle a late reconciliation or a halt](/guides/cross-chain/36.-handle-a-late-reconciliation-or-a-halt.md)     | Responds to the alarms of the cross-chain layer and resumes operation. | Issuer                   |

The "Order" column follows the life of a position on a satellite, then the operations around it. The "ID" column is the permanent reference number of each guide. See [How guides are numbered](/guides/about-the-guides.md).

Three things to know before reading them.

* **What is described on the satellite side.** These guides give the calls on the reference chain in full. On a satellite, they state what T-REX Lite does and what it checks. Its interface is covered under Build: Implement T-REX Lite on a new chain.
* **Which movement to use.** A delegation-out and a recall move a position between the reference chain and a satellite for one owner. A transfer changes the owner, and always starts from a wallet on a satellite. See [Movement types](/cross-chain-the-distributed-register/movement-types.md).
* **Where the concepts are.** The validation is explained in [Authorization before execution](/cross-chain-the-distributed-register/authorization-before-execution.md), and its states in [The dual-state lifecycle](/cross-chain-the-distributed-register/the-dual-state-lifecycle.md).


---

# 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.t-rex.network/guides/cross-chain.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.