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
Shown in the video. Another thing to note is that balances are not the same in Courts than in Dashboard/MyCourts. Probably because of different hooks giving different balances. Maybe thats the cause of this issue? in my experience the one I used at Dashboard/MyCourts seems to give accurate user balance results (One thing to note is that the query from Courts is a contract call, while the one on Dashboard/MyCourts is a subgraph query)
2023-11-07.18-12-15.mp4
Update: I unstaked everything from all courts via frontend, balance is 0 on Courts, but balance is still existing on Dashboard/MyCourts
2023-11-08.09-51-51.mp4
In the subgraph, this is the only handler modifying the court.stake field:
Shown in the video. Another thing to note is that balances are not the same in
Courts
than inDashboard/MyCourts
. Probably because of different hooks giving different balances. Maybe thats the cause of this issue? in my experience the one I used atDashboard/MyCourts
seems to give accurate user balance results (One thing to note is that the query fromCourts
is acontract call
, while the one onDashboard/MyCourts
is asubgraph query
)2023-11-07.18-12-15.mp4
Update: I unstaked everything from all courts via frontend, balance is 0 on
Courts
, but balance is still existing onDashboard/MyCourts
2023-11-08.09-51-51.mp4
In the subgraph, this is the only handler modifying the
court.stake
field:The text was updated successfully, but these errors were encountered: