How Kaspa Boards works

Kaspa Boards is an accountless imageboard where every thread and reply is a signed KBRD payload inside a Kaspa transaction. The public website is a viewer over the BlockDAG; the Desk creates posts, keeps your local history and lets you send or collect tips.

From message to BlockDAG

1. Write in the Desk. Pick a board, start a thread or reply, optionally attach one image, and review the permanent-post warning.
2. Sign locally. Browser WASM seals the text and metadata with the post's authorship key, then funds the transaction from the unlocked Wallet. Private keys and the profile seed never go to the server.
3. Pay only the network. KaspaForge adds no platform fee. The Desk reads the node's current fee rate and prices the actual transaction mass; longer posts and more inputs can cost more.
4. Rotate wallet change. Any change returns to the next seed-derived HD address and the Desk saves that address before broadcast, so a successful post cannot strand funds on an unrecorded key.
5. Index, don't own. The relay submits the signed transaction; the board indexer independently verifies the KBRD signature and projects valid posts into a rebuildable SQLite cache.

Pseudonymous identity, with an honest boundary

There is no board account, email, username or hosted profile. Each post displays a short fingerprint derived from the public key that signed it. You choose how that key behaves:

Formatting and conversations

Posts are plain UTF-8 text. Raw HTML is never accepted. The Desk's live preview and both readers use the same small imageboard-style grammar:

My posts keeps your local history, text and reply notifications. Opening a saved post jumps to that exact post and marks only its replies as read. Clear deletes the local history and syncs that deletion, but cannot delete on-chain posts and deliberately keeps the financial keys needed for future tips.

Tips: send to a post, then Grab

1. Each anonymous post is also a tip address. Its signed public key maps to a normal Kaspa P2PK address. A stable board identity deliberately reuses one key, so all of that identity's posts share one tip jar; the interface labels the balance shared identity instead of counting it once per post.
2. The author keeps the claim key. The Desk stores it in an append-only encrypted claim vault separate from disposable My posts history.
3. Grab sweeps every available tip. The Boards panel shows the uncollected total beside Grab. Pressing it collects tips in place into the Wallet and reports the amount collected.
4. Recovery does not require Sync for new posts. Wallet → Tips → Recover tip keys derives KBRD v2 anonymous keys from the profile seed and public nonces, accepting a key only when its public key matches the signed post.

Forge Sync is still useful across devices and is the fallback for old KBRD v1 posts whose random keys were not seed-derived. Without Sync, those legacy keys exist only in the encrypted profile copy that recorded them. Collecting any tip creates a public on-chain link between that post key and the destination Wallet address.

Moderation changes the viewer, not the chain

KaspaForge applies topic rules, reports and local image classification to what its own worksafe public viewer serves. A hidden post or thread becomes a neutral tombstone: its text, image and author fingerprint are withheld, while the transaction ID remains linked to the canonical public explorer. Read the Boards publication rules before posting.

Common questions