Closed sepu85 closed 2 years ago
@sepu85 i think tthis is a mistake and the button should say withdraw next to each protocol at the first section there's a claim button only for rewards
i think this is a mistake and the button should say withdraw next to each protocol
I agree, in portfolio section, all rows (staking positions) should have a button saying Withdraw
rather than Claim reward
Claim Reward
to Withdraw
at the first section there's a claim button only for rewards
now I understand, nice. So that's a button that claim ALL rewards from ALL positions?? I believe we should have a dedicated Claim Rewards
button per each staking position, but this is a new feature we could add to the backlog (let's talk this before opening a new issue, then).
in issue #42 I stated the following for the G$s reward, now I'm realizing the statement is wrong:
- G$ rewards
How much value your stake has accumulated so far
now, I'm not sure what's supposed to be there, could you @sirpy check configurations and tell me what exactly means that variable? then we ping @adaptivecodeio to update that issue.
I'm guessing those are yearly rewards, but would like you to confirm it before re-opening that issue.
in the portfolio page at the top it shows your "all accumulated (claimed+unclaimed) rewards from all contracts" in the middle it shows you "claimable rewards" per position it shows the "all accumulated rewards(claimd+unclaimed) from this contract"
Yes we need to reconsider the claim rewards buttons, that was a decision Tomer took.
@YpetrovAJ Here the user need to have two buttons next to his stake position "Withdraw" and "Claim Rewards" Needs a layout from the designer
Bug Description It is currently not possible to Claim Rewards without withdrawing liquidity from staking pool, also UX is not clear about gow many G$s are for the staker to claim his rewards.
Steps to Reproduce
Expected Behavior User CAN choose to Claim G$ Rewards without withdrawing his whole liquidity.
Additional Context Add any other context about the problem here (screenshots, whether the bug only occurs only in certain mobile/desktop/browser environments, etc.)