Vault operations

Operator-bounded, LP-verifiable

Run strategies non-custodially under a mandate LPs can read straight from the chain, enforced by the contract, not by your promise.

The problem

You run other people’s money under explicit mandate. Your entire pitch is non-custodial. If the bounding mechanism is off-chain or vendor-controlled, that pitch is half-true at best, and the smart LPs are starting to ask.

What to look for

What LPs and allocators want

  • Verifiable bound

    Not "we promise we won’t." Not "our compliance won’t let us." The constraint has to be readable by an LP, on the chain.

  • Composability across venues

    Strategies span 5–15 dapps. Anything that locks you into a vendor’s integration timeline bottlenecks your strategy.

  • Multi-step execution that doesn’t half-fail

    Borrow → swap → deposit can’t leave funds stranded between steps. Clean failure beats partial state every time.

  • Time to add a new venue

    From "the team agrees on a venue" to "the first position is open" should be days, not quarters. A new market shouldn't wait on someone else's integration backlog before your strategy can touch it.

What Zodiac does

The mandate is the smart contract

  • Onchain operator roles

    Targets, selectors, parameter ranges, caps: all in bytecode on the same chain the strategy executes on. The mandate IS the contract.

  • Scope to any protocol

    Adding a venue means specifying which of its contracts and methods the operator may call. No vendor integration timeline. If a protocol exists onchain, you can scope to it.

  • Atomic multi-step execution

    Multi-step strategies bundled, sequenced, and simulated. When a precondition fails, nothing executes. Funds stay in a consistent state.

  • Direct LP transparency

    Your bound is public bytecode. We can give LPs a dashboard; or your developers can build one. The source of truth is on the chain.

Case study

OpenAlpha: a Bitcoin strategy its LPs never hand custody to

OpenAlpha runs a systematic strategy that compounds Bitcoin in Bitcoin terms, and never takes custody of a cent.

  • The vault is a Safe the LPs own collectively, governed through Rethink. LPs deposit wBTC, keep custody, and can withdraw at any time.
  • OpenAlpha is a delegated operator on that Safe, scoped by a Zodiac role to exactly the rebalancing actions the strategy needs. It can move exposure around the Bitcoin base onchain; it cannot send the wBTC anywhere but back to the LPs. Every other call reverts.
  • So “non-custodial” isn’t a claim to trust. It’s bytecode. Any allocator can read the operator’s bounds straight from the chain.

Want to walk through your specific operating model?