Answers to Common Questions

The Braid Chain is a decentralized rollup built for social products that have to stay cheap once traffic gets real. It answers three problems that have followed open networks around for years: silent takedowns, unclear ownership of the graph, and creators who never see the money. It is assembled on the Loomstack proving framework, which leaves members holding both their audience and their identity.

It gave us provable settlement without a bespoke prover, and its data-availability options let us tune cost per post rather than per transfer.

A validium proves state changes on the settlement layer while keeping the underlying data off it. For high-frequency social writes that is the difference between fractions of a cent and something nobody would pay.

Three: a permissioned testnet, an open testnet with incentives, then mainnet with the sequencer handed over in stages.

Posts, follows, and reactions run through a lighter lane with softer finality. Anything that moves value takes the strict path and settles fully before it is treated as final.

Batched proofs, off-chain data availability, and sponsored fees that let an app absorb the cost of a member’s first few hundred actions.

Like an ordinary app. Keys sit behind a passkey, fees are usually invisible, and nothing asks you to sign a prompt in order to leave a comment.

Connect a wallet to the faucet in the console and it releases 250 $WEFT every eight hours, with a larger grant available on request for teams running load tests.

Add the network from the docs page in one click, or open any app already built on it and the switch happens for you.

Profiles became accounts, follows moved to their own registry, and every piece of content now carries a rule set rather than inheriting one.

The query surface is close to what you already know. Writes changed shape, so the client libraries ship a codemod that rewrites most call sites for you.

First-party clients for TypeScript, Swift, and Rust are current. Anything speaking plain JSON-RPC works without a wrapper.

Swap the base interface, re-deploy, and register the module against your account. Most take an afternoon; the storage layout is unchanged.

Every handle, follow edge, and post was snapshotted and rewritten onto the new chain over a single weekend. Nothing was dropped and nothing changed hands.

No. The only visible step was signing in again once, which pairs your existing key with the new account record.

Point your client at the new endpoint, run the codemod, then re-register any modules. Read paths keep working against a compatibility gateway for a full year.

Where your data availability sits, how you want fees sponsored, and whether any contract you depend on has been deployed here yet. The console lists all three before you commit.

The compatibility gateway stays up until 30 June 2026. After that, writes only land on the new chain.