> 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/eu-level/q-and-a/esma-qa-2607-staking-own-account.md). # Staking on own account | | | | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Authority** | ESMA | | **Q\&A ID** | ESMA\_QA\_2607 | | **Status** | Answer Published | | **Published** | 9 July 2025 | | **Legal basis** | [Article 70(1)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-2/article-70.md) [MiCA](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md); [Article 66(1)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-2/article-66.md) [MiCA](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md); [Article 66(2)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-2/article-66.md) [MiCA](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md) | | **Source** | [ESMA Q\&A](https://www.esma.europa.eu/publications-data/questions-answers/2607) | ### Question Does the Markets in Crypto-Assets Regulation (MiCA) permit the staking of clients’ crypto-assets by crypto-asset service providers (CASPs) for their own account? *** ### Answer [Article 70(1)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-2/article-70.md) of MiCA provides that CASPs that “hold crypto-assets belonging to clients or the means of access to such crypto-assets shall make adequate arrangements to (...) prevent the use of clients’ crypto-assets for their own account”. CASPs are thus expected to refrain from using clients’ crypto-assets for their own account. Consequently, MiCA does not allow the staking of clients’ crypto-assets by CASPs for their own account, even in cases where the client has explicitly provided consent. In line with the European Commission Q\&A 2067 available on ESMA’s website, CASPs and clients may mutually agree on the terms under which staking-as-a-service is provided by the CASP, provided that the profits from staking do not solely benefit the CASP 1 . In addition, and by virtue of their regulated status, CASPs providing staking-as-a-service to their clients should act in the best interests of their clients. When providing crypto-asset services, CASPs must act in accordance with the requirements of [Article 66(1)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-2/article-66.md) of MiCA and ensure that they are acting honestly, fairly and professionally in accordance with the best interests of their clients and prospective clients. In addition, they must comply with their obligations under [Article 66(2)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-2/article-66.md) of MiCA and ensure that all information, including marketing communications, addressed to clients or prospective clients is fair, clear and not misleading. Therefore, ESMA recommends that CASP clearly communicate about the costs ultimately borne by clients using the CASP as intermediary to stake their crypto-assets. Accordingly, CASPs should be transparent about any fees or commissions taken by the CASP itself as well as those charged by third parties involved in the provision of the service. 1 As clarified in European Commission Q\&A 2067, staking-as-a-service is when the benefits of staking are shared between the CASP and the client: “staking services (also referred to as staking-as-a-service) are provided to clients for a consideration by intermediaries that undertake to stake the clients’ crypto assets on their behalf. The staking service provider will collect the yield or obtain the validator privileges allowing them to earn block rewards. This yield or these block rewards are then distributed between the service provider as consideration for their service (staking the assets on the client’s behalf, exercising validator obligations and collecting the block rewards, etc.), and the staking service provider’s clients, who are the ultimate owners of the crypto assets that are staked”. *** **Source:** [ESMA original document](https://www.esma.europa.eu/publications-data/questions-answers/2607) --- # 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/eu-level/q-and-a/esma-qa-2607-staking-own-account.md?ask=&goal= ``` `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.