- Home
- Skills
- Euler Xyz
- Agent Skills
- Euler Earn
euler-earn_skill
0
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill euler-xyz/agent-skills --skill euler-earn- AGENTS.md18.2 KB
- metadata.json925 B
- SKILL.md2.2 KB
Overview
This skill is a practical guide for building and operating EulerEarn yield aggregation vaults on Euler Finance. It focuses on vault deployment, strategy lifecycle management, role configuration, and using PublicAllocator for permissionless reallocations. Use it to standardize yield optimization, safety checks, and governance flows for meta-vaults.
How this skill works
The skill inspects vault and strategy configuration patterns, role assignments, and allocation queues to ensure correct behavior and security. It outlines the mechanics of supply and withdraw queues, timelocked cap changes, and the PublicAllocator flow caps used for permissionless reallocations. It also recommends monitoring APYs and limits to maintain safe deployment and reallocation.
When to use it
- When creating a new EulerEarn ERC-4626 meta-vault for yield aggregation
- When onboarding, pausing, or removing strategies and setting caps
- When assigning or auditing roles: owner, curator, guardian, allocator
- When configuring PublicAllocator to allow permissionless reallocation
- When preparing timelocked governance changes to caps or fees
- When monitoring strategy APYs or rebalancing allocations
Best practices
- Use clearly separated roles: owner for governance, curator for strategy ops, guardian for emergency actions, allocator for rebalances
- Enforce timelocks for cap increases and high-impact parameter changes
- Set conservative initial strategy caps and increase via timelock after testing
- Prefer PublicAllocator with flow caps for frequent, permissionless rebalances while retaining emergency controls
- Monitor strategy APY and utilization continuously and validate oracle inputs
Example use cases
- Deploy a new ERC-4626 EulerEarn meta-vault and register supply/withdraw queues for multiple strategies
- Onboard a new lending strategy with conservative cap, then schedule a timelocked cap increase after on-chain audits
- Use PublicAllocator to rotate funds between strategies when on-chain signals show changing yields
- Revoke a pending strategy change with the guardian role during suspicious activity
- Configure a curator to submit queued removals and manage day-to-day allocations
FAQ
Supply queue defines the order and targets for depositing new assets into strategies; withdraw queue defines the order to pull funds out to satisfy redemptions or reallocation.
When should I use PublicAllocator?
Use PublicAllocator when you want permissionless reallocation driven by on-chain actors while protecting against large flow changes via configurable flow caps.