We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I run this to check my actual accounts and I see I have no vesting balances (which is expected).
query partyAccounts { partiesConnection(id:"b62eafc46e6fadc6e45ae51de8bda199f0702131e5b23665f3411223c598acc2"){ edges{ node{ id accountsConnection{ edges{ node{ balance asset{ id symbol decimals } type } } } } } } }
However if I run this I see that supposedly I have about 5.8 VEGA still vesting .... and for some reason this hasnt been updated since epoch 982.
query vestingDetails { party(id: "b62eafc46e6fadc6e45ae51de8bda199f0702131e5b23665f3411223c598acc2") { vestingStats{ rewardBonusMultiplier quantumBalance epochSeq } vestingBalancesSummary{ epoch vestingBalances{ asset { id symbol quantum decimals } balance } lockedBalances { asset { id symbol quantum decimals } balance untilEpoch } } } }
As above
The vestingBalancesSummary API should accurately reflect the accounts API.
1. Submit `xyz` transaction 2. With this payload 3. Query `abc` API 4. Observe the error
0.77.10
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem encountered
I run this to check my actual accounts and I see I have no vesting balances (which is expected).
However if I run this I see that supposedly I have about 5.8 VEGA still vesting .... and for some reason this hasnt been updated since epoch 982.
Observed behaviour
As above
Expected behaviour
The vestingBalancesSummary API should accurately reflect the accounts API.
Steps to reproduce
Software version
0.77.10
Failing test
No response
Jenkins run
No response
Configuration used
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: