You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
When exploring the paravalidators, some parachains show 0 paravalidators which isn't correct
The text was updated successfully, but these errors were encountered: