Offchain boost limit being hit by onchain boost
Summary
It appears as if the offchain transaction limit being hit by onchain transactions https://www.minds.com/media/1035531217399209984?focusedCommentUrn=urn:comment:1035531217399209984:0:0:0:1035949153481478144
The user also reports having lost tokens after accepting the tx when Metamask showed a small error.
Steps to reproduce
(How one can reproduce the issue - this is very important)
Platform information
Firefox, Windows 10.
What is the current bug behavior?
User is shown error, tokens are taken.
What is the expected correct behavior?
User should not be seeing that error.
Relevant logs and/or screenshots
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
added scoped labels
changed the description
added scoped label and automatically removed label
- Developer
Reported also by @ottman
- Developer
Note: Bill said he was on Walrus.
changed time estimate to 4h
- Developer
- Had a look at the code.
- Tested multiple times on different browsers. (Brave, Chromium, Firefox)
Todo
- Try to spec test it out.
- @javanick let me know if you see anything relating in.
added 30m of time spent at 2019-11-07
added scoped label and automatically removed label
- Developer
Downgrading to normal, I'm only seeing a singular report of this.
- Developer
Asking user for additional details.
added scoped label
added scoped label
removed label
- Developer
@benhayward.ben I would try spending a 1 off chain token on a boost to trigger the limit check and then try the five on chain tokens. The combination of off chain and on chain transactions might be what's causing the error.
changed title from Offchain to Offchain
changed the description
- Developer
Had already done that, but ran again locally.
I spend 10 offchain tokens to hit the limit
Metamask still works
I expect given that and given its re-occurrence that it may be a state-changing error in the boost modal. Just awaiting a report where I can chat with the user to try to narrow down what circumstances are causing that state error.
- Developer
Note, that error above is not the error that the user sees on the modal, this one is MetaMask complaining because it's on Rinkeby and I'm using a Mainnet wallet.