PRIMITIVE / 01
Shielded transactions
Use Zcash shielded transaction infrastructure to avoid publishing the normal transparent financial graph.
Technical architecture
Protocol
The Coded Treasury architecture separates receiving, treasury policy, transaction construction, signing and disclosure into distinct responsibilities.
Architecture
Five layers. One private treasury.
The objective is not to invent a new privacy primitive. It is to use Zcash privacy infrastructure with disciplined treasury controls around it.
01 / RECEIVE
Shielded intake
Use shielded receivers and diversified addressing to reduce unnecessary linkage at the point of entry.
02 / STATE
Private treasury
Treasury value remains in shielded state rather than becoming a public balance sheet.
03 / POLICY
Rule engine
Execution requests are evaluated against an explicit operating policy before signing.
04 / SIGN
Isolated authority
Spending authority is separated from the public interface and general application layer.
05 / DISCLOSE
Selective view
Read access can be granted for specific reporting or review needs without publishing everything.
System boundary
The public site cannot spend.
The website should remain a presentation layer. Treasury construction and authorization belong outside the public application boundary.
reference architectureseparation of responsibility
01public_web → read_only
02policy_engine → validate_request
03transaction_builder → construct_proposal
04signer → isolated_authorization
05zcash_network → shielded_settlement
06reporting → permissioned_view
Technical components
Built around existing Zcash primitives.
Coded Treasury is a treasury architecture, not a replacement for the Zcash protocol. The privacy layer is inherited from Zcash; the fund adds policy, operational discipline and controlled disclosure.
PRIMITIVE / 02
Diversified receivers
Generate distinct receiving addresses without treating one permanent public address as the treasury's identity.
PRIMITIVE / 03
Viewing authority
Separate read visibility from spending authority to support selective reporting and due diligence workflows.
CONTROL / 04
Policy validation
Define what the treasury is allowed to do before transaction authorization is requested.
CONTROL / 05
Signer isolation
Keep keys and authorization outside the website and outside general-purpose public application code.
CONTROL / 06
Private infrastructure
Reduce network and operational metadata leakage through careful node, transport and service choices.
Technical review
Read the implementation notes.
The technical documentation describes the policy model, signing boundary, disclosure model and reference operating assumptions.
Open Tech Docs