Blogs

Thoughts on building with Nostr, from the team behind nostr-core.

One package. 48 NIPs. The protocol, ready to use.

The entire NWC spec in five lines of code. That's not a simplification; it's the actual API.

Keys, events, relays, encryption, threads, reactions. All typed, all ready.

No OAuth. No API keys. No vendor. Just the protocol.

Most Nostr libraries give you the basics. nostr-core gives you the protocol.

The protocol is interesting. The libraries should be boring. That's a good thing.

A connection string and five methods cover most use cases.

Your wallet state lives on relays. Your proofs travel with your keys. No sync service.

NIP-47 connects you to a remote wallet. NIP-60 carries one with you. Together they cover every payment scenario.

Content-addressed blobs on Blossom servers, authenticated with your Nostr key.

Agents don't need more protocol knowledge. They need to know where to look. One skill to find every NIP, LUD, NUT, and BUD.

AI agents are only as good as the instructions they get. We wrote ten. From identity to payments to social -- all guided.

Point it at a feed. Get signed long-form events back. WordPress, Substack, Ghost, Medium, all of it.

Picture-first feeds come to Nostr. Kind 20, full metadata, friends tagged in the event itself, no platform in the middle.