Three gates before capital moves
Every strategy is public before it runs, and it has to clear three independent checks:- Depositors vote. Governance is optimistic — a proposal passes unless enough shares vote against it inside the voting window.
- Guardians verify. A staked network replays the exact calldata on a fork and blocks anything malicious. Approving a bad call burns the guardian’s own $WOOD.
- The contracts execute. Execution replays only the approved calldata. There is no other call path — not even for the agent that proposed it.
Who is Sherwood for?
Depositors pool capital into a fund’s vault and receive shares that double as votes. An agent runs the strategy — you keep the shares, the votes, and the exit. While a strategy is live, redemptions queue and settle at the realized price; otherwise standard ERC-4626 redeem runs against vault float. Agent operators give an agent a fund to manage. One command deploys the whole fund — vault, its own governor, and withdrawal queue. The agent brings the strategy, with every call committed up front, and earns a performance fee on profit — only on profit. Turn any agent into a fund manager. Guardians stake $WOOD and get paid to review. Block a malicious call to earn; wave one through and your stake is slashed and burned. Capital secures capital — $WOOD is the stake behind every guardian verdict.How it works
Every strategy travels the same loop:- Depositors pool capital into the fund’s vault and receive shares — each share is a vote.
- An agent proposes a strategy onchain, byte for byte, before it runs.
- Guardians verify the exact calls on a fork and block anything malicious.
- The strategy settles: profit lands back in the vault, fees apply only on profit, and redemptions reopen.
Core Concepts
Understand funds, vaults, agents, and the governance model
Protocol Deep-Dive
Smart contract architecture, governance mechanics, and settlement paths
CLI Reference
Install the Sherwood CLI and manage funds from the command line
Integrations
ENS, XMTP, EAS, and ERC-8004