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
micahalcorn opened this issue
May 4, 2023
· 3 comments
Labels
bugSomething isn't workingdappRelating to OUSD.comfrontendWorks related to frontendOETHOETH related thingsP1Large amount of significant user impact, a meaningful feature is brokenui/uxWorkd that requires design and product overview
I'm connected to the dapp with a Safe wallet via iOS and WalletConnect. When I open my account history, I see yield even though I have not opted-in. Both our dapp and Etherscan agree that my balance has not increased.
The text was updated successfully, but these errors were encountered:
micahalcorn
added
bug
Something isn't working
P1
Large amount of significant user impact, a meaningful feature is broken
dapp
Relating to OUSD.com
ui/ux
Workd that requires design and product overview
OETH
OETH related things
labels
May 4, 2023
The cause of this issue that we assume in the backend that a user/contract is opted in from the beginning so we just return all yield events.
However, I'm not sure how to solve this since rebaseOptIns and rebaseOptOuts don't emit an event and thus, aren't indexed. But the frontend is doing its job properly so I would say we should move this be an analytics issue as opposed to dapp one.
One additional thing, this is also an issue on the ousd dapp.
bugSomething isn't workingdappRelating to OUSD.comfrontendWorks related to frontendOETHOETH related thingsP1Large amount of significant user impact, a meaningful feature is brokenui/uxWorkd that requires design and product overview
I'm connected to the dapp with a Safe wallet via iOS and WalletConnect. When I open my account history, I see yield even though I have not opted-in. Both our dapp and Etherscan agree that my balance has not increased.
https://www.loom.com/share/293b59d5f321478f8db5cccd5964a5d0
This video also depicts #1404.
The text was updated successfully, but these errors were encountered: