You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature would allow users when depositing/donating and withdrawing to instantly swap assets within the same GIVsavings UX
The flow could be like this
Depositing: User can see a list of eligible tokens on the drop down menu, they can deposit this token directly into a GIVsavings account. The token is auto-converted into the right asset and deposited into the account
Withdrawing: User can see a list of eligible tokens on the drop down menu, they can withdraw from their vault and receive the selected token instead of the base asset. The base asset is withdraw, auto-converted and sent to the withdrawer
We'll need to do more research on this feature. Currently Yearn has developed their own version of it but it is error prone and limited in assets eligible.
Here's a demo of how it works on the yearn side:
YearnZap.mp4
This feature may be too complex and we might need to make it a post MVP addition
The text was updated successfully, but these errors were encountered:
This feature would allow users when depositing/donating and withdrawing to instantly swap assets within the same GIVsavings UX
The flow could be like this
Depositing: User can see a list of eligible tokens on the drop down menu, they can deposit this token directly into a GIVsavings account. The token is auto-converted into the right asset and deposited into the account
Withdrawing: User can see a list of eligible tokens on the drop down menu, they can withdraw from their vault and receive the selected token instead of the base asset. The base asset is withdraw, auto-converted and sent to the withdrawer
We'll need to do more research on this feature. Currently Yearn has developed their own version of it but it is error prone and limited in assets eligible.
Here's a demo of how it works on the yearn side:
YearnZap.mp4
This feature may be too complex and we might need to make it a post MVP addition
The text was updated successfully, but these errors were encountered: