Policy engine

Decide exactly what can move, and who signs off

Every transfer and operation is evaluated against your policy before anything is signed: hard limits, sanctions and blockchain-analytics risk, then ordered transaction rules by initiator, vault, network, asset, operation, destination, amount and time of day, then approval tiers. Policies are versioned and changes need a second admin.

USDC25,000 USDC · API
1Sanctioned destinationBlock
2USDC > $10,000 via API2 approvals · CFO, owner
3Payouts ≤ $500 to trustedAllow
4Everything else1 approval
Rule 2 matched · waiting for CFO and owner

Controls you can prove

Transaction rules

Ordered rules: the first match allows, blocks, or requires N approvals from named roles such as CFO, compliance or security.

Time windows

Match only during, or only outside, chosen days and hours in your time zone — for example, block every payment outside office hours.

Contract-method rules

Match what a call does, not just where it goes: block setApprovalForAll and permits, require two approvals for token approvals, or allow only known methods on a dApp router.

Velocity limits

Rules that apply once too much has gone out in a window — over $100,000 in 24 hours by one API key, more than 20 transfers an hour from one wallet, or repeated payments to the same address.

Approval groups

Require each group to sign off — 1 from Finance AND 1 from Compliance — by role or named people. A person counts once.

Risk thresholds

Block or require an approval from the destination's risk level, as scored by your Chainalysis, Elliptic or TRM Labs account.

Hard limits

Per-transfer caps, a separate API cap, a rolling 24-hour limit, blocklists and allowlist-only mode.

Address book with cooldown

New destinations wait out a cooldown before they become trusted; untrusted ones need an approval or are refused.

Versioned and governed

Every change is a new immutable version; with two admins, a second one must approve it.

Bound to the request

The policy version is part of each transfer's intent hash: a policy change invalidates pending approvals.

Explained

Every decision lists its reasons, from the matching rule to the address-book status.

Impact before you publish

Replay an edited policy or a new rule on your last 200 requests — velocity windows recomputed — and see every decision it would change, stricter or looser, before anyone approves it.

Policy as code

GET /policy and POST /policy/impact: keep the policy in git, check every change in CI, publish it in the console.

Address poisoning blocked

A new address with the same first and last characters as one you know — address book, your wallets, past payees — is refused or held for approval, and the bait in your history is marked.

Destination types

Rules for your own wallets, network organizations, address-book entries or one-time addresses — internal moves free, one-time addresses under two approvals.

How it works

  1. 1

    Set your limits

    Caps, 24-hour limit and approval tiers in Policies.

  2. 2

    Add rules

    For example: USDC above $10,000 from the API needs 2 approvals from CFO or owner.

  3. 3

    Preview

    Test any transfer with the preview endpoint to see the decision before asking for it.

Preview a decision

const preview = await cv.transfers.preview({
  wallet_id, asset: "USDC", amount: "25000",
  destination: "0x…",
});
// → { decision: { outcome: "require_approval",
//      reasons: ["Rule “Large USDC”: 2 approvals from cfo / owner required."] } }

Works best with

Ready to see Chainvara in action?

Start free on test networks. Move to production when your controls are in place.