Nostr has one basic object: the event. The event is signed, identified, timestamped and tagged. Different event kinds let clients understand profiles, notes, reactions, long-form content, badges, wallet requests and many other formats.
The event object
NIP-01 defines the basic flow. An event includes an id, a public key, creation time, kind, tags, content and signature. The signature proves that the holder of the private key authorized the event content.
- id. A hash of the serialized event data.
- pubkey. The author identity.
- created_at. Unix timestamp.
- kind. The category of event.
- tags. References, metadata, relay hints and structured context.
- content. The payload, often text but not always.
- sig. The Schnorr signature.
Why kinds matter
Kinds let clients interpret the same event structure differently. A short note, profile metadata, reaction, badge, long-form article, zap receipt or relay list can all use the event model while carrying different meaning.
Tags are the connective tissue
Tags connect events to people, events, relays, addresses, hashtags, geographies, communities, payments and external references. A strong product often depends more on tag design and indexing than on raw posting.
Crays event thinking
For Crays, event kinds and tags can represent profile context, follows, content access, status, award votes, venue signals, membership proof and governance participation. The design challenge is to make that useful without exposing users to protocol clutter.