Social
Posts and comments are written to the Tipping v3 contract, so they are permanent and
attributable. Chat is off chain by design and runs over Nostr relays for realtime messaging, so check
which layer you are using before you publish anything.
On chain or not
| Surface | Where it lives | Permanent? |
|---|---|---|
| Posts | Tipping v3 contract, one entry per tip_id | Yes. No edit, no delete |
| Comments | The same contract, with a comment: media prefix | Yes |
| Tips | A plain AE transfer with a payload naming the post | Yes. It is a transaction |
| Hashtags and topics | Derived by the indexer from post content | Follow the posts |
| Trending tags | The Superhero API's trending index | No |
| Chat messages | Nostr relays, off chain | No. Relay-dependent |
| Notifications | The Superhero API, delivered over a socket and web push | No |
| Moderation state | CommunityManagement.aes per community | Yes; it gates chat rooms |
In this section
- The Feed: the popular and latest feeds, the ranking formula and its weights, and how the infinite feed pages.
- Posting: the contract call, the limits, the content encoding, and both the UI and CLI paths.
- Delegated & Gasless Posting:
post_without_tip_sig, for relayers. - Comments: the
comment:media-prefix convention that turns a post into a reply. - Tipping: a plain AE transfer with a payload that names the post.
- Hashtags & Topics: the bridge from the social layer to the token layer.
- Chat: Nostr-based DMs and token-gated community rooms.
- Notifications: every notification type, its channels, and where a click lands.
- Moderation: community moderation through token-holder governance.
Related
- On-chain social: the design argument for putting content on a chain.
- The Tipping contract: the contract-level reference for the content layer.
- Your first post: the shortest path from a funded wallet to a published post.