For your kind consideration, this is the issue we are facing with the mainnet of Aleph Zero, this network is implementing the runtime version aleph-node/46 and both, the local ws:// endpoint, and Crunch's metadata, are up to date with the appropriate versions.
The first symptom are shown in the logs as:
[WARN crunch::runtimes::aleph_zero] Crunch upgrade might be required soon. Local static metadata differs from current chain runtime version.
[INFO crunch::report] <details><summary>Next era expect <b>NO</b> rewards 🙁</summary>
(apart of the WARN, please note the absence of the Earlier claimed comment in the INFO block.
After which the bot runs without apparent problems and even hooks OK with the paidEras() event, but it fails to retrieve the pending payments and process no payouts at all.
Thus, with the help of another community member, it was determined that at least two functions seem to be failing in the aleph_zero.rs file:
paulormart
commented
1 year ago
Dear Paulo, I hope this case finds you well,
For your kind consideration, this is the issue we are facing with the mainnet of Aleph Zero, this network is implementing the runtime version
aleph-node/46and both, the local ws:// endpoint, and Crunch's metadata, are up to date with the appropriate versions.The first symptom are shown in the logs as:
(apart of the WARN, please note the absence of the
Earlier claimedcomment in the INFO block.After which the bot runs without apparent problems and even hooks OK with the paidEras() event, but it fails to retrieve the pending payments and process no payouts at all.
Thus, with the help of another community member, it was determined that at least two functions seem to be failing in the aleph_zero.rs file:
node_runtime::validate_codegennode_runtime::storage().staking().history_depth(), and/orcrunch.client().clone().storage().fetch()for the abovehistory_depth_addrDo you have an idea were to start looking for a solution?
Please advise!
Best regards...
Milos