Security notes
Security gates before mainnet custody
The Hedgehog dapp is live as a hosted product demo. It does not custody user funds. Mainnet deposits remain gated until the on-chain vault, keeper permissions, failure-mode tests, and audit package are ready.
Current status
The live vault interface connects to a Solana wallet and uses live market inputs to model an automated delta-neutral SOL carry position. In hosted demo mode, creating a position updates strategy accounting and health data, but it does not transfer SOL into a production vault.
This is intentional. It lets users, judges, and early followers test the full experience while the mainnet custody layer is built with tighter security assumptions.
Mainnet release gates
- Vault program. Deterministic deposits, share accounting, withdrawals, fee accounting, and emergency controls need to live in an auditable on-chain program.
- Keeper scope. Automation should only execute allowlisted instructions inside explicit hedge, leverage, price, and unwind limits.
- Integration tests. The strategy needs repeatable tests for stale oracle data, funding flips, borrow spikes, thin buffers, failed swaps, failed perps, and withdrawal pressure.
- External review. Production custody should wait for an independent review of the program, permissions, deployment process, and monitoring assumptions.
Custody model
A production Hedgehog vault should avoid broad off-chain custody. User funds should be controlled by a vault program that enforces what can be deposited, where assets can move, how shares are minted and burned, and when withdrawals or emergency exits are available.
The keeper should not have arbitrary transfer authority. Its role is to maintain the strategy inside predefined constraints, not to own user assets.
Keeper permissions
The keeper is powerful because it can rebalance a multi-leg position. That power must be narrow. The intended design is allowlisted protocol calls, maximum notional changes, hedge-band checks, oracle freshness requirements, leverage caps, and circuit breakers for negative funding or margin pressure.
Any keeper action should be reproducible from public state: current vault balances, current oracle prices, current hedge notional, configured thresholds, and the resulting health score.
Failure modes being tested
Delta-neutral strategies can still lose money. The main risks are hedge drift, stale or manipulated prices, liquidation during volatility, negative funding, rising borrow costs, low liquidity, protocol bugs, failed rebalances, and delayed withdrawals.
Hedgehog's risk engine is designed to make those risks visible through buffer percentage, net delta, estimated APY, keeper age, active position status, and unwind thresholds.
Audit path
The audit path starts with a complete on-chain vault and a focused threat model. From there, the project needs unit tests, integration tests, deployment scripts, role documentation, and explicit invariants for deposits, withdrawals, share accounting, keeper permissions, and emergency controls.
An external audit should review the contracts and the operational model together, because the security of a strategy vault depends on code, permissions, monitoring, and incident response.
User protection principle
Hedgehog should earn user trust by staying honest about status. The product demo can be live today, but mainnet custody should only launch when the system is tested, constrained, reviewed, and easy for users to understand.