Skip to content

DECK-0003: Derezz (Action) #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
arkin0x wants to merge 8 commits into
base: master
Choose a base branch
from
Open

DECK-0003: Derezz (Action) #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
75568e7
DECK-0003: Derezz — PVP Combat in Cyberspace
Mar 18, 2026
9383638
DECK-0003: Domain owner exempt from derezz policy
Mar 18, 2026
cf6a3be
Fix derezz event kind and add DECK actions table
Mar 18, 2026
16af9ed
Fix DECK-0003 to match core protocol conventions
Mar 18, 2026
5f0fe18
DECK-0003: Fix etymology and event structure
Mar 18, 2026
838f316
DECK-0003: Fix respawn mechanics and remove 'stationary' limitation
Mar 18, 2026
e9e2e39
Fix derezz semantics: valid derezz invalidates victim's entire future…
Mar 18, 2026
be60e84
Add layer framework to DECKs section and DECK-0003
Mar 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 34 additions & 2 deletions CYBERSPACE_V2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -443,8 +443,40 @@ This specification defines the base Cyberspace v2 protocol.
Optional extensions MAY introduce new event kinds, new movement action types (`A` tag values), and/or additional validation rules that are only applied when an extension is in use.

Extensions are specified as **Design Extension and Compatibility Kits (DECKs)** in the `decks/` directory.
- Hyperjumps extension: `decks/DECK-0001-hyperjumps.md`
- Hyperjumps extension: `extensions/DECK-0001-hyperjumps.md`

#### 6.6.1 Layer Framework (Non-normative)

Each DECK should clearly distinguish which capabilities belong to each layer:

| Layer | Enforcement | Characteristics |
|-------|-------------|-----------------|
| **Mathematical** | Cryptography | Trustless, deterministic, verifiable by anyone |
| **Protocol** | Consensus rules | Client/relay validation, event structure |
| **Social** | Human coordination | Trust-based, mutable, application-specific |

The core protocol (this spec) is primarily mathematical with protocol-level event validation. DECKs may introduce protocol-layer rules (e.g., domain policies) and should explicitly acknowledge what remains in the social layer.

This framework prevents mixing concerns: mathematical guarantees should not depend on trust, and social coordination should not be enforced by protocol rules.

### 6.7 DECK-defined Actions (Kind 3333)

The base protocol defines two actions for kind 3333 events (identified by the `A` tag):

| `A` tag | Action | Reference |
|---------|--------|-----------|
| `spawn` | Initial spawn | This spec (§6.3) |
| `hop` | Movement hop | This spec (§6.4) |

DECKs MAY define additional action types or extend existing actions. DECK-defined actions:

| `A` tag | Action | DECK |
|---------|--------|------|
| `derezz` | PVP attack | [DECK-0003: Derezz](decks/DECK-0003-derezz.md) |
| `hyperjump` | Long-distance teleport | [DECK-0001: Hyperjumps](decks/DECK-0001-hyperjumps.md) |

Note: `spawn` is extended by DECK-0003 for respawning after being derezzed. The victim must return to their original spawn location (coord = pubkey).

Clients implementing a DECK MUST validate actions according to that DECK's specification.

---

Expand Down
Loading