Open Juanma0x opened 4 months ago
Just removed the Subscan API key to fall back tot their 2 calls /s per IP at https://github.com/polkadot-cloud/polkadot-staking-dashboard/pull/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:![image](https://github.com/paritytech/polkadot-staking-dashboard/assets/120041850/d1e6ffce-f357-4290-a7bd-8fc18fc7a7ed)
Subscan: https://polkadot.subscan.io/nomination_pool/159![image](https://github.com/paritytech/polkadot-staking-dashboard/assets/120041850/9d11d1d9-9e2f-4ae8-8357-50c64b777579)
nominationPools.poolMembers
result is consistent with Subscan.