The key words "RAW", "DRAFT", "STABLE", "DEPRECATED", and "RETIRED" in this document are to be interpreted as described in NIP-1962.
1031Rocket Ignition Event [STATUS: DRAFT]31108Rocket Metadata Event [STATUS: RAW]2008Consensus Event (signed by a pubkey with Votepower) [STATUS: DRAFT]31009Identity Tree Event (list of pubkeys to include in the tree) [STATUS: DRAFT]1971Problem Tracker Event [STATUS: DRAFT]
- Rockets
- Identity Tree
- Problem Tracker
- Non-binding ideas about protocol flow
- Non-binding ideas about VM architecture
- Original Identity Tree
Most Nostrocket data structures can be used with or without Nostrocket. When Nostrocket NIPs are used without being attached to the Nostrocket economic system, we say that it is being used detached.
The following icons are used to represent what data should and should not be included in Events depending on whether the NIP is being consumed as part of the Nostrocket economic system, or if it's being used detached from Nostrocket.
-
🚀 Indicates that this is only applicable when when operating attached to Nostrocket.
-
🍌 Indicates that this is only applicable when used in detached mode.
ignitionTag = ["e", "1bf16cac62588cfd7e3c336b8548fa49a09627f03dbf06c7a4fee27bc01972c8", "", "root"]
note1r0cketrztzx06l3uxd4c2j86fxsfvfls8klsd3aylm38hsqewtyqyp7wj7