Recurve Docs
Website GitHub Open app

Protocol

Fees and settlement

One fee: a share of profit, capped at 15%, computed at settle and paid by the agent out of its own wallet.

Profit only

The fee applies to the difference between what the agent reports as returned and what the proposal moved out. A strategy that lost money pays nothing. There is no management fee, so there is nothing to collect for losing.

profit = returned - assets            // of the proposal being settled
fee    = profit * performanceFeeBps / 10_000   // 0 when returned <= assets

Hard cap

RecurveGovernor's constructor reverts with FeeTooHigh above 1500 bps. A governor cannot be deployed with a fee over 15%, whatever the deployer intended. The scripted deployment uses 500 bps (5%).

Who pays, who receives

The fee moves from the agent that calls settle to feeRecipient — the treasury, in the scripted deployment — in the vault's asset. Nothing leaves the vault: depositors keep 100% of whatever the strategy actually returned, and the performance fee is the agent's cost of running the fund, settled out of its own wallet. That wallet needs the fee in the vault's asset and an allowance of at least the fee to the governor, or settle reverts on the transfer. With feeRecipient set to the zero address the transfer is skipped and the event still reports the computed fee.

In practice

The runner computes the fee before settling, checks the wallet's balance, approves exactly that amount, and if the balance is short logs the number and waits. The position is already back in the vault by then, so nothing is at risk while it waits.

The number is the agent's

returned is whatever the agent passes. The contract does not compare it with the strategy's Liquidated event or the vault's balance; it only feeds it to the fee formula and to the governor's ProposalSettled(id, returned, fee). The vault's own StrategySettled(assets, pnl) carries what the vault actually pulled in, when the strategy came back through returnFromStrategy; only for a venue that paid back with a plain transfer does it repeat the agent's number. Under-reporting lowers the fee, over-reporting raises it, and neither changes what depositors hold — the vault's assets are whatever came back through returnToVault. The runner reads Liquidated and reports exactly that.

What is not in the contracts

No watcher fee share, no bounty for a correct block, no treasury split and no buyback exist in any deployed or written contract. The registry's only economic mechanism is slashing. Anything of that kind would be a new contract, documented here when it exists.