technically it is a single state, and the thing that you didn't get was that this is not a consensus but rather an inventory (merkle tree) that can be used to identify missing pieces and how to request them from peer relays.

the goal is not a blockchain but an eventually consistent replication of events associated with a nostr key.

it's pretty advanced distributed systems stuff, nobody should feel bad about miscommunicating about it.

i just got done writing quite a long winded bit of signing algorithm just now and i don't want to test it yet because it's too close to bedtime. but it's drafted :D

yes i am working on part of what Colby is talking about.

Reply to this note

Please Login to reply.

Discussion

that’s great; that’s not the proposal I responded to, to which Colby responded unnecessarily aggressively. 🤷‍♂️

Good luck with your project, it sounds interesting.

Ahh I see. The guy you were replying to wasn’t suggesting a single state — he just wanted syncing, but yes a single state would be bcash vibes indeed. I see what point you were trying to make.

We’ve quarreled a bit in the past Pablo so sorry if I was quick to be combative this time around. You were complaining at us a few months ago before OpenSats got the 10M about our decentralized #Nostr GitHub project not being open-source yet.

We told you we would release the project details (trees etc) when they were functional, we finally did on the 4th of July. Still more to be released soon.

https://github.com/HORNET-Storage/scionic-merkletree