HoodYield documentation
Architecture, automation, security model, and production risks.
How it works
Automated yield routing with transparent, shared-vault guardrails.
HoodYield separates user accounting from strategy execution. Users hold standard ERC-4626 shares; keepers automate approved operations; governance controls the strategy universe through a timelock; and a limited guardian handles emergencies.
Deposit lifecycle
Step 1
Choose a risk vault
Low, Medium, and High ERC-4626 vaults isolate accounting, strategy exposure, and automation frequency.
Step 2
Approve and deposit
Approve the vault's verified underlying asset, then receive transferable shares representing your proportional claim.
Step 3
Harvest and compound
A rate-limited keeper realizes strategy rewards. Net profit remains in the vault and increases the asset value of every share.
Step 4
Guarded rebalance
The keeper can route a shared vault only to governance-allowlisted, asset-compatible strategies with bounded loss checks.
Vault policies
Policies below are read from deployed vaults and the production data provider. No static financial values are used.
| Vault / Asset | Protocol | APY | TVL | Risk score | Your balance |
|---|
Security model
Timelocked governance
Strategy approvals, keeper changes, and configuration updates wait through the governance delay.
Emergency guardian
A dedicated guardian can pause immediately and evacuate a strategy, but cannot resume operations.
On-chain guardrails
Reentrancy protection, pausing, strategy allowlists, asset checks, minimum harvest return, and rebalance loss limits.
Risk disclaimer
HoodYield is non-custodial software, not a bank, broker, investment adviser, or guarantee of returns. APY is variable and historical performance does not predict future results.
Users may lose some or all deposited assets due to smart-contract defects, strategy failure, oracle manipulation, depegging, bridge risk, liquidity constraints, Stock Token issuer risk, governance actions, or Robinhood Chain/network disruption. Risk scores are relative product labels—not audits or credit ratings.
Contracts must complete independent audit, testnet soak testing, verified-source deployment, multisig configuration, and production oracle/strategy integration before accepting mainnet deposits.
Historical replay →
Compare risk policies against a passive benchmark.
Automation policies →
Understand shared-vault keeper schedules and controls.