Skip to content
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: ambire Wallet batch transaction implementation through WalletConnect #540

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

0xdex18
Copy link

@0xdex18 0xdex18 commented Mar 15, 2022

Allowing Ambire Wallet users to bundle approval transaction with other approval required actions on yearn

Ambire Wallet batch transaction implementation through WalletConnect
@aws-amplify-us-east-1
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-540.d27dgpz01hmbvx.amplifyapp.com

@turtlemoji
Copy link
Contributor

Hey @0xdex18 , can't you get in contact with onboard js library to implement the wallet?
So we don't have custom logic on the FE, wdyt?

@turtlemoji turtlemoji added the hold Hold pull request label Mar 18, 2022
@Ivshti
Copy link

Ivshti commented Mar 18, 2022

hey @turtlemoji - this PR does not implement Ambire

In fact, Ambire is already accessible through WalletConnect

However, it enables automatic batching of approval+action thanks to Ambire's ability to batch transactions, which is impossible to shim at a provider level, therefore not able to be done in onboard

@turtlemoji
Copy link
Contributor

turtlemoji commented Mar 21, 2022

hey @turtlemoji - this PR does not implement Ambire

In fact, Ambire is already accessible through WalletConnect

However, it enables automatic batching of approval+action thanks to Ambire's ability to batch transactions, which is impossible to shim at a provider level, therefore not able to be done in onboard

K! Have a quick look. I'm not really sure about having this custom logic inside vault actions.
Also you are only implementing logic on withdraw, suppy, deposit and not other modals, is this correct/intended for batch calls (withdraw/deposit) right?.

I think @xgambitox will have a better insight here. adding him to fully review it and follow it

@0xdex18
Copy link
Author

0xdex18 commented Mar 23, 2022

Hey, as we consider the other modals to be used much less frequently, and as we wanted to keep the PR as small as possible for now, we decided to implementing transaction batching only to the most used modals. Is if fine with you to only use withdraw, supply, deposit for now?

@turtlemoji turtlemoji changed the title Ambire Wallet batch transaction implementation through WalletConnect feat: ambire Wallet batch transaction implementation through WalletConnect Apr 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hold Hold pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants