CRDTs

[staab]

Replaceable events in general are bad, but especially lists, which can have race conditions when used from multiple clients. p2panda has an excellent design which accounts for this.

[mikedilger]

Can you summarize how p2panda solves this?

[staab]

Entries are like nostr events, with a hash + signature, with the following differences:

• Payloads are separate from entries, so you can download histories without downloading content.
• They provide a backlink to the previous entry in the log.
• logs (merkle trees representing a series of entries) are differentiated by a log id, reducing contention over histories.
• Entries have sequence numbers, which can help with detecting and reconciling forks.
• Conflicts are resolved deterministically, resulting in eventual consistency. They can also be resolved manually with a merge operation.