> For the complete documentation index, see [llms.txt](https://apexpool.gitbook.io/stake-pool-scripts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apexpool.gitbook.io/stake-pool-scripts/stake-pool-registration/retiring-the-stake-pool.md). # Retiring the stake pool When a stake pool is not operating anymore, it must be retired. A stake pool must be retired in order to recover the 500 ADA deposit. In order to retire a stake pool, a `stake pool deregistration certificate` must be created and submitted to the blockchain with a transaction (similar to the `stake pool registration certificate`). The transaction to submit the `stake pool deregistration certificate` must be signed with the cold key (`cold.skey`) and with the payment key of the payment address where the UTxO used to pay the transaction fee resides. When creating the `stake pool deregistration certificate`, the epoch when the retiring takes place must be specified. After the stake pool is retired, the 500 ADA deposit is returned to the stake pool rewards address (just like the regular stake pool rewards). In order for this to happen, the stake key must be still registered until the rewards are withdrawn. If the stake key is not registered, the 500 ADA deposit are lost (they will be sent to the treasury instead). The following script can be used to create the `stake pool deregistration certificate`: ```bash #!/bin/bash source ./env cardano-cli stake-pool deregistration-certificate \ --cold-verification-key-file ${NODE_HOME}/pool-keys/cold.vkey \ --epoch 365 \ --out-file ${NODE_HOME}/pool-certificates/pool-deregistration.cert ``` The transaction to submit this certificate is similar to the transaction described in the section above. The `--witness-override 3` should be updated to `2` (because the transaction will only be signed by 2 keys: the `cold.skey` and a payment skey). --- # 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://apexpool.gitbook.io/stake-pool-scripts/stake-pool-registration/retiring-the-stake-pool.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.