search

input-output-hk / smash

Stakepool Metadata Aggregation Server
36 stars 7 forks source link

smash API returns pool hash error that doesn't seem correct #188

Open Vardominator opened 2 years ago

Vardominator commented 2 years ago

I'm unable to find my pool in Daedalus, and only Daedalus. When running curl https://smash.cardano-mainnet.iohk.io/api/v1/errors/c485ab20bd3f105e59f3c50a0d3fbaf615a51f70a1c6d29d00a1fd27, I receive the following error:

[{"utcTime":"1638415532.270524s","poolId":"c485ab20bd3f105e59f3c50a0d3fbaf615a51f70a1c6d29d00a1fd27","retryCount":1,"cause":"URL parse error from poolId 'c485ab20bd3f105e59f3c50a0d3fbaf615a51f70a1c6d29d00a1fd27' when fetching metadata from '34.65.134.134' resulted in : 34.65.134.134","poolHash":"f3ace0265ea1772fd151e178db79715405fcd074fe4ae1ca33216c752e3f1c86","time":"02.12.2021. 03:25:32"},{"utcTime":"1638155855.781211s","poolId":"c485ab20bd3f105e59f3c50a0d3fbaf615a51f70a1c6d29d00a1fd27","retryCount":1,"cause":"Hash mismatch from poolId 'c485ab20bd3f105e59f3c50a0d3fbaf615a51f70a1c6d29d00a1fd27' when fetching metadata from 'https://tinyurl.com/b9pshetu'. Expected bbd17554c79d3d00f065ae41a3461fabd96b7974dc0832ac62aeebae19918487 but got f3ace0265ea1772fd151e178db79715405fcd074fe4ae1ca33216c752e3f1c86.","poolHash":"bbd17554c79d3d00f065ae41a3461fabd96b7974dc0832ac62aeebae19918487","time":"29.11.2021. 03:17:35"}]

However, all other pool monitoring sites are showing that this pool is in a healthy state: https://pool.vet/#GENS1 https://pooltool.io/pool/c485ab20bd3f105e59f3c50a0d3fbaf615a51f70a1c6d29d00a1fd27/epochs https://pool.pm/c485ab20bd3f105e59f3c50a0d3fbaf615a51f70a1c6d29d00a1fd27 https://adapools.org/pool/c485ab20bd3f105e59f3c50a0d3fbaf615a51f70a1c6d29d00a1fd27

The pool is also findable in Yoroi.

I'm also able to reproduce the metadata hash in the node from three different sources:

$ cardano-cli stake-pool metadata-hash --pool-metadata-file <(curl -s -L https://raw.githubusercontent.com/geniusyield/GeniusStakePool/main/stake_pools/g1.json)
20c9a62dafc8450f0c2ed61bbb7ce6ffd7425fba04108a7c6e91ccee8eaa0964
$ cardano-cli stake-pool metadata-hash --pool-metadata-file <(curl -s -L https://tinyurl.com/b9pshetu)
20c9a62dafc8450f0c2ed61bbb7ce6ffd7425fba04108a7c6e91ccee8eaa0964
$ cardano-cli stake-pool metadata-hash --pool-metadata-file <(cat /cardano/cardano-node/gens1/config/pool_metadata.json)
20c9a62dafc8450f0c2ed61bbb7ce6ffd7425fba04108a7c6e91ccee8eaa0964

Why are the hashes, both the supposedly correct and incorrect ones in the SMASH error response, not matching the hash that the cardano CLI produces?

Seaside-Staking commented 2 years ago

Exact same problem here for ticker SEA, Every pool fetching website sees the hashes as correct except daedelus. Metadata change has been more than 24 hours ago