Apologies for the lack of updates, I’ve been in contact with support since Dec 23.
The metadata has been updated multiple times with the correct hash included while generating the registration certificate. Before each registration, the metadata file was downloaded and the hash from the downloaded metadata file was used.
https://kelownastaking.ca/poolMetadata.json
Hash: 441b9c3e2c35feedfe30754b750ec9571897ab5b206fcf07918f572828a393f4
https://kelownastaking.ca/metadata.json
Hash: 5227a0d6503b03552ffbdb67b39f27d0ea0641e4620b1694ca3f6ed8f84077e8
https://kelownastaking.ca/metadata-1.json
Hash: c8b1ecd8f94b76a9c029fe9e3e210c043314de6e351617fe6233be26b5b2cc05
https://raw.githubusercontent.com/ezrabenson/mt/main/mdata.json
Hash: e90849a0b237d32659d6e557425e36ad972ff6414415cd43f0c3949a779efbbc
At the moment, it appears that it may be an issue with SMASH.
KLWNA shows on all pool explorers with the correct metadata, even on pooltool which previously was not updating.
My pool retired in epoch 215 and was brought out of retirement the same epoch.
Prior to SMASH 1.4.0, retired pools that are active do not show up in Daedalus.
- [CAD-2476] - SMASH not returning active pools that were previously retired #140
Release SMASH 1.4.0 · input-output-hk/smash · GitHub
Check if pool is delisted
curl --silent “https://smash.cardano-mainnet.iohk.io/api/v1/delisted”
2>&1 | grep -o e63d0fa435f185cf651c81bf666f51199ca6dd7ba1fe7cbf75d76776
Check if pool is retired
curl --silent “https://smash.cardano-mainnet.iohk.io/api/v1/retired”
2>&1 | grep -o e63d0fa435f185cf651c81bf666f51199ca6dd7ba1fe7cbf75d76776
e63d0fa435f185cf651c81bf666f51199ca6dd7ba1fe7cbf75d76776
Check for errors
There are no errors, the pool is not delisted, however it does show up as retired.
I am waiting on a response from support as they are checking to see if SMASH 1.4.0 has been deployed on their servers.