Avatar
semisol
52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd
👨‍💻 software developer 🔒 secure element firmware dev 📨 nostr.land relay all opinions are my own.

NFDB QCG test 3 wirh different tag #test2

NFDB QCG test 2 #test

NFDB QCG test 1 #test

This is a test event for NFDB, a scalable Nostr relay database

this protocol was made originally for IRC-based /dev/random cross-seeding, while also allowing on demand requests if required

it still works to this day

m^2, but yes

the first part prevents exponentially scaling broadcast storm-like behavior, while the 2nd part means you do not have a persistent trackable identifier being broadcast to the networks you use

The times can be changed based off of requirements

- Each client should assume it is not a master at the start

- A client that is a master should broadcast a discovery message every 5 seconds.

- A client that is a master should stop being a master if it sees another client broadcasting a discovery message.

- A client that has not seen a discovery message for 10 to 25 seconds (random for each client) should make itself a master and broadcast a discovery message.

- The discovery message should contain a unique nonce.

- Each client should broadcast a response containing a hash of its own ID, a private value (unique per group of people that want to sync) and the nonce.

- Clients should check the hash to match what they expect, by calculating it with the nonce, the client’s ID and what it assumes is the correct private value.

The effective value of a bounty is lower than the reward as there is no guarantee someone’s work will get paid just because someone else did it a day faster