Service
Nostr systems, down to the relay.
We operate Nostr on both sides of the wire: clients in TypeScript and PHP, and relay implementations in Go. That is an unusual place to have spent time, and it is the reason we can tell you when the protocol does not fit your problem.
What this involves
-
Relays configured for a purpose
We operate relay implementations in Go, including a members-only relay with its own storage layer. Access rules, retention and moderation are decisions specified by the customer, not defaults to accept.
-
Client applications
Web clients in TypeScript and Svelte, and Nostr features inside PHP applications where the rest of the system already lives.
-
NIP implementation and review
Reading a specification, configuring standard components to it exactly, and being honest about which parts of the ecosystem actually support it in practice.
-
Keys, signing and identity
The part where mistakes are permanent. Signing flows, delegation and key handling that does not put a user one bad click away from an unrecoverable loss.
Is this the problem you have?
If it is adjacent rather than exact, say so anyway — the useful conversations usually start that way.