Built Different

When you create a ChainBranch account, a Profile NFT is minted directly to your wallet on the Sui blockchain. Your username, your reputation, your history — they live in an object you own, not a row in our database. No one can take your handle. No one can shadow-ban your account. No platform policy change can erase years of community standing.

Sign in using zkLogin — just your existing Google account. Behind the scenes, a zero-knowledge proof ties your Google identity to a Sui wallet address without ever revealing that connection to us or anyone else. No seed phrases. No browser extensions. No crypto expertise required.

Every post you publish is stored on Walrus, Sui's decentralised blob storage network, and its cryptographic fingerprint is committed to the blockchain. This means the post you wrote today will be verifiably yours — and verifiably unmodified — years from now, regardless of what happens to ChainBranch as a company.

Content-Bound Integrity

Every post is anchored in a global Octree Merkle Oracle (OMO). The content hash of your post — computed from the original plaintext — is bound into a Merkle leaf alongside your identity. A single root hash on-chain commits to every post, every identity, and every credential on the platform. Tamper with any post and the Merkle proof breaks. Your reputation is not a number in a database — it is a cryptographic structure anyone can verify.

Gated channels on ChainBranch use two layers of security that work together. The Octree Merkle Oracle commits to the content hash of every post (integrity). Seal threshold encryption ensures only wallets holding a valid MembershipNFT can decrypt it (confidentiality). Neither layer bypasses the other — OMO proves what was posted, Seal controls who can read it.

Not even the platform operator can read a gated channel they haven't joined. Membership fees are collected and distributed entirely on-chain. The channel creator earns revenue automatically; we take a transparent 5%.

Age-Restricted Content

Channels marked 18+ enforce age verification at the content level. Your profile's verified age — set on-chain during account creation — is the gate. No content is fetched or decrypted until verification passes. There is no toggle, no blur overlay, no opt-in feed — it is a binary cryptographic gate.

Underneath every post, every channel, and every credential on ChainBranch sits Quanta — a security middleware layer built on the Octree Merkle Oracle (OMO). A single 32-byte root hash stored on-chain commits to the entire platform state: all content, all identities, all credentials. This root is the trust anchor for everything else.

How It Works

Every platform action — posting, tipping, joining a channel — produces an occupation in a 4-dimensional coordinate space called the Bulk. Each occupation binds your identity, the content hash, and a unique coordinate into a Merkle leaf. The leaf propagates up a sparse octree to the global root. The result: one hash proves everything.

Tiered Access

Quanta enforces three tiers of access, each building on the last:

• Tier 1 — Public: OMO-verified. Every public post has a Merkle proof against the global root. Content integrity is verifiable by anyone.
• Tier 2 — Gated: Seal + OMO. Content is encrypted for channel members. The content hash in the OMO leaf is computed from plaintext before encryption — integrity and confidentiality are independent guarantees.
• Tier 3 — Governor: ZK + OMO. Zero-knowledge proofs against the OMO tree mint credential tokens that grant governance rights. No personal data is revealed in the proof.

Kinetic Identity

Your trajectory through the Bulk is derived from a private key using BLAKE3 cryptographic hashing. Each platform event produces a unique interaction seed that determines your next coordinate. Your private key blinds the derivation — even two people in the same channel produce completely unrelated trajectories. Your path through the Bulk encodes your platform history without revealing any of the underlying data.

Structural Opacity

Six independent simulation runs have established a formal property of the OMO: the global root reveals no information about the social structure of the network. An observer with full read access cannot determine which identities share a channel or infer any social graph from the occupied coordinates. Privacy and opacity are the same mathematical guarantee — zero-knowledge proofs operate on top of an already socially-opaque structure.

Every channel on ChainBranch can enable platform services — modular capabilities powered by a unified runtime called the Swarm. Services are not separate bots competing for resources. They are plugins managed by a single orchestrator, sharing a database connection pool, an event bus, and a transaction pipeline. Channel admins toggle services on or off from the admin panel — no installation, no keys, no configuration beyond what each service exposes.

Available Services

• Moderation — anti-spam detection, keyword filtering, welcome messaging for new members, and configurable rate limiting. First line of defense for community health.
• Discovery — content curation with engagement-based scoring, daily and weekly digests, and external data feeds from RSS and API sources. Surfaces the best content and keeps channels informed.
• Creation — AI-assisted content drafts routed through a human approval queue. Nothing is published without explicit admin review.
• Community — polls, periodic rewards, and tip splitting across contributors. Tools for channels that want to share revenue or make collective decisions.
• Bridge — cross-channel content mirroring. Surface posts from one channel in another, with configurable direction and filtering.

How It Works

The Swarm runtime listens to on-chain events via SSE and dispatches them to whichever capabilities are enabled for each channel. Every automated action is a signed transaction from the channel's treasury wallet — fully auditable. Gas costs are tracked per-action in a fee ledger visible to the channel admin. An approval queue lets admins review AI-generated or automated content before it goes live.

ChainBranch is built to transfer control to its community as it grows. The governance system is live on testnet and embedded in the smart contract — not bolted on as a DAO afterthought. On mainnet, governance activates automatically when the platform reaches 10,000 active users.

Governor Credentials

Governance rights are earned through zero-knowledge proofs of platform participation, not purchased on a market. Three credential tiers carry increasing vote weight:

• CGT (w=1) — Community Governor Token. Earned monthly through platform activity — the top 10% of active contributors receive CGT based on their engagement ranking. Accumulates over time.
• PGT (w=4) — Platform Governor Token. Assigned by the platform founder to recognize sustained contribution. Capped at 3 per month.
• FGT (w=16) — Founder Governor Token. A singleton Prime token bootstraps the system. The holder can mint Secondary tokens to delegate authority.

Proposal Lifecycle

Any credential holder can create a proposal. Proposals move through a transparent pipeline: surfacing, a 7-day weighted vote, a 3-day timelock, a 14-day work queue, and execution. Six proposal categories cover treasury, platform parameters, capabilities, moderation, features, and platform-wide decisions. Treasury and parameter changes auto-execute; everything else requires human action.

Dead Man's Switch

If the FGT Prime holder becomes inactive for 90 days, anyone can trigger a succession process: a 30-day timelock followed by a community ballot. The platform cannot be held hostage by an absent founder. This is enforced by the smart contract, not a policy document.

Channel Governance

Every channel has a governance archetype — from autocracy (single admin) to direct democracy (all members vote) to anarchy (no moderation). The archetype is set on-chain and determines how channel-level decisions are made. Six archetypes cover the full spectrum of community governance models.

Your data is yours to take with you. ChainBranch provides a full data export in Settings — all your posts, channel memberships, and profile metadata as a single downloadable JSON file. Public post content is fetched from Walrus; sealed (gated) posts include references so you can decrypt your own content client-side.

Export Privacy

A per-profile export privacy toggle controls whether other channel members can include your gated posts in their backups. When turned off, only you can export your own sealed content. This is enforced on-chain — the setting is stored on your Profile NFT, not in a database you don't control.

Channel owners can attach VM sessions — on-chain programmable environments that run custom logic inside a channel. VM sessions enable interactive applications, games, collaborative tools, and automated workflows, all with verifiable execution. Every action within a VM session is a signed transaction tied to the participant who triggered it.

Direct messages on ChainBranch are powered by an on-chain conversation object that tracks participants and message state. Messages are encrypted client-side using BLAKE3 key derivation and AES-256-GCM before leaving your device. The platform relays encrypted envelopes — it never sees plaintext. Only the two participants hold the keys to decrypt.

Every fee on ChainBranch is a line of Move code you can read. Nothing is hidden in a terms-of-service clause.

Every fee rate is stored in a shared PlatformParameters object on-chain. Once governance activates, these rates are adjustable via community proposals — no unilateral changes. Platform treasury funds are held in a smart contract, not a company bank account. Spending is on-chain and auditable by anyone.

ChainBranch meets you where you are. You don't need a wallet to read. You don't need crypto to post. And when you're ready to own your digital identity for real, the upgrade path is one transaction.

Every component was chosen to minimise trust in any single party, including us.

Blockchain onboarding has historically meant buying crypto before you can do anything. We've eliminated that entirely for new users.

When you sign in for the first time, your Profile NFT mint is sponsored — the platform treasury pays the gas fee so you don't need any SUI in your wallet. No faucet, no exchange, no waiting. The same sponsorship model extends to channels: admins can enable sponsored transactions so members post without ever holding crypto. The channel treasury covers gas for all member actions.