Space Protocols
How do billions of space assets coordinate without centralized control?
Space infrastructure requires protocols for timing, positioning, communication, and settlement. The same patterns that govern terrestrial DePIN apply at orbital scale — but with tighter constraints and higher stakes.
The Three Flows in Space
INTENT → ROUTE → INFRASTRUCTURE → SETTLE → FEEDBACK
↓ ↓ ↓ ↓ ↓
Signal Ground Satellite Blockchain Orbital
request station constellation settlement telemetry
routing
| Flow Stage | Space Implementation | Speed | Who Provides |
|---|---|---|---|
| Intent | User requests data/connectivity | Instant | Customer |
| Route | Ground stations select optimal satellite path | Milliseconds | Routing layer |
| Infrastructure | Satellites relay signals, collect data | Light speed | Constellation operator |
| Settle | Usage metered, payments processed | Blockchain tempo | Settlement layer |
| Feedback | Orbital data feeds AI, improves routing | Continuous | Data layer |
Intercognitive in Space
The Intercognitive Standard applies to space — satellites are robots at orbital altitude.
Nine Pillars Translated
| Pillar | Terrestrial | Space Translation | Status |
|---|---|---|---|
| Identity | Machine passports | Satellite/ground station IDs on-chain | 🔴 Gap |
| Positioning | GEODNET RTK | GNSS + RTK extended to orbital reference frames | 🟢 Mature |
| Time | UMT (Universal Machine Time) | Nanosecond sync for conjunction analysis | 🟡 Emerging |
| Sensors | Perception data | EO as composable service | 🔴 Siloed |
| Compute | Edge AI | Orbital edge computing | 🟡 Emerging |
| Connectivity | Network links | Inter-satellite links, ground station mesh | 🟢 Mature |
| Orchestration | Multi-robot coordination | Constellation management, debris avoidance | 🟡 Centralized |
| Maps | Navigation data | Space situational awareness | 🟡 Government-led |
| Fees | P2P transactions | Per-pass, per-image, per-byte settlement | 🔴 Gap |
Impact on Space Operations
| Domain | Current State | With Intercognitive Standards |
|---|---|---|
| PNT | Siloed GNSS systems | Multi-source, fault-tolerant positioning |
| Earth Observation | Proprietary data silos | Composable, fused data products |
| In-Orbit Servicing | Ad-hoc coordination | Standard task markets for refueling, repair |
| Ground Segment | Vendor lock-in | Permissionless antenna/compute marketplace |
| Space Traffic | Government-run catalogs | Decentralized conjunction analysis |
Key Space Protocols
Communication Protocols
| Protocol | Function | Standard Body |
|---|---|---|
| CCSDS | Interplanetary communication | Consultative Committee for Space Data Systems |
| DVB-S2 | Satellite broadcast | ETSI |
| SLE | Space link extension | CCSDS |
| AOS | Advanced orbiting systems | CCSDS |
Positioning & Timing
| System | Function | Precision |
|---|---|---|
| GPS | US navigation | ~3m civilian |
| Galileo | EU navigation | ~1m |
| GLONASS | Russian navigation | ~2-4m |
| BeiDou | Chinese navigation | ~2m |
| GEODNET RTK | DePIN augmentation | ~2cm |
Space Traffic Management
| Component | Current Provider | Protocol Gap |
|---|---|---|
| Debris tracking | US Space Command, ESA | Siloed, latent data |
| Conjunction alerts | 18th Space Defense Squadron | Centralized |
| Collision avoidance | Each operator | No standard coordination |
| Spectrum coordination | ITU | Slow, bureaucratic |
Standard Workflows
Launch Campaign Protocol
T-180 days: Mission definition → orbit parameters, payload specs
T-120 days: Integration → payload prep, vehicle assignment
T-60 days: Rehearsals → mission sim, range coordination
T-14 days: Transport → payload to launch site
T-7 days: Encapsulation → fairing integration
T-3 days: Rollout → vehicle to pad
T-0: Launch → countdown, ignition, ascent
T+30 min: Deployment → payload separation
T+24 hrs: Checkout → initial operations
Ground Station Pass Protocol
Pass scheduling → Acquisition of signal (AOS)
↓
Uplink commands → Satellite processing
↓
Downlink data → Ground processing
↓
Loss of signal (LOS) → Pass complete
↓
Data delivery → Customer
Protocol opportunity: Per-pass settlement on-chain instead of enterprise contracts.
Earth Observation Workflow
Tasking request → Constellation scheduling
↓
Image capture → Onboard processing (optional)
↓
Downlink → Ground processing
↓
Data fusion → AI analysis
↓
Delivery → Customer/API
Protocol opportunity: Cryptographic attestation of capture time, location, and provenance.
Disruption Vectors
| Workflow | Traditional | Protocol Disruption | Friction Removed |
|---|---|---|---|
| Ground access | Enterprise contracts | Per-pass marketplace | Lock-in, lead time |
| Data delivery | Proprietary formats | Composable APIs | Integration cost |
| Spectrum | ITU allocation | Dynamic sharing | Scarcity |
| Traffic mgmt | Government tracking | Decentralized consensus | Latency, access |
| Identity | National registries | On-chain passports | Sovereignty issues |
The Insight
"Space protocols today are where internet protocols were in the 1990s — fragmented, proprietary, and ripe for standardization."
Whoever builds the TCP/IP of space coordination captures the value that flows through it.
Context
- Space Industry — Parent analysis
- Intercognitive Standard — Physical AI coordination
- Protocols — What protocols are and why they matter
- Telecom Protocols — Terrestrial parallel
The Meta Question
"Will space coordination standards emerge from governments, incumbents, or permissionless protocols?"