-
Notifications
You must be signed in to change notification settings - Fork 33
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
feat: adding a receiver as parameter in the accept swap function #119
Comments
Hey @0xneves I wanna work on this |
Hey @blackbeard002 I was waiting your PR 🙈 |
This task is not hard, come on guys |
2 tasks
HEY HEY GUYS I saw that this issue is stopped a while and I did it guys :) PR with all documentation about: #149 |
0xjoaovpsantos
added a commit
to 0xjoaovpsantos/swaplace-contracts
that referenced
this issue
Jan 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is no reason why not allowing to choose the receiver when calling acceptSwap, which is currently setting msg.sender as the receiver of the assets.
Proposal:
The text was updated successfully, but these errors were encountered: