Replying to Avatar Water Blower

The scope of your relay framework is larger than my https://github.com/BlowaterNostr/relayed from a first glance.

It feels like you want to build some sort of web middleware framework but for nostr where an event is akin to a http request.

Then, people can build generic backend software on top of it.

Am I right?

nostr-relay is an extensible relay implementation with complete NIP-01 support. It allows for the replacement of underlying database implementations and can be extended with plugins for additional functionality such as adding blacklists/whitelists, becoming paid relay, and setting up relay clusters, etc

Reply to this note

Please Login to reply.

Discussion

And my personal relay is already powered by it.

What’s the url of your relay? Can other people join?

wss://nostr-relay.app it’s free and everyone can join.

source code: https://github.com/CodyTseng/nostr-relay-nestjs

It uses PostgreSQL. If you care about its performance you can check it out here: http://nostr-relay.app/metrics

Is payment already built in?

I see. The database plugin is nice. But does it mean that I need to run a database in order to run it?

The payment plugin is still on the way, and I need to supplement more knowledge.

I provided an SQLite database implementation, eliminating the need to run an additional database. https://github.com/CodyTseng/nostr-relay-tray uses this implementation.

Great

You can try running this less than a hundred lines of code to experience it. https://github.com/CodyTseng/nostr-relay-sqlite

Let’s definitely have a more throughout discussion. Looks like we are doing similar things.

I think so too. 🫡