Sadly they don't solve conflict resolution. They just push the problem to the application developers. From [1]:
> All the DHT does is accumulate all these [updates] and present them to the application.
> All the DHT does is accumulate all these [updates] and present them to the application.
Yes, people will want conflict-resolution for contention on scarce resources, and it'd be lovely to have that baked into the system.
Two options (and yes, both still leave conflict resolution in the app dev's hands):
- Have the zome function resolve the conflict after it retrieves conflicting metadata from the DHT
- In the future we'll bake conflict resolution right into the network layer, so DHT authorities can resolve the conflict automatically using CRDTS or manually by pinging the nodes that published conflicting information so they can resolve it themselves.
It's also worth mentioning Syn, a library which uses operational transforms (a precursor to CRDTs) for conflict-free collaborative document editing. https://github.com/holochain/syn. I'm looking forward to seeing someone produce something similar, but with CRDTs.