Finance OS

Project introduction

The CFO layer for Web3 teams

Finance OS is an autonomous payroll and compliance engine for Web3 teams. It is designed around one Base treasury, four Chainlink CRE workflows, private AML screening, cross-chain settlement through CCIP, and on-chain audit proof.

Open dashboardRead guide

Mode

Single treasury / multi-chain payout

Primary chain

Sepolia

Cross-chain

Arbitrum, Polygon, Ethereum (soon)

Authentication

SIWE-gated payslips

Private AML screening
Chainlink Confidential HTTP screens payees against sanctions and PEP lists without exposing PII on-chain.
On-chain audit proof
Every pay cycle can publish one aggregate audit hash covering total amount, payee count, chain distribution, and timestamp.
What is real in scope
Project facts from the current spec.
The current docs define Finance OS as a single-treasury payroll product on Base, with CCIP routing, Confidential HTTP screening, SIWE payslips, and MiCA-aware policy enforcement.
Mode: single treasury, multi-chain payout
Repos: smart contracts, backend, and CRE runtime
Payout assets in scope: ETH or any ERC20
Policy scope: AML, ACE rules, MiCA disclosure toggles
Core modules
AML screener, payroll batcher, treasury router, audit hasher, compliance engine, and payslip server.
Stack
Chainlink CRE, ACE, CCIP, Confidential Compute, World ID.
Contracts
AMLScreen.sol, PayrollSettlement.sol, AuditHash.sol, and ComplianceMode.sol.
Reference products
Based on the gap between Request Finance and Coinshift for teams that need treasury and compliance in one workflow.
Workflow
One treasury. Four workflows. One proof trail.
Finance OS is built for the moment a Web3 team needs to pay real people, across real jurisdictions, with a record strong enough to survive diligence.

WF1

Screen privately

01

Chainlink Confidential HTTP screens each payee against sanctions and risk lists without placing sensitive data on-chain.

WF2

Route the batch

02

A single treasury on Base submits one payroll cycle while CCIP sends each payout to the chain each worker prefers.

WF3

Commit proof

03

Finance OS anchors one aggregate audit hash per cycle so regulators, investors, and auditors can verify the batch independently.

WF4

Enforce policy

04

ACE-driven controls toggle MiCA and jurisdiction-specific rules automatically instead of relying on manual review every cycle.

Acceptance criteria
What the current project still needs to prove.
Single treasury deploys on Base and triggers the CRE workflow end-to-end.
AML screening runs via Confidential HTTP per payee with no PII touching the chain.
CCIP routes payout to the payee's preferred chain.
Aggregate audit hash is published on-chain per pay cycle.
SIWE-gated payslip endpoint verifies the registered payee wallet.
MiCA compliance mode activates for EU-flagged payees.
ACE policy engine blocks payout if a payee fails screening.
Pay cycle completes without manual intervention after batch submission.
Competitive differentiation
Where Finance OS differs from the reference products.

Private AML screening

Finance OS

Confidential HTTP per payee, per cycle

Legacy approach

Spreadsheet checks or centralized vendor review

Cross-chain payroll

Finance OS

Native routing from one Base treasury

Legacy approach

Separate treasury actions per chain

Compliance enforcement

Finance OS

ACE policy toggles embedded in flow

Legacy approach

Manual review and checklist signoff

Audit proof

Finance OS

Aggregate on-chain hash each cycle

Legacy approach

Explorer links and exported CSV trails