Private Treasury Governance

Private Treasury Governance defines how fund assets are controlled, protected, and allocated under ZK DAO—without exposing treasury wallets, balances, or transaction history.

In ZKFund, the treasury is never autonomous and never public. It is governed entirely through cryptographically enforced decisions.


Purpose

Public treasuries create systemic risk:

  • Wallets become visible attack targets

  • Balance changes reveal strategy and timing

  • Transaction history enables long-term surveillance

For funds and institutions, this is unacceptable.

Private Treasury Governance ensures that:

  • All treasury actions are governance-gated

  • No financial state is publicly observable

  • Strategy remains confidential before and after execution


Treasury as a Governed State Machine

In ZKFund, the treasury is not a wallet—it is a state machine.

Treasury state changes only when:

  1. A valid proposal is finalized

  2. Required execution approvals are proven

  3. Settlement constraints are satisfied

There is no direct manual control over funds.


Governed Treasury Actions

All treasury actions must originate from governance.

Common governed actions include:

  • Asset swaps

  • Capital withdrawals

  • Strategy allocation

  • Liquidity provisioning

  • Parameter updates

  • Emergency freezes or unlocks

Every action is:

  • Explicitly proposed

  • Cryptographically authorized

  • Deterministically enforced


Withdrawal Governance

Withdrawals are among the most sensitive actions.

Private Treasury Governance enforces:

  • Role-based withdrawal permissions

  • Action-specific approval thresholds

  • Amount and frequency constraints

  • ZK-verified LP share proofs (for LP withdrawals)

Withdrawals do not reveal:

  • Who requested them

  • Who approved them

  • Where funds were sent


Allocation & Strategy Control

Strategy decisions are treated as treasury governance actions.

The system supports:

  • Allocation across strategy classes

  • Risk-bounded execution constraints

  • Time-based or condition-based actions

Allocation details remain private:

  • Percentages are hidden

  • Asset composition is not exposed

  • Timing cannot be inferred externally


Emergency Controls

Private Treasury Governance includes emergency mechanisms, such as:

  • Emergency freeze

  • Restricted execution modes

  • Temporary governance override thresholds

These mechanisms are:

  • Predefined by governance rules

  • Triggered through proof-based authorization

  • Invisible until activated

Emergency actions remain private unless disclosure is explicitly approved.


Accountability Without Exposure

Even though treasury state is private, accountability is preserved.

ZKFund provides:

  • Proof receipts for every treasury action

  • Deterministic enforcement of rules

  • Optional selective disclosure for audits

Anyone can verify:

  • That treasury rules were followed

  • That no unauthorized action occurred

Without knowing:

  • What assets were moved

  • How much was moved

  • To whom


Why Treasury Governance Must Be Private

If treasury governance is public:

  • Governance leaks strategy

  • Execution leaks intent

  • Settlement leaks positioning

Private Treasury Governance ensures that:

  • Capital remains protected

  • Decisions remain confidential

  • Governance remains enforceable


Relationship to Other Layers

Private Treasury Governance depends on:

  • Identity Layer for authorization

  • Governance Layer for decision-making

  • Execution Layer for enforcement

  • Settlement Layer for private execution

It does not bypass or replace any layer.


Private Treasury Governance is the final expression of ZKFund’s philosophy:

Control capital with rules, not with visibility.

Last updated