Describe the bug
This bug was a headache but after hours of investigation, I finally have an explanation.
After claiming rewards and the Metamask transaction goes through, pSTAKE will automatically claim rewards without pressing anything. This usually happens in a 6-8 minutes timeframe. Performing a "claim rewards" transaction in this timeframe, messes up the entire application and results in lost funds (tokens under "unclaimed rewards" disappear). This may also result in a pending transaction on Metamask.
Here are my addresses, it could help to verify the transactions:
cosmos1z94pp438alwffxjeylsczpuatyym83fjpvse2u
0x6c2b8F1C4BB1501049455f1d488ADe6b42Ea2adF
NOTE: This only started happening after I have made 1900 transactions over 4 days.
To Reproduce
Steps to reproduce the behaviour:
Go to pSTAKE application
Wrap some ATOM tokens
Stake some tokens
Wait a few minutes to generate pATOMs under "unclaimed rewards"
Press "Claim Now!" and proceed with the transaction
After the transaction goes through, wait for 6-8 minutes
pATOM tokens under "unclaimed rewards" will automatically be claimed
Expected behaviour
Rewards shouldn't be claimed without the user's desire.
Desktop (please complete the following information):
Describe the bug This bug was a headache but after hours of investigation, I finally have an explanation.
After claiming rewards and the Metamask transaction goes through, pSTAKE will automatically claim rewards without pressing anything. This usually happens in a 6-8 minutes timeframe. Performing a "claim rewards" transaction in this timeframe, messes up the entire application and results in lost funds (tokens under "unclaimed rewards" disappear). This may also result in a pending transaction on Metamask.
Here are my addresses, it could help to verify the transactions:
NOTE: This only started happening after I have made 1900 transactions over 4 days.
To Reproduce Steps to reproduce the behaviour:
Expected behaviour Rewards shouldn't be claimed without the user's desire.
Desktop (please complete the following information):
Ethereum address 0x3f3eb8aad1b3c4a8184f82dc0e471b5641c6bfdc
Criticality Assessment Please pick one:
Checklist