Which treasury pool backs your Vital?
When multiple compute contracts fund the treasury at different rates, which pool backs a contributor's redemption? The answer is a unified reserve with weighted-average backing — not FIFO, not per-contract.
Modeled Economics — Not Yet Observed
The economic framework on this page is structurally sound and calibrated against published cloud GPU pricing, industrial electricity costs, and standard treasury mechanics. However, the specific figures are projections, not measurements. The following metrics require real customer operations to move from modeled to observed:
Real payout history across active contributors
Actual spend vs. equivalent hyperscaler inference
GPU-hours consumed ÷ GPU-hours available, measured live
Redemption behavior during demand shocks
Contributor and enterprise retention over time
What is defensible today
The framework — metering equation, floor-target-ceiling band, unified reserve model, prepay issuance — is the structurally sound part. It is designed to produce correct incentives regardless of the specific numbers.
What is not yet demonstrated
Whether the modeled rates produce sustainable contributor retention, real enterprise savings, and stable reserve behavior under stress. These are empirical questions answered by adoption — not by protocol design.
As real customers onboard, each metric above transitions from modeled to observed and is published with its source (modeled projection vs. production telemetry).
The question
Two compute contracts exist simultaneously:
Alice holds 2.3 Vital. Which pool backs her redemption? First-in-first-out? Weighted average? Per-contract? Unified reserve?
What it is not
First-in-first-out (FIFO)
No.FIFO ties each redemption to the oldest contract. If Contract A is nearly depleted, a contributor redeeming today gets a worse rate than one who redeemed last week — for the same compute. That creates arbitrary, time-based winners and losers. Redemption value should not depend on when you happen to redeem.
Per-contract isolation
No.If each contract backs only the Vital issued against it, a contributor whose compute was funded by Contract A cannot redeem from Contract B's pool — even if Contract A is depleted. That creates redemption failures against active, funded contracts. Liquidity fragments across contracts instead of pooling.
What it is: unified reserve, weighted-average backing
All fiat deposits from all compute contracts flow into a single unified treasury reserve. All Vital issued against those contracts draws from the same reserve. The redemption rate is the weighted average of all active contracts — not tied to any single contract.
In the example: $200,000 in reserve ÷ 200,000 Vital outstanding = $1.00 / Vital. Alice's 2.3 Vital redeems for $2.30. Every contributor gets the same rate at the same moment, regardless of which contract funded their compute.
Why a unified reserve
Every contributor redeems at the same rate at the same time. No arbitrary winners or losers based on redemption timing or contract assignment.
All deposits back all Vital. A contributor whose compute was funded by Contract A can redeem from the full reserve, not just Contract A's depleted pool.
New contracts at different rates blend into the average. The rate moves gradually as contracts are added and Vital is issued — not in jumps when a contract boundary is crossed.
One reserve, one ratio, one rate. Auditors verify a single treasury balance against a single Vital supply figure — not a matrix of contract-to-contributor mappings.
The issuance model: enterprise prepays
Vital is issued under a prepay model. An enterprise deposits fiat into a compute contract before compute occurs. As compute is verified, Vital is issued to contributors — backed by fiat already in the treasury. Every Vital in circulation was issued against a prior fiat deposit.
An enterprise deposits fiat into a compute contract. The fiat enters the unified treasury reserve.
Contributors execute verified inference. The metering equation determines how much Vital to issue per unit of compute.
Vital is minted to contributors against the prepaid deposit. The treasury already holds the backing fiat.
Contributors redeem Vital for fiat from the unified reserve at the weighted-average rate.
Note: earlier walkthroughs described the flow from the contributor's perspective (compute → earn → redeem). The canonical model is prepay: the enterprise deposit precedes compute, and Vital is issued against that deposit. This ensures every Vital is backed by fiat already in the treasury at the moment of issuance.
What if enterprise demand slows?
This is a treasury management question, not a protocol design question — but it matters in diligence. If enterprises stop funding new compute contracts, what happens to issuance and redemption?
Are new issuances paused?
Issuance continues only against active, funded contracts. If no new contracts are funded, no new Vital is issued. Existing contracts continue to issue Vital as their remaining compute is verified, until the contract is exhausted.
Does redemption continue?
Yes. Outstanding Vital remains backed by existing treasury reserves. Redemption continues from the unified reserve at the weighted-average rate. Contributors are not queued or delayed unless the reserve ratio falls below a defined minimum.
Does the reserve ratio change?
If redemptions deplete reserves faster than new deposits arrive, the backing ratio weakens (more Vital per fiat). If new deposits arrive but issuance slows (fewer contributors), the ratio strengthens. The treasury monitors this ratio continuously.
Is there a minimum reserve ratio?
The treasury maintains a minimum reserve ratio — the fiat-to-Vital ratio below which redemptions are throttled rather than refused. This prevents a bank-run dynamic and gives time for new enterprise demand to fund the reserve.
Can compute rates be adjusted?
Yes. The metering equation's factors (batch size, quality, hardware tier, reputation, price factor) are adjustable. If demand slows, the platform can issue less Vital per unit of compute — strengthening the backing ratio without changing the fiat already in reserve.
The honest summary: if enterprise demand permanently stops, the system winds down gracefully — no new Vital is issued, existing Vital is redeemed from remaining reserves, and the reserve ratio governs the pace. The system does not collapse; it contracts. Whether enterprise demand actually persists is the real business risk, and it is demonstrated over time by adoption, utilization, and repeat contracts — not by protocol design.
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 Vital is priced
The redemption rate, the contract-backed model, and why Vital is neither fixed nor floating.
View Vital pricing