4 ms·
Congratulations on the release! As someone who used to be in the Secure Scuttlebutt community an now works on OpenMLS, I wonder how they (you?) deal with concu
by hiimkeks 1y ago
Congratulations on the release!
As someone who used to be in the Secure Scuttlebutt community an now works on OpenMLS, I wonder how they (you?) deal with concurrency of Commit messages. I spent quite some time thinking about ways to detect and resolve forks, and the current iteration of MLS doesn't really have good answers here.
- miloignis 1y agoI looked up the spec, and it seems like they just tiebreak on time and hash and throw away the losing commit: https://github.com/nostr-protocol/nips/blob/001c516f7294308143515a494a35213fc45978df/EE.md#commit-message-race-conditions https://github.com/nostr-protocol/nips/blob/001c516f72943081...
- hiimkeks 1y agoHuh, that would make it easy to provoke forks by just backdating a second commit.