Description I have experienced an issue with the voter wherein claiming rewards submits a transaction that results in no UMA being sent, despite correctly voting. On a second transaction, rewards are correctly claimed. After investigating this issue it turns out that I am not the only one to experience it. @claytonroche has reported the same issue as well as a few people in Discord saying that they needed to send two transactions to claim rewards. Reproduction This issue has only occurred once for me and I have not been able to re-create it. The flow was as follows:
Expected Behavior The first transaction should not be sent. The dapp should never enable the user to send a tx that does not claim any rewards. Additional Context I have de-coded the transaction data for my claim rewards function call. The redacted object is shown below: Decoding @claytonroche's transaction data of the same error yields different output, with his claim rewards call being sent against the first identifier ( These identifiers translate to Therefore it appears that the voter dapp incorrectly tried to claim rewards for past round that had already had rewards claimed. |
Click here to view original web page at github.com