frontend-monorepo
frontend-monorepo copied to clipboard
Vesting rewards and game details not showing
Vesting Rewards
I earned some rewards on testnet .... you can see at the bottom here I earned 155 for taker fees.
10 of those have vested right away
But there are 0 in the vesting balance on screen.
But if I query for accounts:
query partyAccounts {
partiesConnection(id:"3fc24730cad7d22f27244d1c8959135dc71becbfcbf86ac0a3a76622300f86c9"){
edges{
node{
id
accountsConnection{
edges{
node{
balance
asset{
id
symbol
decimals
}
type
}
}
}
}
}
}
}
I should have 145 in there:
"node": {
"balance": "145000000",
"asset": {
"id": "8ba0b10971f0c4747746cd01ff05a53ae75ca91eba1d4d050b527910c983e27e",
"symbol": "USDT",
"decimals": 6
},
"type": "ACCOUNT_TYPE_VESTING_REWARDS"
}
},
Its on the vesting API too ... so I dont know whats up ... whichever way we should be sourcing it ... it shoud be there.
query vestingDetails {
party(id: "3fc24730cad7d22f27244d1c8959135dc71becbfcbf86ac0a3a76622300f86c9") {
vestingStats{
rewardBonusMultiplier
quantumBalance
epochSeq
}
vestingBalancesSummary {
epoch
vestingBalances {
asset {
id
symbol
quantum
decimals
}
balance
}
lockedBalances {
asset {
id
symbol
quantum
decimals
}
balance
untilEpoch
}
}
}
}
Game Details
They are blank!
Even though there are results ... I fear the recent rework of the query might have done something?
This returns results
query gameDetails {
games(epochFrom:13637){
edges{
node{
id
rewardAssetId
epoch
numberOfParticipants
entities{
...on TeamGameEntity{
team{
teamId
}
rank
volume
rewardMetric
rewardEarned
rewardEarnedQuantum
totalRewardsEarned
totalRewardsEarnedQuantum
}
}
}
}
}
}
Additional details / background info
Seeing locked, vesting, and vested rewards fine in mainnet now
I am concerned the Core APIs are not right ... but that isnt our problem
https://github.com/vegaprotocol/vega/issues/11066
Leaving this open until that Core ticket is fixed so I can double check this
I cant easily confirm this in testnet or mainnet at this point.
When Core made the changes I reviewed and tested those at the time and couldnt find any issues.
I think we need to trust this got resolved.