TreasuryOS
How it works

Understand any treasury. Execute only your own.

Inspect any supported public treasury without connecting a wallet. A wallet is required only for execution, and it must own the treasury currently being viewed.

Current execution scope — Sepolia only

SupportedUniswap V3 wallet swap
PairsETH ↔ USDC only
Not enabledAave actions, Base, batch actions, x402

Public analysis

Inspect any public treasury

Enter any supported treasury address. Overview, Positions, risk, stress scenarios, and Activity are public and read-only.

01

Enter any treasury address

No wallet connection is required to inspect a supported public treasury address.

02

Scan wallet and DeFi positions

TreasuryOS reads balances and supported protocol positions from the configured test network.

03

Score treasury risk

Concentration, counterparty, liquidity, and stress sensitivity are converted into an operator-grade risk view.

04

Review the treasury

Portfolio, positions, risk, stress scenarios, and execution activity remain read-only for any public address.

Owner-only execution

Operate only the treasury your wallet owns

When the connected wallet matches the scanned treasury, you can create a plan, approve it, simulate it, sign intent, and explicitly submit the transaction.

01

Verify owner wallet

Execution unlocks only when the connected wallet matches the scanned treasury address. If it does not match, management surfaces stay locked and no transaction can be prepared.

02

Create a deterministic plan

The planner produces a pre-trade ticket for supported Uniswap V3 wallet swaps only.

03

Approve and sign intent

Approval and intent signature confirm operator intent. They do not submit a transaction.

04

Simulate with wallet context

The simulation runs from the real owner wallet context before execution is enabled.

05

Execute explicitly

The user clicks Execute and signs the wallet transaction. TreasuryOS does not execute autonomously.

06

Record and verify

The transaction hash and report hash are retained in the TreasuryOS execution record.

Execution guardrails

What must be true before funds can move

No custody: TreasuryOS never holds funds.
No autonomous execution: the owner must click Execute.
No mismatched wallets: execution is locked when owner verification fails.
No hidden AI actions: plans are deterministic pre-trade tickets.

Proof pipeline

A distinct verification record after execution

01

Report

Risk report generated and hashed

02

Simulate

Wallet-context simulation executed

03

Execute

Wallet transaction submitted

04

Verify

Receipt and calldata verified

05

Record

TreasuryOS execution record saved