Kaspa Boards Is Live: Post, Tip and Talk on the BlockDAG

Most social platforms ask for an account before they let you say anything, then keep the account, the audience and the archive on their servers. Kaspa Boards starts from a different deal: reading is public, posting is accountless, KaspaForge takes no platform fee, and every thread and reply becomes a real Kaspa transaction.

The first version proved that an imageboard could live on a proof-of-work BlockDAG. The version online now feels like a real place: twelve channels, images, familiar imageboard formatting, quote conversations, a mobile-friendly Desk, local post history — and KAS tips that go directly to authors.

This is no longer a protocol demo wearing a web page. It is a public board that happens to have a BlockDAG underneath it.

Open the page and the whole board is moving

The public Boards page opens on Fresh threads from every channel, ordered by the latest activity. A small /<channel>/ badge tells you where each conversation came from, so /crypto/ can sit beside /g/, /fit/ or /ai/ without turning the feed into visual noise. Pick a channel and the view narrows to that board.

There are twelve worksafe boards today:

• /b/ Random — the front page of harmless chaos;
• /crypto/ Crypto & Kaspa;
• /g/ Technology;
• /v/ Video Games;
• /a/ Anime & Manga;
• /mu/ Music;
• /fit/ Fitness;
• /int/ International;
• /sp/ Sports;
• /biz/ Business & Finance;
• /pol/ Politically Incorrect;
• /ai/ Artificial Intelligence.

You do not need a Desk, wallet or account to read. Open a thread and the public viewer gives you the actual board experience: full-size image viewing, greentext, spoilers, backlinks and quote previews that can be followed through a reply chain. When you want to join in, Post a reply opens the same thread in the Desk.

One KAS is a lot of conversation

Kaspa Boards has an unusually short pricing page because there is almost nothing to price:

The fee is not a fixed product charge. It comes from the network and changes with the post size, wallet inputs and the node's current fee rate. The Desk calculates the real transaction before you confirm. At a recent example of about 0.001858 KAS for a short post, 1 KAS would fund roughly 500 posts. Longer posts or a transaction with more inputs can cost more.

That tiny network cost does two jobs. It anchors the post in proof of work, and it makes industrial-scale spam expensive without charging normal readers anything. KaspaForge does not sell reach, insert ads between replies or take a toll from the post.

A good post can receive KAS

The biggest addition since launch is also the easiest to understand: people can tip a post directly in KAS.

Every post already has a cryptographic signing key. Kaspa Boards turns its public key into a normal Kaspa tip address, so there is no platform balance, creator account or custodial wallet in the middle. A reader taps Tip in the Desk, chooses an amount and sends. KaspaForge takes no percentage.

For the author, tips are designed to feel simple:

• the post shows its current tip balance;
• My posts shows what you wrote and which posts received replies;
• the Grab button shows the total waiting to be collected;
• one tap sweeps available tips into the Wallet without leaving the Boards screen;
• a completion message says exactly how much KAS was collected.

Anonymous posts use separate tip jars. If you choose a persistent board identity — the accountless equivalent of a tripcode — its posts deliberately share one jar, and the interface labels it as a shared identity balance instead of pretending the same money exists several times.

There is one honest privacy boundary: collecting a tip creates another public Kaspa transaction. It can link the post's tip address to the receiving Wallet on-chain. That is why the interface says so next to the action rather than hiding the trade-off in a terms page.

Your posts do not have to stay trapped on one device

An accountless product still has to answer a very practical question: what happens when you switch phones, clear local history or open the Desk somewhere else?

KaspaForge separates two things that look similar but are not:

• My posts is convenient history — post text, jump links and reply notifications. You can clear it.
• Tip claim keys are financial capabilities. They live in a separate encrypted vault and are not erased when you clear the history.

For current posts, Recover tip keys can rebuild anonymous claim keys from the seed inside your encrypted Desk backup. That means a new post's future tips are not permanently tied to the browser that created it. The recovery check happens locally and accepts a key only when it matches the public key signed into the post.

Forge Sync is optional. When enabled, it carries encrypted profile changes, My posts and claim keys between your devices; an optional auto-sync can run when the Desk unlocks. The Sync server stores ciphertext, not a readable profile. For older KBRD v1 posts whose anonymous keys were genuinely random, encrypted Forge Sync history or the original profile copy may still be needed.

The important marketing promise is deliberately modest: we give you practical recovery without pretending there is a hosted account behind it. Keep an offline encrypted .age backup anyway. Sync is convenience, not ownership.

It speaks imageboard

Boards should feel expressive before they feel technical. The composer includes a live preview and a small grammar people already understand:

• bold for emphasis;
• *italic* for tone;
• %%spoiler%% for reveals and jokes;
• >greentext for the ancient oral tradition of imageboards;
• ` code ` for commands and snippets;
• ~~strikethrough~~ for corrections, reversals and cowardice;
• >>post-id to quote another post and build a visible reply trail.

Images are first-class too. Attach one from the styled composer, see it large in the catalog, and open it in an in-page viewer instead of being thrown into a raw browser tab. Uploads accept the common web formats, normalize orientation, strip EXIF metadata and create a clean thumbnail.

The text and the image's SHA-256 fingerprint are signed into the Kaspa transaction. The image bytes stay off-chain, where they can be resized, moderated and eventually pruned. That is a deliberate split: the statement is durable; the heavy media remains responsible.

The Desk remembers the conversation

Posting happens in the Kaspa Desk, the same local workspace used by Wallet, Safe, Escrow and Market. The profile is encrypted in your browser and protected by your local password. KaspaForge does not create a hosted board username or email identity.

After you post, the Desk rotates wallet change to a fresh HD address. My posts keeps the body of new posts, highlights direct replies, counts unread responses and lets you jump back to the exact quoted post. Opening an item scrolls to it and flashes the row, so the action is visible on desktop and mobile instead of apparently happening somewhere above the screen.

The mobile board is not a cut-down afterthought. Channel navigation, quote chains, post history, reply notifications, images, tips and recovery all live in the same PWA surface. Install it or use it in a browser; the keys stay with the encrypted profile either way.

Permanent does not mean unmoderated

Every hosted channel is worksafe, including /b/. Users can report any post. Images pass through local classification before they are served, and the operator can hide a post or thread, block an image hash and remove hosted image bytes.

What moderation cannot do is rewrite Kaspa. A hidden item becomes a tombstone in the KaspaForge viewer; its text, image and author fingerprint are no longer served there, while the underlying transaction remains in the public BlockDAG. The publication rules describe what this viewer will and will not carry.

That distinction matters. “On-chain” is not an excuse to abandon a public surface, and “moderated” is not a claim that a proof-of-work ledger can be edited. Kaspa Boards does both jobs honestly: permanent record underneath, curated worksafe viewer on top.

Why Kaspa makes this feel normal

The technology earns its place when you stop noticing it. Kaspa's BlockDAG accepts parallel proof-of-work blocks and currently runs at ten blocks per second. A post can surface in seconds, and the fee can stay small enough that writing a reply does not feel like settling a contract.

Under the interface, the browser signs a compact KBRD message and puts it inside an ordinary Kaspa transaction. Our indexer verifies those messages and turns them back into boards. If the cache disappears, it can be rebuilt from the BlockDAG. If KaspaForge disappears, the text transactions do not disappear with it.

Want the full limits, recovery model and wire details? They are in the Boards documentation, and the source code is public.

Say something worth the fee

Kaspa Boards is a small experiment with a large idea: public conversation does not have to begin with surrendering an account to a platform.

You can read without signing up. You can post with keys that stay in an encrypted local profile. You can attach an image, format a joke, follow a reply, receive KAS and recover the keys needed to collect it. KaspaForge takes no platform fee. The network keeps the record.

The board is live. The only missing feature is your post.