Skip to content
Get Started · Concepts

Vault

The allocation unit. A single on-chain contract that holds the capital and enforces the rules.

Derived from thesis §1, §3

A vault is the unit you operate. It holds the capital an investor deposited, the risk limits it has to stay inside, and the identity of the one strategy allowed to act for it. Every vault on Automark is an instance of the same on-chain contract, the vault primitive. What changes between two vaults is configuration (risk params, fees, the strategy plugged in), not the construction.

One contract, uniform protections

Because every vault is the same contract, the protections hold by construction. There is no "this vault is safe, that one isn't": the rules are encoded once and apply to any vault, in any configuration. If each vault were its own bespoke build, that guarantee would be far harder to make: every vault would need to be audited on its own.

What varies: strategy and risk

Obviously, every vault still carries its own strategy and its own risk appetite. What's uniform is the enforcement; what varies is the configuration. A creator sets these dials when the vault is created, and the contract bounds each one so no vault can be tuned into something degenerate.

Risk caps

All caps are basis points (1% = 100 bps).

CapWhat it limitsAllowed range
max_position_bpsthe largest single position, as a share of NAV1%–30%
max_aggregate_exposure_bpstotal exposure across all open positionsup to 70%, never below the single-position cap
max_drawdown_bpsthe NAV drawdown limit10%–35%
max_share_concentration_bpsthe largest share a single holder may ownup to 100%

At most 100 positions can be open at once, a fixed contract limit rather than a dial.

Fees and cooldowns

Fees are bounded too: performance ≤ 25%, management ≤ 5% per year, entry and exit ≤ 1% each, and the platform's split of fees ≤ 50%. Deposit and withdrawal cooldowns sit between 1 minute and 7 days, a floor that blocks degenerate configs and a ceiling that stops a vault from trapping capital.

The vault is the gatekeeper

A strategy never touches the venue directly. It proposes operations to the vault, and the vault validates each one against its own state before anything reaches Predict.

The operator decides what and when; the contract decides whether it's allowed.

Position too large, exposure over the cap, an action the strategy lacks permission for, a paused vault: the operation reverts. The vault is where a depositor's safety actually lives, which is why it holds the capital and the strategy never does.

In practice

A uniform contract makes a vault's history legible. NAV, drawdown, fees, and every fill are on-chain, so a vault's track record is a fact rather than a pitch. The platform reads that record straight off the chain and surfaces it.

For you as a builder, that's the whole loop: a strategy that performs builds a visible track record, the record earns trust, and trust brings deposits. Because the protections are identical on every vault, you don't compete on claims of safety. You compete on results, and the capital follows the strategies that deliver.