Cyberspace is a Nostr protocol for a shared 3D space, specified in the arkin0x/cyberspace repository and associated with the ONOSENDAI client. Signed Nostr events place objects in the space and record avatar movement as a chain of hops, each carrying a proof that verifiers check.

Objects and doors

The carried-object merge makes objects carried by an SNO object part of the parent payload. A root table resolves a-address placements before any relay fetch, with each entry keyed under the carrier author’s key, so the root copy takes precedence over a fetched reference. A present but invalid entry yields a placeholder and does not trigger a fetch. Carried objects are sealed inside the bag, and re-publishing an object from a bag omits its table unless the user chooses otherwise.

The doors and chest looks merge adds kind 3341 doors. Each door identifies one room at a specific height, and the room key derives from the location key plus a door secret. The room bag is sealed, and multiple or nested doors are supported. Rotating a lock SHOULD rotate the secret and reseal the room. A chest uses the first look tag that is well formed for its closed or open shape, and a failing payload means no look. Door test vectors await a first implementation.

Both changes were open proposals in October and are now normative specification text.

Movement proofs

The sampled residue revision changes the hop proof commitment to Merkle-sealed modular residues with 16 sampled openings. A verifier checks word-sized residues without rebuilding the large roots. Trees and location keys are unchanged, and the new proof, mn, and mp tags are mandatory.

The only exemption is an exact-ID list of legacy hops holding 2658 version 1 hop IDs that passed the project’s published audit, with 8 failing hops omitted. There is no date-based grace period. That audit’s census read one relay and missed a feeds relay, so the list does not prove complete historical coverage.

Normative signed chain vectors lock the verdict, position, and failure point for 158 synthetic movement chains, 140 ported and 18 new. Separate non-normative golden hop-proof vectors cover 7 prover hops and 26 verifier cases so ports in other languages can compare exact encodings. Where they differ, the spec text wins.

These merges change the specification. They do not show which clients verify the new proofs or render doors, and they carry no hardware performance claim.

Primary sources:

Mentioned in: