Metadata hash doesn't match registered hash

Staking & Delegation Operate a Stake Pool
1

Metadata hash 441b9141b36220bfe90b83fa348f628cdcb10eb99649659dd6c4d13ce315c832 doesn’t match registered hash cf8fa3cd3d96ca7990ec84a6f6e99083718731fccb25eda7e5811c2d7a761fde

https://pool.vet/#edu1

I can’t figure out how to get this to properly match.

I created a gist, put my metadata in there. Took the raw data of that and shortened the link to get the URL hash.

Any suggestions on what the issue could be?

2
  • switch the branch to master (click main, type master and click create branch master)
    image

Cheers,

3

Screen Shot 2021-05-24 at 9.34.29 AM
Screen Shot 2021-05-24 at 9.34.29 AM3552×1736 359 KB

It is not obvious to me where the branch option is for gists.

4

Give me the link and I will show u

Or go to my guide and check there

Step 6

5

That is the registered url:
https://git.io/J3T5S

but now it seems working:

$ wget https://git.io/J3T5S
--2021-05-24 17:16:39--  https://git.io/J3T5S
Resolving git.io (git.io)... 52.204.190.140, 54.87.76.159, 35.174.24.146, ...
Connecting to git.io (git.io)|52.204.190.140|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://gist.githubusercontent.com/austinnegron/9b44c804e2021dc82098d7b72cb0b1ca/raw/72fbc0edad40e2df1f55d308be49af950c1a93e1/tca_metadata_v2 [following]
--2021-05-24 17:16:39--  https://gist.githubusercontent.com/austinnegron/9b44c804e2021dc82098d7b72cb0b1ca/raw/72fbc0edad40e2df1f55d308be49af950c1a93e1/tca_metadata_v2
Resolving gist.githubusercontent.com (gist.githubusercontent.com)... 185.199.110.133, 185.199.109.133, 185.199.108.133, ...
Connecting to gist.githubusercontent.com (gist.githubusercontent.com)|185.199.110.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 145 [text/plain]
Saving to: ‘J3T5S’

J3T5S                                           100%[=====================================================================================================>]     145  --.-KB/s    in 0s      

2021-05-24 17:16:39 (2.29 MB/s) - ‘J3T5S’ saved [145/145]

the only problem could be is that there is no HTTP content header with applicaton/json

related:

6

Hi Laplasz… it worked. And I’m not entirely sure why.

My solution was to keep hashing my metadata.json until it gave me the same hash from the git url. I guess it was just guess & check for me. Cheers.

7

Thank you Alex. Taking the raw data from the repo worked much better than taking the raw data from the gist. Cheers.

1 Like