Block Buzz: AI Agents Get a Cryptographic Identity (2026)

[Alex]: Welcome back to the Nerd Level Tech AI Cast! I'm Alex, your resident code wrangler and cryptography fan.

[Jamie]: And I’m Jamie, your favorite tech-question-asker-slash-human-who-constantly-forgets-their-own-passwords. [laughs] Today’s episode is all about something called “Block Buzz,” and—spoiler alert—no, it’s not a new caffeinated blockchain energy drink.

[Alex]: Though, honestly, I’d buy that. [PAUSE] But no, today we’re talking about what happens when you give every AI agent its very own cryptographic identity. Picture Slack and GitHub had a baby, and then that baby got super into elliptic-curve cryptography.

[Jamie]: Hold up. You’re saying AI agents get their own… what, passports? Birth certificates? Crypto-wallets?

[Alex]: Think of it more like a digital passport, but one that can’t be faked, forged, or accidentally left at home in your other pants. Block—yes, Jack Dorsey’s Block—just released Buzz, an open-source workspace where both humans and AI agents show up as first-class citizens in the same channels and workflows.

[Jamie]: So, if I’m chatting in Buzz, I could be talking to Alex, our intern Sam, and… GPT-7, all in the same thread?

[Alex]: Exactly. And here’s the twist: every AI agent gets its own cryptographic keypair. That’s the same crypto magic behind Bitcoin, by the way.

[Jamie]: Okay, but don’t bots already have accounts? Like, we add bots to Slack all the time to remind us when it’s Pizza Friday.

[Alex]: Sure, but that bot is usually just piggybacking on a service account or using your API key. In Buzz, each agent has a unique identity, and—here’s the nerdy bit—it also carries a second signature tying it back to the human who authorized it.

[Jamie]: So, it’s like “I, Jamie, hereby grant PizzaBot permission to order extra cheese, and if anything goes wrong, you know it was me who let the cheese monster loose?”

[Alex]: [laughs] Yes, exactly! That’s the chain of custody. If PizzaBot orders 200 pizzas, there’s a cryptographic paper trail showing you gave it the green light. Every action—merge, message, workflow—is signed and tamper-evident.

[Jamie]: Okay, but, like… why do we need all this? Isn’t it overkill for bots?

[Alex]: Well, turns out, 57% of companies already have AI agents running in production, but 68% say they can’t reliably tell what’s the bot’s work and what’s a human’s. That’s like having a Roomba and not knowing if it’s cleaning the floor or ordering a new couch.

[Jamie]: [snickers] That explains my living room.

[Alex]: [PAUSE] With Buzz, every move is logged, signed, and linked to a human—a proper audit trail. No more “who did this?” mysteries when something goes sideways.

[Jamie]: And this is all running on… something called Nostr? Sounds like a Harry Potter spell.

[Alex]: It does, right? Nostr actually stands for “Notes and Other Stuff Transmitted by Relays.” It’s an open protocol, kind of like a more decentralized, open version of chat and sharing platforms.

[Jamie]: So is Buzz totally peer-to-peer? Like, I can run it from my Raspberry Pi and take down Slack?

[Alex]: Not quite. Each Buzz deployment runs on a single relay server. So it’s decentralized in the sense that anyone can run their own relay and keep control of their data—not that there’s no server at all. Block hosts an official relay, but you can self-host if you have the patience and, uh, a high Rust tolerance.

[Jamie]: [groans] Another reason for me to finally learn Rust, I guess. [PAUSE] So, what can you actually do in Buzz? Is it just for coding teams?

[Alex]: For now, yeah, it’s most appealing to teams managing code and lots of agents. You get channels, threads, voice, code repositories, automated workflows—the whole shebang. And, bonus: it comes with its own Git forge, so you can host your repos inside Buzz, not off on GitHub.

[Jamie]: Wait, so you’re saying feature branches are channels, and all the code reviews and CI results are posts in the same place? That actually sounds… kind of awesome. No more “where did that comment go?” scavenger hunts.

[Alex]: Exactly. Plus, it ships with harnesses for coding agents like Claude Code, OpenAI Codex, and something called “goose”—which, I checked, is sadly not an actual goose but a coding agent Block open-sourced last year.

[Jamie]: Missed opportunity for a mascot if you ask me. [PAUSE] But, real talk, can Buzz really replace Slack or GitHub? I mean, those are… kind of a big deal.

[Alex]: Yeah, that’s the billion-dollar question. Slack and Microsoft Teams basically own enterprise messaging, and Block isn’t exactly rolling in cash these days. They just reported a pretty rough quarter and are mid-restructuring.

[Jamie]: So, no business model yet, lots of unfinished features, and I have to wrangle Docker and Rust just to try it… sounds like it’s not for the faint of heart.

[Alex]: Not yet. If you’re a solo operator or a non-technical team, Buzz probably isn’t your jam right now. But if you want your AI agents working alongside humans, with real accountability and open-source freedom, it’s worth watching.

[Jamie]: Plus, you get to say “secp256k1” in meetings and sound like an absolute wizard.

[Alex]: [laughs] Can confirm, it gets you instant nerd cred.

[Jamie]: So, to sum up: Buzz is open-source, built for teams where humans and AI agents work as equals, and every action is cryptographically signed and traceable. It’s early days, but it’s a bold step for agent governance.

[Alex]: That’s right. Whether Buzz takes off or not, giving agents verifiable, portable identities feels like the missing piece for the agent era.

[Jamie]: All right, that’s our nerd level deep-dive for today! If you liked the show, make sure to subscribe, leave us a review, and tell your favorite bot—or, you know, human—about it.

[Alex]: Thanks for tuning in to the Nerd Level Tech AI Cast. Until next time, keep your keys private and your bots accountable! [Outro music fades out]