Buzz (buzz.xyz): Block's Nostr Agent Workspace, Explained

Key takeaways

1. Date / source. August 12, 2026, unpublished internal watch report. Aggregates Block posts, ARCHITECTURE.md, press, X and three independent accounts.
2. Key framing. launch vocabulary is not architecture documentation. Transposable method: for any platform that calls itself decentralized, read ARCHITECTURE.md before the announcement post. ### The decentralization / architecture gap | Source | Statement | |---|---| | Jack Dorsey tweet | "model-agnostic, decentralized, self-sovereign, and open source" | | Block's ARCHITECTURE.md | "The relay is the single source of truth. All reads and writes flow through it. There is no peer-to-peer event exchange, no gossip, no replication." | | TFTC | "Two of those three hold cleanly. The third needs a qualifier." | A single relay per community constitutes a single point of failure. The sovereignty on offer is organizational — self-host, carry your identity with you — not network redundancy. ### Demonstrated rigor vs exploitation risk | What is formally verified | What is not | |---|---| | multi-tenant isolation mechanized in TLA+ | the unit of permission is channel membership | | authorization properties verified in Tamarin | agents run in --dangerously-skip-permissions, outside any sandbox | | model-checked Git storage protocol | agent observability is lacking — silent OOM kills, abandoned tasks appearing active | | hash-chained append-only audit log | — | The formal proof covers identity and storage; the exploitation risk sits in tool authorization and visibility. Don't let the former reassure on the latter. ### A security distinction worth keeping Tamper-evidence ≠ tamper-resistance. Signed events prove who did what; they do not prevent a compromised relay operator from deleting events. On the relay hosted by Block, messages are not end-to-end encrypted, and model providers may receive prompts and channel content. Question to ask any vendor selling a "tamper-proof" audit log: tamper-proof against modification, or against deletion? ### Figure correction Block's TL;DR announces "33% more work": this is the ratio of completed tasks — 20 versus 15 out of 44 —, not a score gain. The score rises from 59.1% to 71.5%, i.e. +12.4 points, of which 11.4 come from the additional completions. The report itself juxtaposes the two in its synthesis, an ambiguous phrasing not to be copied verbatim into a slide. Full detail, including the negative result on short tasks, in [[patel-block-buzz-teams-tokens-benchmarks-2026-08-06]]. ### Technical stack and deployment Rust relay (Axum WS + REST), Postgres (events + full-text search), Redis (pub/sub, presence, typing), S3/MinIO (media via Blossom), Tauri + React desktop. 127 event kinds; NIP-01 (feed), NIP-42 (login auth), NIP-98 (REST auth), NIP-34 (Git events). Deployment via a production Docker Compose (Postgres, Redis, MinIO, Caddy/TLS), one-click Railway, or Block's free hosted relay in beta. Rust 1.88+, Node 24+, pnpm. ### Interoperability buzz-acp is an Agent Client Protocol harness (born at Zed, JSON-RPC 2.0 over stdio, now under community governance) that plugs in goose, Codex and Claude Code, and translates ACP ↔ MCP — ACP on the client/agent side, MCP on the tools side. Added to this is buzz-agent, an in-house agent: up to 8 concurrent sessions, each with its own MCP servers, history and context; Anthropic Messages API, OpenRouter, or any OpenAI-compatible endpoint (vLLM, llama.cpp, Databricks, Ollama). A formulation worth keeping: "The agent does not know what MCP server it talks to. The MCP server does not know what agent is calling it. They compose through protocols, not imports." For the acronym trap around ACP, see [[girard-acp-deux-protocoles-un-sigle-2026-08-02]]. ### Genealogy goose (Block, January 28, 2025, Apache 2.0, CTO Dhanji Prasanna) is the ancestor, contributed in December 2025 to the Linux Foundation's Agentic AI Foundation alongside MCP and AGENTS.md — 27,000+ stars, 350+ contributors. BuilderBot, Block's first internal Slack agent, provides the original problem: shared credentials, model switching, identity management. Block has been building a position on the open agentic layer for eighteen months. ### Market stakes Bradley Axen (Head of AI Capabilities, Block): "Every company is going to need a place where humans and agents work together. The question is whether that place is proprietary or open." Justin Waldron (Zynga co-founder): "Buzz is not a slack killer. It's much bigger. It's the first proper multiplayer agent harness." Reception: ~25,900 GitHub stars (~7,600 in three days), a Dorsey tweet at ~2.3–2.7M views, TechCrunch / SiliconANGLE / Decrypt coverage, public endorsement from Sundar Pichai. ### Independent field reports | Source | Contribution | |---|---| | DevTools Daily (~07/26) | two-person workspace, self-hosted on a VPS behind Caddy, with Codex, Copilot and Claude agents — successful consolidation, real agent-to-agent handoffs within the same thread; observability is missing | | João Queirós (07/23) | first in-depth evaluation; origin of the channel-authorization formulation | | darrenjrobinson | three agents with distinct identities in a self-hosted Buzz, each with its own keypair and its own billing — "qualitatively different from a bot integration" | Various guides: agents only act on @mention; without a stop instruction, two agents can loop into infinite replies; the hosted onboarding has had bugs (issues #2484, #2367) making self-hosting more reliable at this stage. ### Mobile app (Tom Brow, 07/29) The app does not host agents: it signs messages and connects directly to relays; identity comes from the desktop via QR pairing, with no standalone identity path on mobile. Privacy: no analytics SDK, EXIF metadata stripped before upload, push following a NIP-PL draft where relays cannot see the device token and the gateway sees neither public keys, content, metadata, nor relay identity. A reference model for designing push without metadata leakage. ### What's missing for production use No published price for managed hosting, no enterprise adoption figures, no fine-grained per-tool authorization, no agent observability, unsigned Windows binaries, scattered docs, an early-stage Git forge UI. Block states it plainly: "rough edges and giant chasms". The three proposed re-evaluation thresholds: evaluate self-hosted on a non-critical project if the team is already agent-heavy; wait for fine-grained per-tool authorization and observability before any production use; re-evaluate once a hosting price and a v1.0 are published. ### How to use this fiche It is the context dossier; primary sources lie elsewhere. For the thesis and identity model → [[longwell-block-buzz-workspace-agents-nostr-2026-07-21]]. The dossier ages fast: releases every few days, GitHub metrics in motion, statuses dated mid-August 2026. Worth noting: to help people leave GitHub, Buzz hosts its own code on GitHub.