Zone Earnings — Full Participation, Inference & Coverage Reward System
The Zone earning model defines rewards for vehicle agents, mesh inference nodes, region hosts, the Zone service, and governance-compliant identities across DOSFI, MeshInfer, and MeshNativeExchange. Categories, formulas, and tiers are published; credit accrual into the payout ledger and Vital (DIU) settlement are not yet connected.
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.
Earning Categories
Participation Earnings
Vehicle Agents
Inference Earnings
MeshInfer Nodes
Coverage Earnings
Zone Region Hosts
Service Earnings
Zone as a Mesh-Native Service
Governance Earnings
Identity & Compliance
Each category defines how a contribution is scored and priced. Publishing a formula does not by itself create a balance — credits become redeemable only once accrual is connected to the payout ledger.
Earning Tiers
Tier multipliers apply to cumulative credits per recipient. As a vehicle, node, or region host accumulates credits, their tier upgrades automatically — increasing the multiplier on all future earnings.
Schemas & Message Formats
ZoneEarning Record Schema
{
"earning_category": "enum[participation, inference, coverage, service, governance]",
"recipient_id": "string",
"recipient_type": "enum[vehicle, node, region_host, service, identity]",
"mesh_credits": "number",
"score": "float (0-1)",
"weight": "float",
"session_id": "string",
"region": "string",
"metrics": "json",
"vital_settled": "boolean",
"status": "enum[active, settled, pending]"
}Earning & Payout Events
// Earning event (Vehicle Agent → Zone)
{ "type": "zone.earning", "category": "inference", "recipient_id": "node_0x7a...",
"mesh_credits": 42, "score": 0.87, "weight": 1.2, "vital_settled": true, "ts": "iso8601" }
// Payout event (Zone → MNE Marketplace)
{ "type": "zone.payout", "recipient_id": "node_0x7a...", "total_credits": 1250,
"tier": "gold", "vital_amount": 12.5, "fiat_amount": 125.00, "currency": "USD" }Earning APIs
POST /v1/zone/earnings/activate — Activate full earning model (admin)
GET /v1/zone/earnings?category={cat} — Query earnings by category
GET /v1/zone/earnings?recipient={id} — Query earnings by recipient
POST /v1/zone/earnings/payout — Settle accumulated credits to Vital (DIU)
GET /v1/zone/earnings/leaderboard — Top earners across all categoriesUnified Earning Dashboard Specification
Aggregate Mesh Credits across all 5 categories
Bar chart: participation, inference, coverage, service, governance
Ranked recipients by total credits with tier badges
Bronze / Silver / Gold / Platinum breakdown across all earners
Per-node earning detail for all 9 mesh nodes
Credit-to-Vital conversion and fiat settlement status
Activation Status
Earning model defined, credit accrual not yet connected
The categories, formulas, base rates, and tier multipliers on this page are published, and the admin activation routine can score live mesh node state to produce earning records. Credits are not yet posted to the payout ledger, so accumulated credits do not create a redeemable balance. Vital (DIU) settlement and marketplace payout visibility begin only once accrual is connected.
Earnings balances and payout history live on the Payouts dashboard.
DIU → USD Payout
Request a payout
Settle accumulated Mesh Credits to Vital (DIU) and redeem to USD. Payouts require KYC verification — unverified, pending, or failed accounts are blocked.
No IP or device leakage. Contributor IP addresses, device identifiers, node metadata, and routing information are never collected, stored, or transmitted.