Buzz

Buzz — Technology. architecture: Nostr relay written in Rust (Axum WS + REST) under Apache 2.0, with Postgres for events and full-text search, Redis for pub/sub, presence and typing, S3/MinIO object storage for media via Blossom, Tauri + React desktop client; 127 event kinds, NIP-01, NIP-42, NIP-98, NIP-34 · source code: Open: code, protocol specifications, test vectors, security sections, and formal models published on github.com/block/buzz; site buzz.xyz · privacy: Telemetry and cancellation as encrypted ephemeral messages, encrypted but durable memory and cost accounting; the server sees only routing metadata. Inference can be routed to an authorized peer's machine, with encrypted model traffic flowing directly between them · decentralization: ARCHITECTURE.md sets the relay as the single source of truth, with no peer-to-peer exchange, no gossip, no replication: one authoritative relay per community, hence a single point of failure. The claimed decentralization is organizational sovereignty (self-hosting + portable identity), not network redundancy · definition: Self-hostable workspace from Block (July 21, 2026, Apache-2.0) built on Nostr, where humans and agents share the same channels; each participant is a keypair, each event is signed in an append-only log · agent identity: Each agent gets its own key pair; its owner signs a narrowly scoped authorization and the agent signs its own work under its own name — "authorization does not erase authorship". Agent revocation without replacing the human identity, cascading disconnection if the owner is removed · interoperability: Claude Code, Codex, goose, and any agent speaking Agent Client Protocol can work there; switching model or harness preserves identity, permissions, and project history · security limits: Authorization is scoped at the channel level, not per tool or action; agents launched with --dangerously-skip-permissions outside a sandbox; no observability of agent activity; signed log is tamper-evident but not tamper-resistant; messages are not end-to-end encrypted on the hosted relay · maturity: Version 0.4.21 or 0.4.22 at launch depending on the source, then 0.5.x; repository created on March 6, 2026, first public releases on May 3, 2026, public launch on July 21, 2026. About 25,900 GitHub stars by mid-August 2026. Unsigned Windows binaries, sparse docs, early-stage Git forge UI; no published pricing for managed hosting · positioning: Presented to shareholders as an internal system for agent collaboration, communication, and code repositories aimed at reducing coordination delays — a productivity framing, complementary to the protocol-openness framing (Apache-2.0, Nostr, ACP) documented elsewhere in this corpus · role: Stated destination of Berd's learnings: the shared human+agent space · status: Human+agent workspace on Nostr, in beta as of August 18, 2026 · Git storage: Repositories stored as immutable content-addressed packfiles on object storage, plus a mutable manifest pointer advanced by conditional compare-and-swap that constitutes the commit point; protocol specified in TLA+ and model-checked, with a mandatory conformance suite per backend · formal verification: Multi-tenant isolation specification mechanized in TLA+, authorization properties verified in Tamarin, Git storage protocol model-checked — an unusual level of formalism for a 0.x version, but covering identity and storage, not tool authorization · agent teams: Agents call each other: a SmartBee delegates a subset of work to a WorkerBee, waits, reviews, and sends it back, with no human relay. Each agent has a name, a persona, a memory, and its own presence in the channel — a seat rather than a session