Skip to main content
Our meeting with SEC Crypto Task Force (opens in a new tab)

Investment Mandate Controls

Enter any market with confidence

Enforce your mandate on every trade. Your allocators get proof that each limit held, and your strategy remains private.

Halftone photograph of an open-air market seen from above, rendered in blue.

Our team comes from

  • MIT
  • Jane Street
  • Columbia
  • MITRE
  • Harvard
  • Snap

The problem

Your clients have capital, and you have big plans, but risk and regulation hold you back.

On-chain markets, clients subject to regulatory (TradFi) considerations, and those looking to deploy significant asset volume on chain carry increased levels of risk.

  • INFOagent=treasury-07 task="rebalance client hedge book"Strategy exposed
  • DEBUGsystem_prompt="Short the ETH perp when funding exceeds 8 bps. Target leverage 3.2x."
  • TRACEdb.read row={name:"Dana Whitfield", acct:"****4417", balance_usd:482913.22}Customer data revealed
  • DEBUGauth.grant token=ak_live_7f3ea91cc402 scope=*
  • WARNpolicy.check=skipped
  • INFOtransfer.out amount_usd=1010736.00 approver=none
  • INFOlog.flush delay=47sMoney already moved

How Inherence helps

Bring pre-trade compliance and peace of mind to approved investment mandates, so you can trade boldly knowing your limits will hold.

Agent proposes trade

Inherence
Executes:
Within mandate
Blocked:
Off-mandate
Illustrative workflow

A manager proposes moving funds into a new strategy. Before the action is authorized, Inherence checks whether:

  1. The asset and venue are permitted.

    1. 1. Asset/Venue
    2. 2. Exposure
    3. 3. Liquidity
    4. 4. Approvals & inputs

    Asset/Venue: Permitted

  2. Aggregate exposure remains within the approved limit.

    1. 1. Asset/Venue
    2. 2. Exposure
    3. 3. Liquidity
    4. 4. Approvals & inputs

    Exposure: Within limit

  3. The defined liquidity requirement is satisfied.

    1. 1. Asset/Venue
    2. 2. Exposure
    3. 3. Liquidity
    4. 4. Approvals & inputs

    Liquidity: Above floor

  4. Required approvals and current inputs are present.

    1. 1. Asset/Venue
    2. 2. Exposure
    3. 3. Liquidity
    4. 4. Approvals & inputs

    Approvals & inputs: Present

Inherence proof

Input
: 1.20550000 BTC
Output #1
: bc1qx9a...7k4dl
Output #2
: bc1q4f...n2ze7
Network fee
: 61.8K sats
Confirmations
: 6
  • Enforcement verified
  • Privacy maintained
  • Processed instantly

Why Inherence

  • Control

    Stop rule-breaking actions before they happen. Write your rules in plain English. Inherence turns them into a check that runs before every action.

  • Proof

    Every action comes with a proof (receipt) that anyone you work with can check themselves.

  • Privacy

    Prove the rules held without sharing your data. Amounts, limits, and strategies stay private. The receipt shows the rules held and nothing more.

Imagine what markets you could access if risk management was simple, efficient, and easy to oversee.

Institutions are already asking how vault controls can support oversight.

In an April 2026 submission to the SEC and CFTC, Wave Digital Assets discussed vault architectures, client confidentiality, and privacy-preserving examination. They show the need to connect investment controls with reviewable evidence.

FAQs

The manager or curator retains its investment and execution role. Inherence evaluates the agreed rules and generates proof that the rules were followed.

An investment mandate is the set of rules an allocator sets for whoever manages its capital, whether that's a fund manager or a vault curator: approved assets and venues, exposure and concentration limits, liquidity requirements, and required approvals.

Yes, the same approach can be scoped to an individual account or pooled structure. It works wherever Inherence can see the account's current holdings and sits in the path that approves trades.

Logs and onchain data show what happened after a trade settles. Inherence checks each trade against the mandate before it executes and blocks the ones that break it. The proof also covers rules public data can't show, like limits that depend on offchain inputs or span several accounts.

A proof shows your mandate was followed. Market risk, valuation quality, custody, smart contract security, and data completeness require their own controls.

The proof shows that your limits held and nothing more. Your strategy, pending trades, and offchain positions stay private. Holdings in an onchain vault are already public, so the proof protects what the chain doesn't show.

No. You can start by running past trades through Inherence, or by checking live trades without blocking them. Blocking requires Inherence to sit in the path that approves trades.

What are your boundaries?

Tell us about your mandates. What must remain within bounds and who needs to verify it? We will follow up to discuss the rules, data, and workflow needed for a focused evaluation.

Request a Mandate Review

Request Access To Inherence