there are few steps which help to verify if your registration is alright and if not helps to debug the issue! I learned this on try and error and by following the official Cardano Telegram channel.
- Check the hash number of your published metadata.json
cardano-cli stake-pool metadata-hash --pool-metadata-file <(curl -s -L https://git.io/JtepM)
cardano-cli stake-pool metadata-hash --pool-metadata-file <(cat poolMetaData.json)
Replace the URL and the poolMetaData.json as it fits your setup.
- If the hash number is the same, chek if your metadata is represented correctly with
cardano-cli query ledger-state --mainnet --allegra-era --out-file ledger.json
This operation is memory hungry and will show if your hardware is good enough to run a stake pool. Short term it helps to include a swapfile on your node to resolve memory issues.
Now look through the file ledger.json and search your hash number.
- Sometimes Daedalus is slow in showing your pool ticker. This can be resolved by deleting the file
cardano-node.socketwhen the application Daedalus is not running.
How to find this file: click on
Helpin your Daedalus application, then click on
Daedalus state directory:. Next open the directory
wallet. Here you can find the file
cardano-node.socketand delete it after the Daedalus application is turned off. Restart your Daedalus. Now it should fetch your pool ticker. This process takes some time.
- If you still experience problems I learned that it helps to register the pool with a new metadata.json name. For example you might consider to give your metadata.json file a version number: metadata1.json.