Extending Akash with Deterministic, Verifiable Compute Across Terrestrial and Orbital Nodes

[Nodlshire]

Wnode → Akash Ecosystem Grant Proposal: Deterministic Sovereign Compute Across Earth Mesh and Space Mesh

1. Summary
   Wnode is a sovereign compute mesh currently operating as a live MVP, with public launch scheduled for August 1st, 2026. It provides a deterministic WebAssembly (WASM) execution environment engineered for high‑frequency, verifiable, capability‑scoped workloads across heterogeneous hardware, spanning terrestrial infrastructure (Earth Mesh) and orbital compute nodes (Space Mesh (Sept 2026)).

This proposal requests funding for a minimal, provider‑side integration that enables Akash providers to execute deterministic Wnode workloads through a lightweight Go sidecar. The integration does not require:

• changes to Akash core,
• modifications to provider runtimes,
• new hardware,
• operational overhead.

By adding Wnode, Akash providers gain the ability to process high‑density micro‑tasks, agent workflows, and verifiable compute pipelines with cryptographically signed receipts, predictable performance, and cross‑mesh optimization. This expands Akash’s execution surface, increases provider utilization, all of which fully aligns directly with economic mechanisms such as AEP‑76 (Burn‑Mint Equilibrium).

Current Status
Wnode is live in closed MVP with active nodes across both Earth Mesh and Space Mesh. All core components are open source:

• GitHub: https://github.com/wnode/wnode
• Documentation: https://https://wnode.one/docs
• Demo walkthroughs:
    ◦ Node Operator UI: https://www.youtube.com/watch?v=NjkikU7lKOw&t=9s
    ◦ Admin UI: https://www.youtube.com/watch?v=7vIVYjBe1K0

2. Architecture Overview

Code
Akash Provider Runtime <---> Wnode Adapter (Go Sidecar)
|
v
Wnode Ingress + Capability Layer
|
v
Deterministic WASM Engine
|
v
Optimization Engine
|
Earth Mesh + Space Mesh

Component Summary

• Provider Runtime Standard Akash provider stack; untouched.
• Wnode Adapter (Go) Hardened sidecar responsible for workload forwarding, receipt verification, and telemetry mapping.
• Ingress + Capability Layer Validates payloads, enforces capability scopes, and ensures deterministic execution boundaries.
• Deterministic WASM Engine Executes workloads with strict memory ceilings, instruction limits, and reproducible behavior               across all hardware classes.
• Optimization Engine Routes workloads across Earth and Space Mesh based on latency tolerance, resource availability, and execution policy.
• Earth Mesh + Space Mesh Unified execution surface spanning terrestrial and orbital compute nodes.

4. Execution Flow
   Code
   Akash Tenant Deployment
   |
   v
   Akash Provider Runtime
   |
   v
   Wnode Adapter (Go)
   |
   v
   Wnode Ingress Layer
   |
   v
   Deterministic WASM Engine
   |
   v
   Signed Receipt Envelope
   |
   v
   Back to Akash Provider → Tenant

Execution Properties
• Deterministic Replay Identical inputs produce identical outputs across all hardware classes.
• Cryptographically Signed Receipts Each execution yields a verifiable result envelope.
• Capability‑Scoped I/O All outbound operations are explicitly declared and enforced.
• Uniform Runtime Profile Providers interact with a consistent execution interface regardless of underlying mesh.

5. Space Mesh / Orbital Compute
   Space Mesh is an operational layer within Wnode’s architecture. Orbital nodes function as asynchronous execution surfaces connected via standard satellite communication protocols.
   Code
   +----------------------+
   | Space Mesh |
   | Orbital Compute |
   +----------+-----------+
   ^
   |
   v
   +---------------------------+---------------------------+
   | |
   v v
   +----------------------+ +----------------------+
   | Earth Mesh | | Edge / Local |
   | (Ground Infrastructure)| | Devices |
   +----------------------+ +----------------------+

Value to Akash
• Resilient, physically isolated compute Ideal for background agents, verification loops, and state audits.
• Unified routing Earth and Space Mesh are treated as a single logical topology.
• Differentiation Akash becomes the first decentralized cloud with seamless orbital execution.

6. Optimization Engine
   The optimization engine increases provider throughput and improves network‑wide efficiency.
   Core Functions
   • Latency‑Aware Scheduling Urgent tasks → Earth Mesh Tolerant tasks → Space Mesh
   • Micro‑Task Consolidation Thousands of agent steps packed into continuous leases.
   • Deterministic Batching Reproducible grouping for consistent replay.
   • Fault‑Isolated Recovery Deterministic replay enables clean recovery without state drift.
   Impact on Akash
   • Higher task density per lease
   • Increased provider revenue
   • Better utilization of idle capacity
   • Strong alignment with AEP‑76 through increased transaction volume

7. Integration Details & Risks
   Integration Footprint
   • Fully isolated Go sidecar
   • Native compatibility with Akash telemetry
   • Zero changes to provider runtime
   • One‑line enablement for providers
   • Apache 2.0 licensed

Risks & Mitigations
• Security Sidecar runs with minimal privileges; full audit planned pre‑pilot.
• Determinism Cross‑architecture determinism validated across Earth and Space Mesh.
• Reliability Automatic fallback to Earth Mesh on satellite degradation.
• Adoption Low‑friction onboarding with SDK + documentation.

8. Success Metrics
   • ≥5 Akash providers running Wnode workloads in pilot
   • ≥30% increase in task density per lease
   • ≥10 new workload types (agents, verification, micro‑tasks)
   • Measurable provider revenue uplift

9. Milestones & Budget
   Milestone Deliverable Cost
   M1 Provider Adapter (Go) $5,000
   M2 Deterministic WASM Backend + Testing $5,000
   M3 Telemetry + Settlement Integration $4,000
   M4 Developer SDK + Documentation $3,000
   M5 Pilot Deployment + Monitoring $3,000
   Total $20,000

10. Timeline
    • Integration: 6–8 weeks
    • Public Wnode Launch: August 1st, 2026
    • Pilot Deployment: Immediately after launch
    • Completion: Within 10 weeks of grant approval

11. Sustainability & Next Steps
    Wnode will maintain the integration as open source. Revenue will derive from usage‑based mesh fees and enterprise licensing. Future work includes deeper Akash integration and additional ecosystem tooling.

Closing Statement
Wnode provides Akash with a deterministic, verifiable execution layer that spans both terrestrial and orbital compute. The integration is minimal, secure, and aligned with Akash’s roadmap. It expands the network’s capabilities, improves provider economics, and positions Akash at the forefront of decentralized, sovereign compute.