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

Paravalidators for some parachains do not show up #669

Open
DrW3RK opened this issue Jan 25, 2025 · 1 comment
Open

Paravalidators for some parachains do not show up #669

DrW3RK opened this issue Jan 25, 2025 · 1 comment

Comments

@DrW3RK
Copy link

DrW3RK commented Jan 25, 2025

When exploring the paravalidators, some parachains show 0 paravalidators which isn't correct

Image
@kukabi
Copy link
Member

kukabi commented Jan 26, 2025

Thanks for the report @DrW3RK. I started with importing the missing paras, and now I'm looking into this.

As a note, to my knowledge, not all paras have assigned cores at every block, so it seems normal that some paras will have 0 paravalidators assigned through some blocks, but eventually they should be assigned to a core of n paravalidators.
This data is fetched from the SubVT backend system, not the node RPC directly, so the data arrives not at every block, but every few blocks, as SubVT processing is slower than the actual block rate. So it's only going to update every few blocks, but you're right, it seems to be getting locked after switching to Polkadot.

In Kusama, you should be able to observe how it changes (although slower than actual) by keeping the pointer over a certain para - especially an active one such as the system chains.

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

2 participants