README
What Gao DePIN Is / Is Not#
Gao DePIN is
Gao DePIN is not
An infrastructure services marketplace
An investment contract
A contribution-based compensation system
A profit-sharing arrangement
A usage-driven economic model
A passive income program
A non-custodial settlement system
A yield-generating protocol
A contribution-weighted governance structure
A staking-for-interest mechanism
Gao DePIN is the physical infrastructure layer of Gao Internet. It enables independent operators to contribute real-world resources — compute, storage, and bandwidth — to power a sovereign, distributed internet architecture. Every layer above DePIN depends on it:
-
Layer 8 (AI OS) — compute for agent execution
-
Layer 6 (Network) — bandwidth for P2P relay and routing
-
Layer 5 (Domain) — storage for resolver nodes and Merkle snapshots
-
Layer 4 (Payment) — infrastructure for settlement monitoring nodes
Architecture#
┌──────────────────────────────────────────────────────────┐
│ Layer 8 — AI OS (compute requests) │
└──────────────────────┬───────────────────────────────────┘
│
┌──────────────────────▼───────────────────────────────────┐
│ Layer 7 — Gao DePIN │
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────────┐ │
│ │ Compute │ │ Storage │ │ Bandwidth │ │
│ │ Nodes │ │ Nodes │ │ Relay Nodes │ │
│ │ (CPU/GPU) │ │ (IPFS+) │ │ (P2P relay) │ │
│ └──────┬──────┘ └──────┬──────┘ └────────┬────────┘ │
│ └────────────────┼───────────────────┘ │
│ │ │
│ ┌───────────────────────▼─────────────────────────────┐ │
│ │ Performance Verification │ │
│ │ Validators audit service delivery via │ │
│ │ cryptographic receipts + challenge-response │ │
│ └───────────────────────┬─────────────────────────────┘ │
│ │ │
│ ┌───────────────────────▼─────────────────────────────┐ │
│ │ Settlement — Layer 4 (Gao Payment) │ │
│ │ Usage-based fees paid directly to operators │ │
│ │ No pooling. No custody. Non-custodial. │ │
│ └─────────────────────────────────────────────────────┘ │
└──────────────────────────────────────────────────────────┘
Node Class Summary#
Type
Resource
Consumers
Compensation basis
Compute
CPU/GPU execution
AI OS (L8), SDK (L3)
Per verified execution unit
Storage
Data persistence
Domain (L5), Workspace (L1)
Per GB per period (verified availability)
Bandwidth
P2P relay, routing
Network (L6), Browser (L2)
Per GB transferred (verified delivery)
Hybrid
Multiple resource types
Multiple layers
Combined per verified metric
Validator is a verification role — not a service node type. Validators audit service delivery and sign receipts. They do not provide compute, storage, or bandwidth to consumers. See validator-spec.md.
Two-Rail Economic Model#
Rail A — Proof-of-Contribution (Early Network Phase)#
During early network formation, infrastructure contributors may receive protocol compensation based on measurable, validator-verified service performance.
-
Finite total allocation — fixed at launch, does not inflate
-
Declining distribution over time on a predetermined schedule
-
Performance-weighted only — no passive holding mechanism
-
Supports initial infrastructure bootstrapping
Rail B — Usage-Based Infrastructure Fees (Long-Term Model)#
As network usage grows, operators are compensated directly through usage-based fees paid by consumers.
-
Storage usage fees · Compute workload execution fees · Bandwidth relay fees
-
Optional priority service tier premiums Over time, Rail B is designed to become the dominant compensation mechanism. Fixed governance canon: Governance may tune bounded parameters, but may not override non-custodial settlement, fabricate contribution records, or grant governance weight via token ownership.
$GAO Token Utility#
$GAO serves protocol-level operational functions:
-
Transaction fees (gas) for network operations
-
Validator security bonds (where applicable)
-
Protocol-level coordination mechanisms $GAO does not provide: passive staking rewards, interest or APR, dividend rights, revenue sharing, or ownership interest. Governance influence is based on contribution history, not token ownership.
Cross-Layer Interaction#
Layer
DePIN's role
L2 — Browser
Bandwidth relay nodes power P2P connectivity
L4 — Payment
Settlement monitoring infrastructure; fees paid directly to operators
L5 — Domain
Storage for resolver nodes, Merkle snapshots, IPFS pinning
L6 — Network
Backbone bandwidth and relay infrastructure
L8 — AI OS
Compute nodes execute agent workloads under GAR v1 sandboxing
All DePIN calls from applications flow through @gao/system-sdk → sdk.infrastructure. No direct node access.
Further Reading#
File
Description
node-operator-guide.md
Node types, hardware requirements, registration, SLA, compensation model, exit
validator-spec.md
Receipt verification, challenge-response, fraud detection, collateral, slashing
proof-of-contribution.md
PoC mechanism, scoring model, Rail A distribution, governance weight
storage-compute-spec.md
Technical spec for storage and compute node operation, SDK integration
security-model.md
Threat model, protocol invariants, fraud mitigation, Sybil resistance
Compliance Positioning#
Gao DePIN is structured as an infrastructure marketplace, not a custodial service or financial product. It does not pool revenue, distribute dividends, guarantee compensation, or provide passive returns. Final regulatory interpretation depends on jurisdiction. Operators and integrators must assess applicable requirements with qualified legal counsel.
Legal Disclosures#
This document is informational only. It does not constitute an offer of securities, investment advice, financial recommendation, or legal counsel. Participation involves operational and market risks — demand variability, competitive pricing pressure, infrastructure maintenance costs, technical failures, and regulatory developments. No guarantees are provided regarding revenue, token value, network growth, or operational outcomes. Before participating, consult independent legal and financial advisors, assess technical capabilities and risk tolerance, and ensure compliance with applicable laws in your jurisdiction.