Tech Docs

System purpose

Coded Treasury is a private treasury architecture centered on Zcash. The public interface communicates the fund's operating model while treasury-specific financial state remains confidential by default.

The architecture is intentionally conservative: privacy is provided by Zcash, while Coded Treasury adds treasury policy, authorization boundaries, operational controls and a selective disclosure model.

Design principles

Minimize public financial telemetry

Balances, counterparties, portfolio decisions and transaction timing can reveal strategy. The public website therefore avoids publishing live treasury data unless disclosure is intentionally authorized.

Separate policy from state

The operating rules may be described publicly even when the current treasury state is private. This creates a useful distinction between how the system is intended to behave and the financial information it protects.

Separate viewing from spending

Read access should not imply transaction authority. Selective reporting can be designed around viewing capability while spending keys remain isolated.

Shielded intake

The receiving layer should favor shielded Zcash receivers and address diversification. The objective is to avoid making a single permanent public address the treasury's visible identity.

• Generate distinct receiving addresses when appropriate.
• Avoid unnecessary transparent outputs.
• Do not publish a live treasury balance as a marketing metric.
• Keep participant-specific receiving information private.

Policy layer

The policy layer defines the intended operating constraints before an execution request reaches the signing boundary.

Authorization boundary

The public website should have no access to treasury spending keys. Transaction construction, review and authorization should be separated so a compromise of the presentation layer does not imply control of treasury funds.

• Public interface: read-only.
• Policy engine: validates request against defined rules.
• Transaction builder: prepares the transaction proposal.
• Signer: isolated authorization environment.
• Network: broadcasts the authorized transaction.

Selective reporting

Privacy does not require an all-or-nothing reporting model. Coded Treasury is designed around deliberate disclosure to a specific audience for a specific reason, rather than perpetual public visibility.

Operational privacy

Transaction privacy can be weakened by careless infrastructure. A production deployment should consider node ownership, RPC exposure, logging, transport metadata, key handling, backups and administrative access as part of the privacy model.

Infrastructure should be designed so the least amount of information is available to each component required to perform its role.

Implementation status

This website presents the Coded Treasury operating model and reference architecture. Deployment-specific custody arrangements, live balances, participant information and private operating details are intentionally not represented in the public interface.