Quant review
How the Perps.fun quant team reviews Individuals proposals before deploying the vault.
Every proposal submitted on
app.perps.fun/propose is reviewed by
the Perps.fun quant team before a vault is deployed. The launchpad is
permissionless to apply to but permissioned to launch from; the quality
bar at review is what backers and traders rely on.
Outcomes
| Outcome | Effect |
|---|---|
| Approve | The vault deploys and bonding opens. Status moves to bonding. |
| Revise | Reviewer requests changes through the proposer's contact channel. Proposer revises and resubmits. |
| Veto | Declined with rationale. Status moves to vetoed. The proposer can submit a new proposal addressing the issues. |
What reviewers check
- Oracle robustness. The chosen feed covers the asset's full trading hours and can sustain HIP-3's 3-second update cadence. Off-hours behaviour is defined.
- Leverage and margin. Maximum leverage is sized to the underlying's typical intraday range. Funding rate multiplier reflects the underlying's typical carry.
- OI cap sizing. The cap is sized against the underlying's order-book depth and venue concentration.
- Market thesis. The proposal answers clear demand for hedging or speculation, with reference to comparable markets where they exist.
Working with reviewers
Reviewers contact the proposer through the profile contact methods
(email, X/Twitter, Telegram). Inline feedback is captured against the
proposal. The proposer revises directly on /propose and resubmits.
Common veto rationales: thin liquidity on the underlying, an oracle source that cannot sustain the 3-second cadence, or a leverage and margin configuration that creates avoidable liquidation risk.
After approval
On approval, Perps.fun deploys the vault and the vault page becomes visible on app.perps.fun. See Vault.