# Eras - 384 to 385

This page is an archive of expected display issues that existed during the first 2 eras (384-385) post `3.52.0-mainnet` runtime upgrade, which are no longer relevant.

### Summary

* ["Other Stake" disappearing on Polkadot.js frontend](#other-stake-disappearing-on-polkadot.js-frontend)
* ["Active Nominators" disappearing from the "Targets" view on Polkadot.js frontend](#alternative-places-where-these-numbers-can-be-checked-are)

#### "Other Stake" disappearing on Polkadot.js frontend

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](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fmainnet3.creditcoin.network#/legacy-staking) staking page, will disappear. This happens due to the update in `pallet-staking` storage API. 

<figure><img src="/files/GEvX0YovIptYpyAv5YkF" alt=""><figcaption></figcaption></figure>

This issue resolved itself once the first era ended. "other stake" became visible as well as the identities of the nominators nominating a specific validator

<figure><img src="/files/Viyug0QUnvcrOgAm5Eou" alt=""><figcaption></figcaption></figure>

#### 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

<figure><img src="/files/zRwY4ZrFHADdYsqL26sk" alt=""><figcaption></figcaption></figure>

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>

<figure><img src="/files/JsNBXHJrZrwWjMPJW2I9" alt=""><figcaption></figcaption></figure>

* 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.

<figure><img src="/files/1wSFMlrEAbhr0iVVQuPj" alt=""><figcaption></figcaption></figure>

* 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. \
  \
  \&#xNAN;*Note: for the eras after the runtime upgrade (Era 384), use staking > erasStakersPaged to get the staking information.*&#x20;

<figure><img src="/files/h7y10uP6AWmy75nGy5hc" alt=""><figcaption></figcaption></figure>

#### 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.

<figure><img src="/files/EHafxHEC0ebnicsw4aRW" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/BdHo0n57ZnrqcicXlIpT" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.creditcoin.org/releases/3.52.0-mainnet/3.52.0-mainnet-considerations/eras-384-to-385.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.