3.52.0-Mainnet Considerations
Introduction
Version mainnet-3.52.0
includes important changes that may temporarily affect polkadot.js functions. All functionalities should be resolved within 2 eras. Below is a shortlist of potential issues that a user may encounter after this release. Also, please note the important API changes introduced by this release.
Shortlist of potential issues
"Other Stake" disappearing
During the first era, after the runtime upgrade, the users will notice that the "other stake" indicator, together with the "active" nominators on the polkadotjs apps frontend staking page, will disappear. This happens due to the update in pallet-staking
storage API.

This issue will resolve itself once the first era passes, and you will be able to see "other stake" as well as the identities of the nominators nominating a specific validator

Alternative places where these numbers can be checked are:
Creditcoin3 Subscan: https://creditcoin.subscan.io/validator This resource will be useful to visually check the number and identity of nominators for individual validators, while the polkadotjs app frontend is not displaying the values correctly during the first few eras post-runtime upgrade

As well as checking individual nominators per validator and their stake by clicking on the number of nominators https://creditcoin.subscan.io/nominator?address=5ES52Q7gs2xrVQTAxS3kkoEkKmF5XzTAgSZbU7xTXnXozzKQ

Staking Dashboard: https://cc3-staking.creditcoin.org/#/overview If you need more details about your specific nominations, you should head over to the Creditcoin3 Staking Dashboard, which will display every detail correctly for your specific nominations, as well as the number of total active nominators, together with the pending payout amounts for the past 7 days.

Blockchain Storage Calls: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fmainnet3.creditcoin.network#/chainstate Querying
staking > erasStakers
for the current era and your nominated validator, will show you the full list of the nominator stashes and their stakes for this specific validator for a given era. You can verify that your account is indeed in the list of nominators and earning rewards. Note: for the eras after the runtime upgrade (Era 384), use staking > erasStakersPaged to get the staking information.

Active nominators disappearing from the "Targets" view
Same as above, the users will see the number indications for active nominators disappear across corresponding validators. All the sources stated above can be used to verify that the nominations are still very much active.

And this issue, as well as the first one, gets resolved after the first era post-runtime upgrade

"Payouts" page showing inaccurate information
Another issue that may arise after the upgrade to the latest version is the "Payouts" page displaying inaccurate information regarding the eras for which the validators have pending payouts. This is another harmless frontend bug, which will not hinder any protocol functionality whatsoever. However, to make our users' lives easier, the Creditcoin team has released a handy CLI tool that ensures you can view the eras where a validator has pending rewards correctly.
You can follow the validator-rewards
package readme for instructions on installation and running the tool, or follow the steps given below:
Run without installing:
npx @gluwa/validator-rewards
Global install:
npm i -g @gluwa/validator-rewards
validator-rewards
You’ll be asked to select a network:
Mainnet →
wss://mainnet3.creditcoin.network/ws
Testnet →
wss://rpc.cc3-testnet.creditcoin.network/ws
Custom → type any
ws://
orwss://
network URL (prefilled from.env
if present)
Then enter a validator stash (SS58). You’ll see a table like:
┌─────────┬──────┬────────┬──────────────┬─────────────┬────────────┐
│ (index) │ era │ points │ pagesClaimed │ pagesToClaim│ totalPages │
├─────────┼──────┼────────┼──────────────┼─────────────┼────────────┤
│ 0 │ 578 │ 1234 │ '0' │ 1 │ 2 │
│ 1 │ 579 │ 987 │ '—' │ 1 │ 1 │
└─────────┴──────┴────────┴──────────────┴─────────────┴────────────┘
The tool will display the eras for which the specified validator has pending rewards, together with the number of points accumulated through that era and the number of pages that the validator has to claim
Last updated