Specification

The protocol, as written.

Every page below is the repository's own markdown, rendered from commit 8a5b13662640 with a sha256 per file. The URLs are stable: they name the document, not the file it happens to live in. Each page has a raw markdown twin for machines, and one manifest lists them all.

Normative

Cyberspace v2: Protocol Specification

The canonical specification: the 256-bit coordinate system, spawn, hop and sidestep proofs, the temporal work axis, location-based encryption, Nostr integration, and the GPS mapping.

/spec/v2 · /spec/v2.md

DECKs: design extensions

DECKs: Design Extension and Compatibility Kits

How the protocol is extended without changing the base specification, and the registry of DECKs.

/spec/decks · /spec/decks.md

DECK-0001: Hyperspace (Bitcoin block transit)

Long-distance transit through Bitcoin block hashes: stops, landfalls, stations and rides, and the proofs each one carries.

/spec/hyperspace · /spec/hyperspace.md

DECK-0002: Virtual Spawn

A genesis movement event that places an identity without a physical spawn.

/spec/virtual-spawn · /spec/virtual-spawn.md

DECK-0003: SNO (Simple Nostr Objects)

The small 3D object format: an integer lattice with 1/120 ticks, indexed faces, a 256-colour palette, and hard limits. Kind 33331 standalone; the same payload inside bags and avatars.

/spec/sno · /spec/sno.md

Rationale

Cyberspace Design Rationale

Why the protocol is shaped the way it is: the case for imposing locality on a digital system, and the alternatives that were rejected. Non-normative.

/spec/rationale · /spec/rationale.md

Design records

Territory, conflict, and the game layer

The design record separating what the base protocol guarantees from what games built on it may add: holding a region, derezz as an opt-in game, and why there is no domains DECK.

/spec/territory · /spec/territory.md

What can be sold in Cyberspace

A record of which measured limits are real and what, given them, can and cannot be sold.

/spec/what-can-be-sold · /spec/what-can-be-sold.md

Artifacts

File	What it is	URL
cyberspace-neon-256 palette	The built-in 256-colour SNO palette as JSON: 24 hues by 8 steps (index = hue * 8 + step), then steels and signatures.	/spec/sno-palette.json
Palette sheet	The same palette as an image, one cell per index.	/spec/sno-palette.png
SNO reference validator	Dependency-free Python that accepts or refuses an SNO payload exactly as DECK-0003 section 1.9 says, and runs its own rejection table.	/spec/sno-reference.py
Landfall reference	Reference computation for DECK-0001 landfalls.	/spec/landfall-reference.py
Hint reference	Reference for bag hints (section 7.7), with golden vectors.	/spec/hint-reference.py
Sidestep reference	Reference for the sidestep proof (section 6).	/spec/sidestep-reference.py
Visualization vectors	Golden vectors at the Cantor Height 34 scale for renderers.	/spec/visualization_vectors.json