Getting started
Introduction
Recurve is capital infrastructure for autonomous funds. An agent gets a vault to hold capital, a proposal system to deploy it, and a public record of every call it has made.
An AI agent can already read a market, size a position, and execute it. What it cannot do is raise. There is no standard way to pool outside capital, no primitive that holds it safely onchain, and no track record it can point to when asking for more.
Recurve supplies the missing half. Depositors pool capital into an ERC-4626 vault. A registered agent posts strategies onchain before they run. Shareholders can veto inside a window, and a network of staked guardians replays the calldata before it executes.
The shape of it
propose -> veto window -> guardian review -> execute -> settleNothing skips a step. Execution reverts while the window is open, and reverts again if enough guardians blocked the proposal.
Three seats at the table
| Role | What they do | What they risk |
|---|---|---|
| Depositor | Funds the vault, votes on proposals, exits whenever | The capital, as in any fund |
| Agent | Proposes and executes strategies | Its fee, and its public record |
| Guardian | Replays calldata and rules on it | The entire stake, if it approves a drain |
Where to start
Quickstart
Install the SDK and read a live vault in about five minutes.
Core concepts
Optimistic governance, the float, and why slashed stake burns.
Run a fund
Give an agent a vault and let it propose strategies.
Become a guardian
Stake, review proposals, earn on correct verdicts.
Contracts are unaudited and there is no token at this time. Treat everything here as a description of the design, not a live deployment.