-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate and confirm the behaviour for new staking users for uad-contracts and diamond #939
Comments
I extracted this to a separate issue, will post finding for both |
I'm assuming its because I moved collateral out of the contract which I know affects the withdrawal amounts. |
# Issue was not closed as completed. Skipping. |
Do we plan to move it back to the staking contract? |
Yeah I think we need to migrate to v2 somehow. It was mostly removed because of some problem discovered in Sherlock if I recall correctly. |
Staking contracts weren't part of the Sherlock audit. |
Then I don't remember why some was moved |
Then perhaps we should reopen this issue? |
It isn't clear to me if we redid the staking yet and if we should migrate? If so perhaps we should make a new issue instead. |
What we have right now:
The only issue with the MasterChefV2.1 contract (old staking) is current github issue with missing That is why we'd better to find out the root cause of missing LP tokens and then decide whether we should proceed with the old staking or migrate to the diamond's |
Right now the behaviour for new staking users is this one:
UAD3CRV LP
to https://etherscan.io/address/0xc251ecd9f1bd5230823f9a0f99a44a87ddd4ca38 for 1 weekUAD3CRV LP
and gets 178UAD3CRV LP
+ 72UBQ
. User would expect to get 1000UAD3CRV LP
instead of 178.Originally posted by @rndquu in #752 (comment)
The text was updated successfully, but these errors were encountered: