<aside> ⚠️ This is a rough draft and not final.

There are some new channel concepts being proposed, like curation mode, and other existing channel concepts that we are recommending to be deprecated, like hide cast and channel passes.

Please provide feedback via DC to @dwr

</aside>

Goals

• Allow channels to be permissionlessly created and managed
• Reduce protocol complexity while still allowing flexibility for experimentation
• Ship as quickly as possible

Proposal

• Channels are created and paid for onchain, similar to FIDs
• Every channel is owned by an FID
• Settings are stored onchain, e.g. whether curation mode is on or off
• Metadata stored on Hubs like the channel profile page

How channel feeds work

• By default, curation is not turned on. All casts appear in a single feed. Clients are free to experiment with different algorithms. e.g. for channels without curation, Warpcast will use priority mode.
• If curation is turned on, there are two feeds for each channel:
  • Curated — any cast liked by FID set onchain as the curator
  • All — other casts in the channel; clients may apply filtering to this feed, e.g. Warpcast will apply priority mode by default
• Curators will likely either be:
  • The channel owner — esp. for new or smaller channels. The owner will manually like casts to curate. Warpcast will show the curator a special Priority feed to help surface new and interesting content (client only feature)
  • A bot — esp. for larger and more active channels. Tools like automod will help enable this.

Illustrative example of how channel pages will appear based on curation and what type of user is viewing