At its core, a Nostr event represents a discrete piece of facts shared across the Nostr protocol. These events are cryptographically signed data packets that convey messages, user actions, or metadata. Unlike traditional social media posts tied to centralized databases, Nostr events are stored in a decentralized manner, empowering users with unparalleled control and censorship resistance.
Each event follows a standardized structure including:
- Event ID: A unique identifier derived from the content and metadata.
- Public Key: Identifies the creator of the event.
- Timestamp: Marks the precise creation time.
- Content: The actual message or data payload.
- Signature: Ensures authenticity and integrity.
These elements collaborate to create a tamper-proof ledger of communications, offering openness and trust.Events can represent a wide array of user interactions such as text notes, replies, reactions, or file references – making them the basic building blocks of the Nostr ecosystem.
| Component | Purpose |
|---|---|
| Event ID | Unique identifier ensuring event uniqueness |
| Public Key | Identifies event creator |
| Timestamp | indicates event creation time |
| Content | Holds the data or message |
| Signature | Authenticates and secures the event |
Create your Nostr Profile