Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible substrate staking pallet bug: empty validator info query results #5140

Open
traumschule opened this issue Apr 23, 2024 · 3 comments

Comments

@traumschule
Copy link
Contributor

I noticed a 'hole' querying validator info that may indicate a bug in substrate itself or for example modifications to Joystream/substrate.

The first symptom is the missing own stake both in p-js and pioneer.
ownstakebug-pioneer
ownstakebug-pjs

On further inspection following chain queries return empty information as well:

  • staking.bonded
  • staking.ledger

In following screenshot for each query the first entry is for j4Rc8VUXGYAx7FNbVZBFU72rQw3GaCuG2AkrUQWnWTh5SpemP the second (correct): j4ShWRXxTG4K5Q5H7KXmdWN8HnaaLwppqM7GdiSwAy3eTLsJt. Both staking.payee and staking.validators return correct output for the first address (24) and are omitted here regarding the second (26) for brevity.

ledger

Please confirm that this problem persists and consult upstream if necessary. (cc @rossbulat )

Finally correct account information for 24 from the p-js details pane:
jssde-details

(feel free to change title based on findings)

@mochet
Copy link

mochet commented Apr 24, 2024

Someone else reported the same issue on our Discord and made a stackexchange issue for it: https://substrate.stackexchange.com/questions/11260/validator-reports-0-own-stake

It ended up showing up for them randomly after some time. I did look on Polkadot and it appears some validators had the same thing happening to them. I also asked on the Polkadot Watercooler and linked the stackexchange thread but never got any response or interest from anyone.

@traumschule
Copy link
Contributor Author

I noticed another staking anomaly that shows and counts one nominator (j4RUKCimuWUSAC6tYVL5X1cn6qW2iVjgT35DFzgccCreqTnd6) twice for j4Wfvho5H5kdogeZfb3pnuZGzucyjUPVkvj4BNLVYPf4JzdVZ.

To my understanding one account can nominate a validator only once but here it makes the bulk of the total stake with 2x1.258M/3.8M.

staking.nominators:
  [
    [
      j4RUKCimuWUSAC6tYVL5X1cn6qW2iVjgT35DFzgccCreqTnd6
    ]
    {
      targets: [
        j4Wfvho5H5kdogeZfb3pnuZGzucyjUPVkvj4BNLVYPf4JzdVZ
      ]
      submittedIn: 1,894
      suppressed: false
    }
  ]

@bedeho
Copy link
Member

bedeho commented May 12, 2024

Have not had time to review, is this urgent?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants