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
In a "destroying" nominating pool, the pool's root is unable to view the complete list of accounts that are still members of the pool and have not yet unbonded.
The behavior appears inconsistent, and the pool's status could be merely circumstantial.
Just removed the Subscan API key to fall back tot their 2 calls /s per IP at #2184. I'll do some tests to check the member list behaviour and get back.
In a "destroying" nominating pool, the pool's root is unable to view the complete list of accounts that are still members of the pool and have not yet unbonded.
The behavior appears inconsistent, and the pool's status could be merely circumstantial.
Screenshots from pool #159:
Staking dashboard:
Subscan:
https://polkadot.subscan.io/nomination_pool/159
nominationPools.poolMembers
result is consistent with Subscan.The text was updated successfully, but these errors were encountered: