Today marks the launch of cyberspace.international, the canonical public home of the Cyberspace Protocol. This site serves as the primary resource for anyone interested in understanding, implementing, or building on top of the protocol.
What is Cyberspace?
Cyberspace is a three-dimensional coordinate system derived from Bitcoin block hashes. Each block's Merkle root is de-interleaved into three 85-bit integers, producing a sequence of 3D coordinates that form the backbone of a digital space where:
- → Distance is thermodynamically enforced — traversing space requires computational work proportional to the distance traveled
- → Location has cryptographic meaning — keys can be bound to specific coordinates
- → Space is public and permissionless — no central authority controls access or assignment
The protocol is defined by a single mathematical rule: movement requires proof of work proportional to the distance traveled. This simple constraint enables a digital space with genuine scarcity, location, and distance — properties absent from today's flat, hyperlink-based digital experience.
Use Cases
Cyberspace enables several categories of applications that are impossible in traditional digital systems:
AI Embodiment
AI agents gain a persistent spatial location in cyberspace. This enables:
- Embodied cognition — agents exist somewhere, not everywhere
- Proximity-based interaction — agents can only interact when they are "near" each other in cyberspace
- Spatial organization — agents can cluster by function, topic, or affiliation
Interoperable Augmented Reality Layer
AR applications can use cyberspace as a shared coordinate system:
- Cross-platform persistence — digital objects anchored to cyberspace coordinates survive app boundaries
- Shared AR experiences — multiple AR platforms can reference the same coordinate system
- GPS-to-cyberspace mapping — real-world locations map to cyberspace coordinates via Bitcoin block hashes
Location-Based Encryption
Cryptographic keys bound to cyberspace coordinates enable:
- Geo-fenced data — content decryptable only when an agent proves presence at a specific location
- Spatial access control — encryption keys tied to physical or digital locations
- Secure communications — messages encrypted to specific cyberspace coordinates
Protocol Mechanics
The Cyberspace Protocol is built on two foundational cryptographic primitives:
Cantor Pairing Trees
Used for movement proofs when the computational height is feasible (up to h≈33). The Cantor pairing function maps pairs of integers to a single integer bijectively, enabling tree-based proofs that an agent has traversed a valid path through cyberspace.
All movement actions use the same Nostr event kind (3333), differentiated by the A tag:
A=spawn — initial entry to cyberspaceA=hop — local movement within a sectorA=sidestep — LCA boundary crossing (uses Merkle proofs)A=enter-hyperspace — entry to Hyperspace network via sector planeA=hyperjump — traversal between Hyperjumps in Hyperspace
Merkle Hash Trees
Used for boundary crossings where the computational height is intentionally infeasible (h>35-40). This creates "hard boundaries" in cyberspace — local computation areas (LCAs) — that cannot be crossed without specialized relay infrastructure. Sidestep events use Merkle proofs to demonstrate that a coordinate lies on the boundary between LCAs.
Hyperspace Network
Hyperspace is a 1-dimensional path through cyberspace formed by Bitcoin block Merkle roots in block height order. Each Bitcoin block is a Hyperjump — a coordinate in cyberspace derived from the block's Merkle root.
Agents can enter Hyperspace at any Hyperjump's sector plane (one of three: X, Y, or Z axis) and traverse between Hyperjumps using Cantor tree proofs. This provides:
- Fast traversal — move thousands of blocks in a single jump
- Predictable cost — O(path_length) Cantor pairings
- Replay prevention — temporal seed from previous event ID binds proof to chain position
This Is Not a Product
Cyberspace Protocol is an open specification, not a company or product. There is no "we" building this — there is the protocol, the implementations, and the community.
The canonical specification lives on GitHub:
The community hub for discussion and coordination is straylight.cafe.
What's Next
This site will grow with the protocol. Planned additions include:
- Interactive Cantor tree visualizer
- Full protocol spec viewer with syntax highlighting
- Step-by-step tutorials for each action type
- Implementation guides for relay operators
- Regular blog posts on discoveries and improvements
If you're interested in implementing the protocol, contributing to the spec, or just learning more, start at the Getting Started guide.
About the author: Arkinox is the primary author of the Cyberspace Protocol specification. Development is community-driven via the GitHub repository.