
Key takeaways
- Block's Buzz provides a workspace teams can host themselves, running as a Nostr relay instead of a proprietary service.
- Buzz records messages, reactions, approvals, workflows, and git activity as signed events in one unified log.
- Human colleagues and artificial intelligence agents use the same identity model when they author events in Buzz.
Block released Buzz as an open workspace, built to run as a Nostr relay, that teams can host themselves instead of relying on a proprietary service. The project gave human colleagues and artificial intelligence agents the same identity model while recording their work as signed events in one unified log.
A workspace built from signed events
Buzz recorded each message, reaction, workflow step, review approval, and git event as a signed event in one unified log. Instead of placing chat in one system, code activity in another, and approvals in a third, the workspace represented those actions with the same signed event model.
The shared model applied to authors as well as actions. A human message and a workflow step an agent generated entered the log under the same identity rules. That gave both kinds of participant an attributable place in the workspace, rather than pushing automated work into an opaque channel.
Hosting it yourself changes who keeps the record
Block built Buzz so a team can host it themselves, running it as a Nostr relay. Those choices let a team operate the workspace itself (on servers it controls) rather than depend entirely on a proprietary collaboration provider to keep every message, reaction, workflow step, review approval, and git event.
The unified log extended beyond conversation. Messages and reactions sat beside workflow steps, review approvals, and git events as signed records. Buzz treated an artificial intelligence agent as an author with the same identity model as a person, giving automated work a visible place in the log instead of an invisible one operating outside it.
One identity model for mixed teams
Buzz used the same identity model for human and artificial intelligence agent authors. Its Nostr relay foundation put signed authorship into the data model, and hosting the workspace themselves gave operators control over where it ran.
The architecture joined communication and execution in one signed log. A team could see messages, reactions, work steps, approvals, and code events through the same event structure, whether the author was human or an artificial intelligence agent. Buzz changed both the storage boundary and the identity boundary, compared with a workspace kept entirely by its vendor.
Why It Matters
Buzz records human and agent activity as signed events in a Nostr relay a team can run itself, giving that team one attributable log without making a proprietary provider the sole keeper of its operational memory. That matters as artificial intelligence agents become workplace teammates, because automated actions need accountable identity, not a hidden vendor process. Bitcoiners already understand the value of verification over institutional promises. Buzz carried that instinct into collaboration software by letting operators host the record themselves and requiring agents to use the same identity model as people.




















