Private DAO treasury OS

What this enables

• →A treasury that transacts without broadcasting strategy. DAOs, protocol foundations, crypto companies, and investment collectives run swaps, yield, grants, payroll, OTC, LP positions, and investments out of one account — today all of it public, so every rebalance, grant recipient, and OTC counterparty is legible to competitors and front-runners. STRK20 keeps operations confidential while the treasury stays a single managed account.
• →Role-based permissions with cryptographic teeth. A treasury manager deploys max $500k into whitelisted protocols; market makers trade but cannot withdraw; employees spend $10k/month. Each role is a Session Key scoped to a budget, a protocol allowlist, and an action set — enforced on-chain, not by trust in a signer.
• →Solvency members can verify without surveillance. DAO members prove the treasury is solvent and within policy without seeing every operational transaction. A Viewing Key exposes aggregate reserves and rule compliance to token holders while per-transaction detail stays private to the operators.
• →Unlinkable execution across venues. Each strategy, venue, or counterparty runs through its own Private Sub-Account, so an OTC block trade, a Hyperliquid position, and a grant payout can't be stitched into one treasury fingerprint by outside observers.
• →Compliance-ready by construction. Screening, selective disclosure, and source-of-funds proofs are wired into the treasury so a foundation can satisfy auditors and counterparties under authorization — confidentiality from the public, disclosure to the parties entitled to it.

What you build

A Treasury helper contract that holds shielded balances in the Privacy Pool and fans execution out across Private Sub-Accounts, one per strategy or venue. Permissions are Session Keys parameterized by budget cap, protocol allowlist, action type, and recurrence — a manager key capped at $500k into whitelisted protocols, a market-maker key that can InvokeExternal into perps and DEXs but can't withdraw, an employee key metered at $10k/month. External calls into Ekubo, lending markets, perps, and OTC venues route through InvokeExternal so operations settle privately while remaining policy-enforced. Viewing Keys drive two disclosure surfaces: an aggregate solvency proof for members and a full transaction book for auditors under the Compliance Layer, which also handles screening, selective disclosure, and source-of-funds proofs for grants and payouts.

Why this isn't Safe

Safe has already proven the demand: modular smart accounts with granular allowances, role-specific execution, recurring actions, and spending limits are exactly how serious treasuries want to operate. But every Safe module runs on a transparent ledger — the allowances, the recipients, the strategy, the balances, all public. Anyone can watch a foundation's runway, front-run its rebalances, and profile its grantees. STRK20 keeps Safe's permission model and adds the missing half: Privacy Pool balances, Sub-Account execution, and Viewing-Key disclosure, so the treasury is governable and provable without being public.

Why this isn't Squads

Squads is the Solana equivalent — multisig treasury management with roles, spending controls, and program integrations, and it's the standard for Solana-native organizations. Same transparent-ledger limitation: positions, counterparties, and payouts are all on-chain in the clear, and members can only "verify" by watching everything everyone does. STRK20's treasury lets members verify solvency and policy compliance through a Viewing Key over proven aggregates, while the operational detail stays confidential — role-based control without turning the treasury into a public surveillance feed.