Stakr Protocol — Agent Overview

Stakr Protocol — Agent Overview

This skill gives agents the context to interact with the Stakr protocol: ERC-4626 tokenized vaults with multi-reward staking for any ERC-20 token. Use it when building integrations, scripts, or tooling that create vaults, add rewards, modify reward schedules, or let an agent operate its "own" vault.

Protocol at a Glance

• StakrVault: Single-asset ERC-4626 vault. Users deposit underlying, get shares; they can lock shares to earn multiple reward tokens over configurable windows.
• StakrVaultFactory: Deploys vaults and holds protocol fee configuration. One factory per chain.
• Rewards: Up to 25 reward tokens per vault. Each reward has startTime, endTime, and total amount. Distribution is linear over the window; logic is Masterchef-style (accumulated rewards per share).
• Ownership: A vault can have an owner (address that can add/modify rewards) or address(0) for permissionless reward addition.

When an agent is said to have its "own vault", it means: the agent (or a controlled EOA/contract) is the vault owner, so it can call addRewardToken and modifyRewardToken to fund and adjust rewards without third-party permission.

Emphasis: Adding and Modifying Rewards (Agent-Owned Vaults)

Agents that operate their own vault will use these two functions most:

1. addRewardToken(token, amount, settings)

Purpose: Start a new reward program for a given ERC-20 token.

• Caller: Vault owner (or anyone if owner() == address(0)).
• Parameters:
  • token: ERC-20 reward token address. Cannot be the vault’s share token address(vault).
  • amount: Total amount of token to distribute. Tokens are pulled from msg.sender; protocol may take a fee (see factory feeOnAddReward).
  • settings: Settings{ startTime, endTime }. Distribution is linear from startTime to endTime; both must be in the future and startTime < endTime.
• Effects: Registers the reward, pulls tokens (minus fee) into the vault, and emits AddReward. Rewards cannot be withdrawn once added; they can only be modified (extended or topped up) via modifyRewardToken.
• Limits: No duplicate reward token; vault cannot have more than 25 active rewards.

Use this when the agent wants to create a new reward (e.g. launch an incentive program on its vault).

2. modifyRewardToken(token, amount, settings)

Purpose: Add more amount and/or extend (or reschedule) an existing reward.

• Caller: Same as addRewardToken (vault owner or permissionless if owner is zero).