Open
Conversation
added 3 commits
March 18, 2026 17:46
Initial draft specifying: - Kind 333 derezz event with Cantor proof for spatial proximity - Temporal ordering rules (timestamp > previous + 1 second) - Domain owner advantage (knows R = instant derezz) - Kind 334 spawn event for respawning - Domain policy derezz: allow/deny for safe zones - Post-derezz state: victim can only spawn
- Update safe zones section: owner can still derezz - Add owner check in validation logic - Clarify that entering domain means accepting owner authority - Cross-reference DECK-0002 exemption rule
- Change derezz event kind from 333 to 3333 (matches movement events) - Derezz is an action type within kind 3333, identified by 'a' tag - Spawn event also uses kind 3333 with 'a' tag 'spawn' - Add section 6.7 to core protocol: DECK-defined Actions - Table lists base actions (spawn, hop) and DECK actions (derezz, hyperjump) - Links to respective DECK documents
arkin0x
changed the title
added 5 commits
March 18, 2026 17:55
- Use capital 'A' tag (matches core protocol) - Use 'C' tag with coord_hex for coordinates - Spawn after derezz reuses core spawn action with relaxed validation - Update summary table with correct A tag column - Note in core protocol that spawn is extended by DECK-0003 - Initial spawn: coord must equal pubkey - Respawn: coord can be any valid coordinate
- Etymology: derezz = 'de-resurrect' (not Tron reference) - Remove proof_url/proof_hash fields (proofs embedded like movement events) - Pattern event structure after core protocol hop events: - e tags for genesis, previous, victim events - c/C tags for coordinates - proof tag with hash (not URL) - Sector tags X, Y, Z, S - Update validation steps to match new structure - Proof computed same way as hop proof (core protocol §5)
- Respawn after derezz returns victim to ORIGINAL spawn location - coord_hex MUST equal pubkey (same as initial spawn) - This is the dire consequence of being derezzed - Remove 'stationary' limitation (works on moving avatars too) - Being idle makes you an easier target, but not required - Fix kind reference: 3333 not 334 for spawn - Update CYBERSPACE_V2.md to clarify respawn constraint
… chain - Corrected section 3.2: a valid derezz invalidates ALL future actions in the victim's chain, forcing a new spawn event - Added timing attack analysis: backdated derezz is valid but unlikely (requires sleeper pubkey with no published movement) - Removed spawn restrictions from 6.2: protocol cannot deny pubkeys access to cyberspace - Added spawn camping analysis: domain owners can derezz anyone spawning in their territory, creating de facto access control - Strong incentive to mine your own spawn coordinate
- §6.6.1: Document mathematical/protocol/social layer framework - Each DECK should clearly distinguish which layer components belong to - Prevents mixing concerns across layers - Added layer summary to DECK-0003
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Initial draft specifying: