Metadata hash mismatch, now corrected. 24h passed. How long before stake pool is visible in Daedalus?

Staking & Delegation Setup a Stake Pool
1

Have registered the stake pool two days ago with a wrong metadata hash.
Corrected that yesterday. Metadata hash matches, 24h passed but stake pool still not visible in Daedalus.

What else should I do?

Stake pool id:
41f3b15c7c181a004e178446c33a379c686d404aa99ad680199d8b83

curl https://smash.cardano-mainnet.iohk.io/api/v1/errors/41f3b15c7c181a004e178446c33a379c686d404aa99ad680199d8b83 | jq

2

On yoroi ur pool is visible, u should wait more time… possible daedalus sync issues

If not u can open a ticket to daedalus support team

1 Like
3

Hi,

it should pop up imediately. if not you can follow few tricks mentioned here:

Maybe you can up vote it, such that more people will find it useful.

Best,
Johann

2 Likes
4

Thank you. I had a typo in my pool metadata json file, that is I only submitted registration once because the correcting the typo change required changes on the webserver side. Not on the registration side.

With that said, the scripts that you are referring too are returning the same hash since yesterday because my webserver was updated. The question is how much more time will SMASH proxy need to include my stake pool in Daedalus.

5

That’s reassuring. Thank you. I take it’s just an issue how much longer does SMASH proxy needs to update its entries.

6

Hi maciejso, I have the same problem here. My metadata.json at the web server had a space (already fixed) giving me the “Hash mismatch from poolId” error, now the hash on both files are exactly the same. How long does SMASH server need to reprocess the reading? Or do I need to submit another registration? Cheers!

7

In my experience pooltool.io and cardanoscan.io had the pool details much quicker. Yoroi’s was next, the backend is adapools.org. Daedalus took the longest for me, about 24 hours.

what are the first two showing, are they correct?

you shouldn’t have to re-register unless the hash in the poolMetaDataHash.txt file your registered doesn’t match the hash of your .json on the website

8

Thanks KrakenStaking, cardanoscan already updated all metadata info but pooltool and adapools not yet. At pooltools I’ve got an empty ticker and description and on adapools I’ve got the previous ticker name and description. Pledge, fees and other info are already up to date.

Hopefully everything will be correct in the next 24 hours or so.

Cheers!

9

if it still is not working can you post your .json here? also what is your pool id?

10

Thank you. I got it working by reverting to the previous version of the metadata file. There were no blockchain changes needed.

11

Hi,
I recently changed my pool metadata.json with extended metadata and saw metadata hash is not matching with registered metadata hash. I know, I need to re-register but if I don’t do right away, is there any issues?

12

Ticker issue, so u will can’t find the pool in daedalus or on pooltool.io if u will search by ticker

13

no issues…pool is visible in all places including daedalus. I am just worried for leaderslot which is scheduled tonight. do you see any issues to miss block with this?

14

Nope, no issues; metadata is for pool infos for daedalus or sites

1 Like
15

But it play important role in pool registration. I will re-register certificate post tonight. Don’t want to loose block :slight_smile:

16

Or u can restore the old metadata

17

was trying but no luck so far.

18

Why? Just delete what u added

19

What is the ticker?

20

yeah, doing it. Thanks for your quick response as always, Alex.