Bitsocial Docs

Protocol notes, roadmap detail, and contributor playbooks.

This is the source of truth for the ideas the landing page points at. It starts with the protocol-level concepts Bitsocial is built around, then expands into roadmap proposals and the workflow docs currently used inside this repository.

Local moderationPermissionless public RPCSearch docs

Pagefind

Шукайте в документах

Повнотекстовий пошук у поточних документах. Індекс з’являється після запуску збірки документів.

Завантаження інтерфейсу пошуку…

Protocol notes

Explain the core claims from the front page.

These pages replace the old single-page notes view with separate routes, so the landing page can link directly to the idea it is talking about.

Anti-spamCustom challengesWhy each community can choose its own anti-spam policy instead of inheriting a global moderation stack.ModerationLocal moderationWhat "no global bans" means in practice, and what still gets moderated locally by communities and apps.OwnershipIdentity and community ownershipHow keys, hosting delegation, and replaceable infrastructure fit together without turning service providers into custodians.

Roadmap detail

Expand the master plan into pages people can actually read.

The roadmap cards on the landing page now have destination pages instead of generic docs links or an outdated GitHub issue.

Фаза 2Permissionless public RPCA proposal for multi-user Bitsocial RPC infrastructure with isolated users, scoped permissions, and durable ownership.Фаза 4Bitsocial NetworkThe appchain layer proposed to power shared liquidity, decentralized domains, and durable incentives across apps.Фаза 5Decentralize all social mediaThe end-state: many public RPCs, competing apps, portable identities, and optional feed markets instead of captive platforms.

Apps

Clients built on the Bitsocial protocol.

Each app provides a different interface to the same decentralized network. Communities and content are interoperable across all of them.

Іміджборд5chanA decentralized imageboard where anyone can create and own boards, and multiple boards compete for each directory slot.ФорумSeeditAn old.reddit-style alternative where communities are user-owned and compete for default listing slots.

Developer tools

Build on the protocol with hooks and CLI tooling.

Libraries and tools for developers building Bitsocial clients, bots, or community management workflows.

ReactReact HooksA hooks API for fetching feeds, comments, profiles, publishing content, and managing accounts - all without a central server.CLIBitsocial CLICommand-line interface for running a P2P node, creating communities, and managing settings.

Anti-spam challenges

Modular challenges communities can mix and match.

Each challenge type is a standalone package that communities can enable, configure, and combine to fit their moderation needs.

Risk scoringSpam BlockerA centralized risk-scoring service with OAuth and CAPTCHA challenges, dynamic rate limiting, and a network indexer.Image captchaCaptcha CanvasGenerates image captchas with configurable characters, dimensions, and colors.Invite codesVoucher ChallengeGate publishing behind unique voucher codes distributed by community owners to trusted users.On-chainEVM Contract CallVerify on-chain conditions - token balances, NFT ownership, or any smart contract state - before allowing a post.

Infrastructure

Supporting services and protocol-level tooling.

Name resolution, identity verification, and cross-platform integrations that underpin the Bitsocial ecosystem.

NamesBSO ResolverResolves .bso domain names to public keys via ENS TXT records, with caching for Node and browser.IdentityMintpassNFT-based proof-of-personhood via SMS verification, reducing sybil attacks like fake votes and ban evasion.BotsTelegram BotsFeed bots that monitor Bitsocial communities and forward new posts to Telegram channels.

Contributor reference

Keep the repo workflow docs visible instead of hiding them in a raw markdown folder.

The existing docs under /docs/agent-playbooks are preserved and published here for transparency. They are primarily contributor-facing, but they now live inside the docs UI like the public-facing pages do.

WorkflowContributor playbooksHooks setup, bug investigation, translation workflow, long-running agent handoffs, and other repo-specific operating rules.TemplatesProgress and feature-list templatesReference documents for long-running work, including the machine-readable feature list template used by the repo workflow.