README
the first linesNostr Relay Framework -- use it to implement your own custom relay.
There is an example/reference implementation at basic. Binaries for that are also available under Releases.
## Supported NIPs
These are handled by the framework itself, so every relay built on it gets them:
| NIP | |
| 01 | Basic protocol flow (`EVENT`, `REQ`, `CLOSE`, `EOSE`, `OK`, `CLOSED`, `NOTICE`), including what used to be NIPs 12, 15, 16, 20 and 33 |
| 09 | Event deletion request |
| 11 | Relay information document |
| 67 | EOSE completeness hint |
| 77 | Negentropy syncing (`NEG-OPEN`, `NEG-MSG`, `NEG-CLOSE`) |
These depend on what your relay implements:
| NIP | requires |
Ask a scout
a deep read
DeepSeekDeepSeek . DeepSeek V4 Pro for the deep read
fiatjaf is not in a camp, so the read goes to DeepSeek, the open source scout.
10 of 10 public reads left today. Holders get 3 a day.
No read kept yet.A read is kept for a few hours, so the next visitor sees it without a new call.
Scout calls and heat are information, not advice. They describe public GitHub activity and are never a signal to trade.
Recent commits
default branch- 44dMerge pull request #168 from mattn/use-eventstore-notifier . mattn
- 44dUse eventstore.Notifier . Yasuhiro Matsumoto
- 44dMerge pull request #167 from mattn/add-notifier . mattn
- 44dAdd Notifier for running several instances on one storage . Yasuhiro Matsumoto
- 48dMerge pull request #166 from fiatjaf/fix/nip77-go-nostr-0.52 . mattn
- 48dFollow the go-nostr NIP-77 envelope API . Yasuhiro Matsumoto
- 48dMerge pull request #165 from fiatjaf/feat/client-ip . mattn
- 48dExpose the client address to relay implementations . Yasuhiro Matsumoto
- 49dMerge pull request #164 from fiatjaf/docs/supported-nips . mattn
- 49dREADME: list the supported NIPs . Yasuhiro Matsumoto