> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/definitions/tofr/transfer-of-crypto-assets.md).

# transfer of crypto-assets

Definition of transfer of crypto-assets from Regulation (EU) 2023/1113, Article 3, point (10).

|                  |                                            |
| ---------------- | ------------------------------------------ |
| **Defined term** | transfer of crypto-assets                  |
| **Source**       | ToFR                                       |
| **Reference**    | Article 3, point (10)                      |
| **Status**       | Published                                  |
| **Refresh rule** | Regenerate after source legal-text changes |

## Definition

> 1. '**transfer of crypto-assets**' means any transaction with the aim of moving crypto-assets from one [distributed ledger address](/definitions/tofr/distributed-ledger-address.md), [crypto-asset account](/definitions/tofr/crypto-asset-account.md) or other device allowing the storage of crypto-assets to another, carried out by at least one [crypto-asset service provider](/definitions/dora/crypto-asset-service-provider.md) acting on behalf of either an [originator](/definitions/tofr/originator.md) or a [beneficiary](/definitions/tofr/beneficiary.md), irrespective of whether the originator and the beneficiary are the same person and irrespective of whether the crypto-asset service provider of the originator and that of the beneficiary are one and the same;

## Source

[ToFR, Article 3, point (10)](https://headlesslaw.com/rulebooks/tofr/articles/3/).

## Used In ToFR

* [Article 1 — Subject matter](https://headlesslaw.com/rulebooks/tofr/articles/1/)
* [Article 2 — Scope](https://headlesslaw.com/rulebooks/tofr/articles/2/)
* [Article 14 — Information accompanying transfers of crypto-assets](https://headlesslaw.com/rulebooks/tofr/articles/14/)
* [Article 15 — Batch file transfers of crypto-assets](https://headlesslaw.com/rulebooks/tofr/articles/15/)
* [Article 16 — Detection of missing information on the originator or the beneficiary](https://headlesslaw.com/rulebooks/tofr/articles/16/)
* [Article 17 — Transfers of crypto-assets with missing or incomplete information](https://headlesslaw.com/rulebooks/tofr/articles/17/)
* [Article 18 — Assessment and reporting](https://headlesslaw.com/rulebooks/tofr/articles/18/)
* [Article 19 — Retention of information accompanying the transfer (intermediary CASPs)](https://headlesslaw.com/rulebooks/tofr/articles/19/)
* [Article 20 — Detection of missing information (intermediary CASPs)](https://headlesslaw.com/rulebooks/tofr/articles/20/)
* [Article 21 — Transfers of crypto-assets with missing information (intermediary CASPs)](https://headlesslaw.com/rulebooks/tofr/articles/21/)
* [Article 22 — Assessment and reporting (intermediary CASPs)](https://headlesslaw.com/rulebooks/tofr/articles/22/)
* [Article 25 — Data protection](https://headlesslaw.com/rulebooks/tofr/articles/25/)
* [Article 29 — Specific provisions](https://headlesslaw.com/rulebooks/tofr/articles/29/)


---

# 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://www.mica.wtf/definitions/tofr/transfer-of-crypto-assets.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.