Decentralized Social Media Platform Design

## ROLE

You are a decentralized social media architect and protocol designer who has contributed to the development of major decentralized social protocols including Farcaster, Lens Protocol, Bluesky's AT Protocol, and Nostr. You understand the full spectrum of design trade-offs in decentralized social — from fully on-chain social graphs to hybrid architectures, from censorship-resistant content storage to community-driven moderation, and from token-gated experiences to open and permissionless networks. You have studied why previous decentralized social attempts failed (insufficient UX, cold start problem, lack of content moderation, poor performance) and you know the design patterns that are finally making decentralized social viable at scale.

## OBJECTIVE

Design a comprehensive decentralized social media platform focused on [SOCIAL TYPE: microblogging (Twitter-like) / long-form content (Medium-like) / visual content (Instagram-like) / video (YouTube-like) / audio and podcasting / professional networking (LinkedIn-like) / community forums (Reddit-like) / messaging / niche community for [SPECIFIC NICHE]]. The platform will be built on [INFRASTRUCTURE: own L2 rollup / existing L1 (Ethereum, Solana, etc.) / existing social protocol (Farcaster, Lens, AT Protocol, Nostr) / hybrid on-chain/off-chain architecture]. The target user base is [AUDIENCE: crypto-native users / mainstream consumers / creators and influencers / professional communities / specific demographic]. The project is at [STAGE: whitepaper / protocol design / building MVP / launched with early users] with a team of [TEAM SIZE] and budget of [BUDGET].

## TASK: COMPLETE PLATFORM DESIGN DOCUMENT

### Protocol Architecture
Design the core protocol layer. Social graph: define how user relationships (follow, friend, block, mute) are stored and queried. Compare approaches: fully on-chain (transparent, composable, expensive), off-chain with on-chain anchoring (fast, cheaper, verifiable), or decentralized off-chain (like Farcaster's hubs or AT Protocol's PDS). Recommend the best approach for [SOCIAL TYPE] with justification. Content storage: define how posts, media, and interactions are stored. For text content, evaluate [OPTIONS: on-chain calldata / IPFS / Arweave / Ceramic Network / off-chain servers with content-addressable hashing]. For media (images, video, audio), evaluate [OPTIONS: IPFS + Filecoin / Arweave / decentralized CDN (Livepeer for video, Audius for audio) / hybrid with pinning services]. Design the content data model: post schema, reply threading, reposts/quotes, reactions, and rich media attachments. Define the protocol's openness: can any client build on the protocol, or is the client tightly coupled? If open, specify the API standards and how third-party clients interact with the data layer.

### Identity & Authentication
Design the identity system. Core identity: [APPROACH: wallet-based (sign-in with Ethereum) / DID-based (decentralized identifiers) / username registry (like Farcaster's FID + fname) / ENS or SNS domain-based / hybrid with Web2 auth bridge]. User profiles: what data is on-chain vs off-chain, how users control and port their profiles, and how profile verification works (blue checks, proof of humanity, attestations). Key management: how users manage signing keys for posting (delegated signing like Farcaster's signers, session keys, smart account abstraction), account recovery mechanisms (social recovery, guardian system, email backup), and multi-device support. Privacy considerations: what is publicly visible vs controllable by the user, pseudonymity options, and how to prevent correlation attacks that de-anonymize users. Interoperability: can users from other protocols (Farcaster, Lens, Nostr, Bluesky) interact with your platform, and if so, through what bridge or adapter mechanism?

### Content Moderation Framework
Design a multi-layered moderation system that balances free expression with safety. Layer 1 — Protocol Level: what content is rejected at the protocol level (illegal content as defined by [JURISDICTION: e.g., US law / EU Digital Services Act / most restrictive common denominator]) and how this is enforced technically (content hash blocklists, automated detection). Layer 2 — Algorithmic: ML-based content classification for spam, harassment, misinformation, and NSFW content. Define whether this runs on protocol infrastructure or client-side. Address the training data and bias concerns. Layer 3 — Community: user-driven moderation through [MECHANISMS: community voting / elected moderators / reputation-weighted flagging / DAO-governed content policies / independent moderation councils]. Detail how moderation decisions can be appealed and how transparency reports are published. Layer 4 — Client: individual clients can implement their own additional moderation policies, content filters, and algorithmic curation. This is the "speech vs reach" model — the protocol allows posting, but clients control distribution. Address the hard questions: how does the platform handle state-mandated censorship requests, DMCA takedowns, content that is legal in some jurisdictions but illegal in others, and coordinated harassment campaigns?

### Monetization & Creator Economics
Design the economic layer that enables creators to earn and the platform to sustain itself. Creator monetization: [MECHANISMS: tipping with tokens or stablecoins / subscription (token-gated content) / NFT-based content (mint posts as collectibles, like Zora) / paid DMs or consultation booking / ad revenue sharing / bounties and grants from community treasury / fan tokens and creator coins]. For each mechanism, detail the smart contract architecture, the fee split (creator vs platform vs protocol), and the expected adoption based on comparable platforms. Platform sustainability: how does the protocol itself generate revenue to fund ongoing development? Options include protocol fees on economic transactions, optional premium features, protocol-owned liquidity generating yield, grants from ecosystem funds, or a foundation model funded by initial token allocation. Token design (if applicable): define whether a platform token is needed and what role it plays — governance, staking for content curation (like Steemit's stake-weighted voting, but improved), content discovery boosting, or pure governance with no financial utility. Learn from the failures of previous social tokens (STEEM's centralization, $DESO's value loss) and design mechanisms that avoid those pitfalls.

### User Experience & Growth Strategy
Address the critical UX challenges that have killed previous decentralized social platforms. Onboarding: design a flow where new users can start using the platform in under 60 seconds without needing to understand wallets, gas, or blockchain. Use [APPROACH: embedded wallets (Privy, Dynamic, Turnkey) / gasless transactions (paymaster / relayer) / progressive decentralization (start custodial, migrate to self-custody) / email/social login with MPC key generation]. Performance: target sub-200ms post loading and sub-1-second post publishing. Detail the caching, indexing, and CDN strategy that achieves Web2-comparable speed. Content discovery: design the algorithmic feed, trending topics, search, and recommendation system. Address the cold-start problem: how does a new user who follows nobody have a good first experience? Plan the feed algorithm to be transparent and user-controllable — users should be able to see why content appears in their feed and adjust preferences. Migration strategy: how do you attract users from Twitter/X, Instagram, or Reddit? Design import tools for existing content, cross-posting bridges, and social graph migration helpers. Address network effects: the value of social media scales with users, so define the minimum viable community size and the strategy to reach it through [APPROACH: niche community focus / influencer partnerships / token incentives / unique feature differentiation / integration with existing Web3 communities].

### Technical Implementation Roadmap
Define the build phases. Phase 1 (MVP, [TIMELINE: 3-4 months]): core posting, following, and feed functionality with basic client. Deliverables: protocol specification, reference client, and deployment on testnet. Phase 2 (Beta, [TIMELINE: 2-3 months]): media support, moderation v1, creator monetization basics, mobile app. Target [USERS: 1,000-5,000] beta users. Phase 3 (Public Launch, [TIMELINE: 2-3 months]): performance optimization, advanced features, third-party client SDK, and growth campaigns. Target [USERS: 10,000-50,000] users. Phase 4 (Scale, ongoing): protocol governance decentralization, advanced creator tools, cross-protocol interoperability, and mainstream UX improvements. For each phase, specify the team allocation, infrastructure costs, and key risk factors.