Register a Stake Pool with Metadata
Make sure you have access to:
File | Content |
---|---|
payment.vkey | payment verification key |
payment.skey | payment signing key |
stake.vkey | staking verification key |
stake.skey | staking signing key |
stake.addr | registered stake address |
payment.addr | funded address linked to stake |
cold.vkey | cold verification key |
cold.skey | cold signing key |
cold.counter | issue counter |
node.cert | operational certificate |
kes.vkey | KES verification key |
kes.skey | KES signing key |
vrf.vkey | VRF verification key |
vrf.skey | VRF signing key |
Registering your stake pool requires:
- Create JSON file with your metadata and store it in the node and in a url you maintain
- Get the hash of your JSON file
- Generate the stake pool registration certificate
- Create a delegation certificate pledge
- Submit the certificates to the blockchain
WARNING: Generating the stake pool registration certificate and the delegation certificate requires the cold keys. So, when doing this on mainnet you may want to generate these certificates in your local machine taking the proper security measures to avoid exposing your cold keys to the internet.
#
Create a JSON file with your pool's metadataStore the file on your web server. For example https://teststakepool.com/poolMetadata.json. You must store your pool metadata on reliable server, in case if metadata files will not be available then your pool might disappear from wallets and potential delegators will not be able to find it.
#
Get the hash of your metadata file uploaded to server:These command will return hash value of json file, what we just uploaded to our web server. Keep in mind that you need to put your own address instead https://teststakepool.com/poolMetadata.json
#
Generate Stake pool registration certificateParameter | Explanation |
---|---|
cold-verification-key-file | verification cold key |
vrf-verification-key-file | verification VRS key |
pool-pledge | pledge lovelace |
pool-cost | operational costs per epoch lovelace |
pool-margin | operator margin |
pool-reward-account-verification-key-file | verification staking key for the rewards |
pool-owner-staking-verification-key-file | verification staking keys for the pool owners |
pool-relay-ipv4 | relay node ip address |
pool-relay-port | port |
metadata-url | url of your json file |
metadata-hash | the hash of pools json metadata file |
out-file | output file to write the certificate to |
You can use a different key for the rewards, and can provide more than one owner key if there were multiple owners who share the pledge.
The pool-registration.cert file should look like this:
#
Generate delegation certificate pledgeTo honor your pledge, create a delegation certificate:
This creates a delegation certificate which delegates funds from all stake addresses associated with key stake.vkey
to the pool belonging to cold key cold.vkey
. If there are many staking keys as pool owners in the first step, we need delegation certificates for all of them.
#
Submit the pool certificate and delegation certificate to the blockchainTo submit the pool registration certificate
and the delegation certificates
to the blockchain by including them in one or more transactions. We can use one transaction for multiple certificates, the certificates will be applied in order.
#
Draft the transaction#
Calculate the feesFor example:
Registering a stake pool requires a deposit. This amount is specified in protocol.json
. For example, for Shelley Mainnet we have:
#
Calculate the change for --tx-outAll amounts in Lovelace
#
Build the transaction:#
Sign the transaction:#
Submit the transaction:#
Verify that your stake pool registration was successful.Get Pool ID
Check for the presence of your poolID in the network ledger state, with: