Earn & Vault Positions
Supply assets to a vault, track your private shares and use its redemption path.
Hold vault shares#
A vault action exchanges an underlying ERC-20 for fixed-unit shares. The Pool measures the shares received and creates a note of that asset. The note records the share quantity; the amount of underlying it can redeem depends on the vault.
Show estimated underlying value separately. Share prices and redemption capacity can change even though the number of shares in the note stays the same.
Supported vault adapters#
The repository has an Aave Stata route, a curated synchronous ERC-4626 path and adapters for specific Morpho and Dolomite venues. Each route identifies its asset pair, contract code and dependencies. A vault needs admission even if it implements ERC-4626.
The fixed-share adapter requires synchronous output and fixed units. It rejects arbitrary calls, rebasing shares, fee-on-transfer tokens and asynchronous withdrawals that cannot return measured tokens before execution ends.
| Position | Held asset | Before redeeming |
|---|---|---|
| Aave Stata or fixed-share vault | Nonrebasing share-token units | Check liquidity, receiver rules and current dependencies |
| Fuyu Earn Flex | fyFLEX vault shares | Check yield fee and share price |
| Fuyu Earn Term | fyTERM shares until withdrawal request | Request withdrawal into the applicable ticket series |
| Pending async redemption | Private fungible tickets | Wait for harvested value or refundable shares under the adapter rules |
Fuyu Earn Flex and Term#
FuyuEarnVault uses its configured venue in two ways. Flex is an ERC-4626 share with a yield fee above its high-water mark. Term receives the configured boost and uses tickets for timed withdrawals. Returns depend on the venue and its accounting rules.
A Term withdrawal burns shares for fixed-value tickets in one of eight weekly series. The documented window starts four to five weeks after the request and lasts three weeks. Missing it means waiting for the next cycle. Check your deployment's timers and backing before requesting a withdrawal.
Supply, redeem or withdraw shares#
The proof covers the supply or redeem route, amount, minimum and private result owner. Use operations admitted by the publisher and backed by a separately reviewed manifest. Quote checks, the proof worker and relay must all use that same route configuration.
An ordinary withdrawal gives the public recipient share tokens. To receive underlying assets, they must redeem those shares with the venue. Removing a Pool redeem route should leave the original share-token exit available.
Before enabling a vault#
Check for venue upgrades, pauses and available liquidity. A preview from an earlier block cannot tell you what can redeem now. Test the full Pool transaction as well as any maxRedeem check.
The integration reports cover test or disposable-fork deployments. A production listing still needs venue review and acceptance on the deployment that will hold the funds.