> 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/hardware-wallet-for-pledge/registration-certificate.md).

# Registration certificate

In order to add a new owner to the stake pool, a new stake pool registration certificate needs to be created.

Even if a stake pool can have multiple owners, there can be only one rewards wallet. The script below will also change the rewards wallet to be the newly added stake pool owner, the hardware wallet.

Change the `pool-registration.sh` script from the `pool-scripts` folder with the new script below:

```bash
#!/bin/bash


source ./env

cardano-cli stake-pool registration-certificate \
--cold-verification-key-file ${NODE_HOME}/pool-keys/cold.vkey \
--vrf-verification-key-file ${NODE_HOME}/pool-keys/vrf.vkey \
--pool-pledge ${PLEDGE} \
--pool-cost ${COST} \
--pool-margin ${MARGIN} \
--pool-reward-account-verification-key-file ${NODE_HOME}/keys/hw-stake.vkey \
--pool-owner-stake-verification-key-file ${NODE_HOME}/keys/stake.vkey \
--pool-owner-stake-verification-key-file ${NODE_HOME}/keys/hw-stake.vkey \
${NET} \
--single-host-pool-relay ${RELAY1_HOST} \
--pool-relay-port ${RELAY1_PORT} \
--single-host-pool-relay ${RELAY2_HOST} \
--pool-relay-port ${RELAY2_PORT} \
--metadata-url ${METADATA_URL} \
--metadata-hash ${METADATA_HASH} \
--out-file ${NODE_HOME}/pool-certificates/pool-registration.cert
```

The changes are:

* the new stake pool owner line: \
  `--pool-owner-stake-verification-key-file ${NODE_HOME}/keys/hw-stake.vkey \`
* the `stake.vkey` was replaced with `hw-stake.vkey` on the `--pool-reward-account-verification-key-file` line.&#x20;

The script must be executed in order to generate the new stake pool registration certificate, which will need to be submitted with a transaction.


---

# 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/hardware-wallet-for-pledge/registration-certificate.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.
