We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Having a single "spender" and "to" for a vector of requests is too restricting.
For each action, the user acted against should be able to be specified.
For actions where tokens are being input into the protocol, the "user" would be the spender, and would need to authorize the transactions.
For actions where tokens are being sent out of the protocol, the "user" would be to, and would not need to authorize the transactions.
This might cause some confusion when designing the Request object for use with filling liquidations.
Request
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Having a single "spender" and "to" for a vector of requests is too restricting.
For each action, the user acted against should be able to be specified.
For actions where tokens are being input into the protocol, the "user" would be the spender, and would need to authorize the transactions.
For actions where tokens are being sent out of the protocol, the "user" would be to, and would not need to authorize the transactions.
Technical Notes
This might cause some confusion when designing the
Request
object for use with filling liquidations.The text was updated successfully, but these errors were encountered: