Applications

Where privacy is a requirement, not a feature.

Organizations rarely need to hide that they operate, only what. These are the workflows VEILOPS is designed for, with an honest status for each.

DAO treasuries

experimental
Problem

Every rebalance and runway decision is public in real time.

With VEILOPS

Treasury operations publish a commitment and a proof against the treasury policy; signers hold the envelope.

Still visible

That an operation occurred, its asset, category, time and policy limit.

Contributor payroll

simulated
Problem

On-chain payroll publishes everyone’s compensation.

With VEILOPS

Each payment is sealed for the contributor and finance, and proven to respect the payroll band.

Still visible

Payment count and timing; never individual amounts or (in private modes) recipients.

Vendor payments

experimental
Problem

Supplier relationships and deal sizes leak strategy.

With VEILOPS

Recipient and amount sealed; the policy limits single payments per vendor category.

Still visible

Category, asset, timing, policy.

Grant programs

experimental
Problem

Grantees are exposed before announcements; amounts invite comparisons.

With VEILOPS

Grant disbursements prove they stay within the committee-approved cap.

Still visible

Program policy and disbursement timing.

Audits & compliance

implemented
Problem

Auditors need everything, the public needs nothing.

With VEILOPS

grantAccess() wraps the data key for an auditor; the commitment opening proves the disclosed amount is the one that was proven.

Still visible

Nothing new. Disclosure is off-chain and scoped.

Market makers & funds

planned
Problem

Positions and flows can be front-run.

With VEILOPS

A future integration with confidential transfers would settle amounts privately.

Still visible

Depends on the settlement layer.

01
experimental

Private Treasury

Confidential financial operation workflows for digital treasuries. Rebalances and transfers carry a commitment to the amount and a proof that it respects the treasury policy.

  • — Policy limits per category and asset
  • — Amounts committed, not published
  • — Encrypted operation log for signers
02
experimental

Proof Engine

Generate and verify cryptographic proofs. Today: veilops-range-v1, a bit-decomposition range proof on Pedersen commitments over ristretto255, made non-interactive with Fiat–Shamir.

  • — Proves 0 ≤ amount ≤ limit
  • — No trusted setup
  • — Verifies in the browser in well under a second
03
simulated

Private Payroll

Support confidential contributor payment workflows. Batch payouts where each line item is sealed for the contributor and finance, and proven against the payroll policy.

  • — Per-recipient envelopes
  • — Compensation never in public records
  • — Batch workflow is simulated today
04
implemented

Selective Disclosure

Reveal specific information only to authorized parties. A data key is wrapped per viewer (X25519 + HKDF). An auditor can open the envelope and check the commitment opening.

  • — Grant access without re-encrypting
  • — Commitment opening proves the disclosed amount
  • — Keys never leave the browser
05
implemented

Public Proof Explorer

Allow independent verification of permitted public proof records. Every record can be re-verified from scratch in your browser. The dataset is sample data today.

  • — Search by operation or proof id
  • — Re-verify any record locally
  • — Tampered samples fail, by design