-
Notifications
You must be signed in to change notification settings - Fork 23
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
SignalBuy contract #197
base: v5
Are you sure you want to change the base?
SignalBuy contract #197
Conversation
Overall no particular issues to me. I think the app can test on it first to see whether it fits the need or not. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's ready for them to test. Perhaps can consider remove coordinator first so it's easier to onboard them.
contracts/PionexContract.sol
Outdated
|
||
// Check provided pionexToken/userToken ratio is better than or equal to user's specfied pionexToken/userToken ratio | ||
// -> _params.pionexTokenAmount/_params.userTokenAmount >= _order.pionexTokenAmount/_order.userTokenAmount | ||
require( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the minPionexTokenAmount
should be checked after fee deducted, may be this require can be removed since it'd be reverted if pionexTokenForUser < _settlement.minPionexTokenAmount
even the ratio here is better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. Fixed in ed48d9b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving the merging
orderHashToMakerTokenFilledAmount
toLibOrderStorage