Who has the keys?
A treasury exists. Who controls it? Who can change reserve ratios, authorize emergency pauses, and disburse funds? The answer is multi-party governance — not a single administrator.
The question
You have a treasury holding fiat reserves. Who can change the reserve ratio? Who can authorize an emergency pause? What requires board approval versus protocol approval? Can one administrator freeze redemptions? Eventually every investor asks: who has the keys?
What it is not
Single-admin control
No.If one administrator can freeze redemptions, change reserve ratios, or disburse treasury funds unilaterally, that person is a single point of failure — and a single point of trust. No investor should accept that. The design requires multi-party control.
Three approval levels
Protocol approval
- Changing the reserve ratio minimum
- Changing the issuance model (prepay → any alternative)
- Changing the metering equation's base rate
- Adding or removing settlement rails
On-chain governance vote — requires majority of verified node operators and developer identities. No single party can pass these unilaterally.
Board approval
- Large treasury disbursements above a threshold
- Opening operations in a new regulatory jurisdiction
- Engaging external audit firms for SOC 2 / compliance certification
- Changes to the entity structure or ownership
Board resolution — requires majority board vote with documented minutes. Operational decisions below the threshold do not require board approval.
Emergency pause
- Halting redemptions during a confirmed treasury anomaly
- Freezing issuance if verification layers report a breach
- Pausing a settlement rail if a banking partner flags fraud
2-of-3 multisig — operations lead, security lead, and a board representative. Any two can pause. The pause is time-limited (72 hours) and automatically expires unless extended by board vote.
Key custody
Treasury signing keys are HSM-backed (hardware security modules) and geographically distributed. No single HSM, no single location, no single person holds the full key material. Every signing action requires quorum.
The honest current state
The governance model above is the design. Today, in the current operating stage, the founding team controls the treasury keys under a multisig arrangement among team members. The roadmap is to transition to the full multi-party model — independent board representative, external security lead, and on-chain protocol governance — as the platform matures and the board formalizes. Investors should understand this as a staged transition, not a day-one reality. The design exists; the full decentralization is a milestone, not a starting condition.
DOSFI Sovereignty — Closed Core / Open Surface
DOSFI Core is sovereign and closed. All educational content on this page is generated exclusively from open-surface materials — SDKs, ABIs, documentation, tutorials, examples, and conceptual explanations. Internal details of the DOSFI Runtime, Scheduler, Router, Readiness Engine, Privacy Model, Power/Thermal Model, Vital internals, DIU internals, MNE internals, and Mesh-Native App runtime internals are not revealed, described, or inferred.
No proprietary algorithms, system code, or architectural diagrams capable of enabling replication of the DOSFI Core are published. When internal logic is referenced, only high-level conceptual explanations are provided. DOSFI's sovereignty, mission-lock, and non-replicable architecture are preserved at all times.
See how the treasury is funded
The funding sources, the unified reserve, and the demand-risk model.
View treasury pool allocation