Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Override metadata on supported vaults to enable USDC zaps on Fantom.
Related Issue
yearn/yearn-sdk#297
Motivation and Context
Remove friction for deposits into Yearn vaults. This is
Step 1
of the Yearn <> Wido Router integration proposal to enable frictionless deposits into all Yearn vaults, regardless of the chain the user is depositing from.This is just a draft PR to kick off the discussion.
Zaps have been pretty successful on Ethereum, contributing to almost 50% of all deposits (see chart below).
Note on the chart: It's filtered down to curve vaults with at least one
zapIn
function call each month to skip vaults with no support for zaps. Source.How Has This Been Tested?
It was tested locally with the frontend running the yalc'ed SDK.
Left ToDo
zapperZapIn
commitExample txs:
https://ftmscan.com/tx/0x4bcd9791a24307bc7760f543ce2d3f15201d578aff5460976d759288f80b834a
https://ftmscan.com/tx/0xc8d1c86e90dda1a1487672cda5dba0005646ba0ad6b4057408526586aae963c6
Screenshots:
The following 4 screenshots show how
zapIn
into a Fantom vault looks