Since #nostr #safebox is coming along nicely, I am thinking about what the requirements would be for a corresponding #safeboxrelay.

I have stood up my own strfry instance for testing. It is working really well, and I test random relays using nostr.watch

So far, I haven’t identified any new functional requirements. I hope not, because I want #safebox to work with any standard relay.

Where there might be a difference in requirements from a regular relay, are non-functional, or service requirements, mostly related to availability and, of course, anonymity. Every #safebox has its own nostr identity, and though it is possible, I highly discourage anyone to create a #safebox using their nsec.

There is one requirement I keeping thinking about. Adding quantum-resistant encryption. If records are being stored for any duration, they risk being hoovered up by someone that has state-level patience and may be willing to wait twenty years before cracking the data. An outside possibility, but I would like to address this sooner than later.

In the end, I see #safeboxrelay as a service, where you alone control the data to safekeep your funds and private data, you can replicate at will, and no one can get your data.