Skip to content

docs: FlowYieldVaults v1 Supported Features reference#200

Draft
vishalchangrani wants to merge 2 commits intomainfrom
docs/v1-supported-features
Draft

docs: FlowYieldVaults v1 Supported Features reference#200
vishalchangrani wants to merge 2 commits intomainfrom
docs/v1-supported-features

Conversation

@vishalchangrani
Copy link
Contributor

Summary

  • Adds docs/v1_supported_features.md — a reference doc for the first version of FlowYieldVaults
  • Covers supported strategies, FLOW-only deposits, YieldToken output, 10-min auto-rebalancing, health factors, fees, and closed-beta access control
  • Open items flagged inline for team confirmation before finalization

What's documented

Section Details
Strategies TracerStrategy, mUSDCStrategy, mUSDFStrategy (v1.1), simple ERC4626 strategies
Input token FLOW only
Output token YieldToken
Rebalancing 10 min interval, 0.95/1.05 thresholds, FlowTransactionScheduler
Health factors Target 1.30, min 1.10, liquidation target 1.05
Fees Scheduling (FLOW), insurance reserve (0.1%), dynamic interest
Access Closed-beta via BetaBadge

Open Items to Resolve

  1. Minimum deposit value — is there a floor?
  2. Management / performance fee — does one exist?
  3. Withdrawal fee — confirm none
  4. Any bridged assets accepted as direct deposits in v1?
  5. Confirm 1,000,000 FLOW deposit capacity cap for launch
  6. Which strategies are strictly v1 vs. later releases?

Test plan

  • Review doc values against final deployment / governance config
  • Resolve all open items and mark PR ready for review

Generated with Claude Code

vishalchangrani and others added 2 commits March 8, 2026 20:28
Adds docs/v1_supported_features.md covering: supported strategies
(TracerStrategy, mUSDCStrategy, mUSDFStrategy, simple ERC4626 strategies),
FLOW-only deposit token, YieldToken output, 10-minute auto-rebalancing via
FlowTransactionScheduler, health factors, deposit limits, fee model, and
closed-beta access control. Open items flagged for team review.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant