Blurt Core Updates #1

Welcome to Blurt Core Updates — a regular round-up of what's actually shipping across Blurt: the blog at blurt.blog, the Blurt Wallet, and the backend that quietly powers all the needed blockchain services. Reviewed, published on-chain, and written for the people who use Blurt, not just the people who build it.

Wherever we have to use a technical word, we'll explain it in plain language right after. This first edition covers a busy few weeks — here are the highlights.

blurt.blog

Errors that finally make sense. When the blockchain refused something — you voted again too quickly, a permission was wrong, you hit a limit — you used to get a blunt "Something went wrong." Now you get a calm message, in your language, that tells you what actually happened. And long messages no longer spill off the screen on your phone. (#157, #158, #159)

Your votes icon keeps state. A vote that was already recorded on the blockchain could still look "un-done" in the app, or disappear when you moved between pages. That's fixed. The little arrow that opens the list of voters now also shows on any post that has votes, not only on the ones the app had already loaded in full. (#166, #160)

No more freezes when a server is down. The app talks to a server called an RPC node (the machine that reads the blockchain for you). If yours went offline, the app used to stay stuck on it and freeze. It now automatically switches to another server from its backup list. (#165)

A new AI assistant — built carefully. There's a new assistant on the blog: it types its answer out live, only offers options the provider really has, and wipes itself when you log out. We spent real effort making it secure before turning it on. (#170–#175)

A quiet privacy win. A video's preview picture is now loaded through Blurt's own image proxy — a Blurt server that fetches the picture on your behalf — so simply opening a post can no longer leak your device's network address (your IP) to an outside host. (#167)

Communities behave on their feed. Opening a community's feed now actually loads that community, so its title and moderator tools appear properly instead of the page treating it like an ordinary tag. (#163)

Blurt Wallet

See what you've paid in fees. Blurt charges a tiny fee on every transaction and then destroys it — that coin is permanently removed from the supply (this is called burning). A new Fees view in the wallet shows exactly what your account has paid over any date range, now with the three decimals BLURT really uses instead of six that meant nothing. (#45, #46)

A burn monitor. A new public page shows how much BLURT the chain has destroyed (burned) over time. (#40)

Manage who can act for you. A new Manage Auth tab lets you grant or take back another account's permission to act on yours — posting permission (posting, voting) and active permission (moving funds). (#32)

Delegations that don't fight you. Delegations — the Blurt Power you lend to another account — are shown in tables you can now sort by column and flip through page by page, instead of scrolling forever. (#31, #34)

Safer confirmations. Clicking outside an action's confirmation pop-up no longer silently closes it and leaves the action stuck half-done. And the transfers history filter now separates money coming in from money going out. (#33, #43)

A fresh front door. The login page now matches the rest of the wallet, tables share one clean frame, balances line up neatly, and a broken profile picture no longer leaves an empty hole. (#42, #41, #35, #44)

Wallet Indexer

Behind the wallet sits a new service — the Wallet Indexer — and it's quietly one of the crown jewels of this release. Instead of the wallet crawling the blockchain every time you open it, the indexer reads all of your account's activity ahead of time and keeps it ready to serve.

Faster, with far more to show. Your history — transfers, fees, delegations, rewards — now loads quickly instead of stalling, and there's a lot more of it there at a glance. It's the same data the chain always held; the indexer just makes it fast to reach and easy to read.

The transparency behind the new wallet tools. The Fees view and the burn monitor above only exist because the indexer now attributes every transaction fee to the account that paid it, and totals everything the chain burns — proposal payouts included. (wallet-indexer #8, #9)

Under the hood

Most of this you'll never see directly. It's the backend — the software that reads the blockchain and serves it to the blog and wallet — being made to behave correctly and stay fast.

The social layer plays by the rules. nexus-go is the service that turns raw blockchain data into feeds, follows, communities and comments. This round it was brought in line with how Blurt has always been meant to work: communities apply their posting and moderation rules properly, account permissions are checked consistently, and when someone deletes a post it now actually disappears from feeds and threads. In short — same behaviour Blurt always intended, made sturdier. (nexus-go #89, #90, #91)

Ready-made post templates. nexus-go can now offer server-side post templates — pre-built post layouts an app can pull down — as an addition that changes nothing on the blockchain itself. (nexus-go #92)

A manual for the whole stack

We've also started a documentation site that gathers the whole Blurt stack in one place — the blog, the wallet, the backend and the node — written in the same plain language as this post, so anyone can understand how Blurt fits together. It's a living reference we'll keep growing, and it already includes a written reference for how communities work, exactly as the backend implements them.

Read it here → docs.blurt.blog (communities reference: nexus-go #86)

That's the first edition — and it's only what shipped recently; there's plenty more in flight.

If you build on Blurt, every item above links to its merge request. If you just use Blurt, the short version is: fewer rough edges, some genuinely new tools in the wallet, and a backend that behaves the way it should.

Made with passion and love by:

— The Blurt Core Team