-
Notifications
You must be signed in to change notification settings - Fork 110
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
is it possible to get pendingRewards for an account member of a pool? #220
Comments
@p4tpr0 Of course. you can try to use this |
It seems I can't get it work: And more importantly, I can see how this call can retrieve api.call.nominationPoolsApi.pendingRewards for a member of the pool. |
|
Ok, thanks, works better without quotes around the effective pool ID (might need to fix the example in the doc). I find the result a bit odd. Issuing this: returns a list of 159 pool members when the real pool currently has only 6 members. My address is not in the result when it's currently a member of that pool. It looks like I'm not sending my request to the right provider. Does westend.api.subscan.io serves polkadot production data or testing data? |
@p4tpr0 Sorry, I didn't understand what you mean, can you explain the problem to me in detail? |
OK :) As far as I know, this particular information is stored here: https://polkadot.js.org/docs/substrate/runtime/#pendingrewardsmember-accountid-balance but it seems I can't get it. |
You can use https://support.subscan.io/#pool-members and
|
EDIT : OK, nevermind, I was not hitting the proper provider. Sorry for the noise. _I've tried this already, but like I wrote earlier: output is not what I expect. Pool ID 91 has 6 members and
|
If I understand correctly (I'm not a dev), https://polkadot.js.org/docs/substrate/runtime/#pendingrewardsmember-accountid-balance shows that it should be possible to retrieve pendingRewards of a member of a pool. Is that correct? And if so, is it possible to get this information with an API Call on subscan?
The text was updated successfully, but these errors were encountered: