Hey everyone. I see that Metadata hash not matching is a common issue on the forums (you can check your own pool at pool.vet) and was hoping somebody may be able to provide additional insight:
Does this mismatch affect block production?
What causes a mismatch? (Is it possibly the result of changes to the poolmetadata.json file in my GitHub repository?)
Can I solve the issue by simply resubmitting my pool.cert with the new poolMetaDataHash.txt (i.e. changing the .txt file on my air gapped machine to the new hash as noted in pool.vet)?
Nope, the block production is not affected but the informations included inside the metada file will not be visible (ticker, pool name, description, etc); so other people will not be able to find your pool by ticker (only by POOL ID), and also they can’t see the description, pool name, etc
What causes a mismatch? (Is it possibly the result of changes to the poolmetadata.json file in my GitHub repository?)
If u registered the metadata file and then u performed some changes on github then the hash will be changed, resulting the mismatch… to solve it you can rollback the modifications on github or send another certificate
Can I solve the issue by simply resubmitting my pool.cert with the new poolMetaDataHash.txt (i.e. changing the .txt file on my air gapped machine to the new hash as noted in pool.vet)?
Yes, every time when you will modify the metadata file you will need to submit a new certificate with the new hash