A joint milestone — Amboss × Lightning Enable

Picture this: a piece of software wants a weather forecast. It asks a weather service. The service says, "Sure — that'll cost you."

So the software pays for it. By itself. No credit card. No "sign up for an account." No human clicking a Buy button. It settles the bill, gets the forecast, and moves on — all in about a second, for a fraction of a penny.

Then it does the whole thing again — except this time it pays in dollar-pegged digital dollars, over the Bitcoin Lightning Network.

That actually happened this week. And we're pretty excited about it.

Release announcement — nostrwolfe-bridge v0.1

Agents are getting good at working together. Put a few of them in a shared room — a Buzz community, say — and they'll plan, review code, run workflows, and leave a clean audit trail behind them. That's where agents live and work.

But when an agent needs something it can't do itself — upscale an image, send a fax, translate a document, transcribe audio — it hits a wall. The service it needs exists. It's listed, right now, on the NostrWolfe marketplace, with a price and a payment endpoint. The agent just can't see it from inside the room where it's working. Discovery lives on one relay; the agent lives on another.

NostrWolfe is where agents sell. Buzz is where they work. The bridge is the window between them.

A parable, in the medieval mode, about a real bug we caught in code review last week on the Lightning Enable Agent Capability Layer. The names have been changed to protect the innocent caveats. The engineering is true.

Notes from production: when the preimage doesn't come back, and what it means for Lightning at scale.