I would like to know the answer to that as well. My current understanding is that CRDTs merely guarantee derministic merging of updates to some basic data stru

I would like to know the answer to that as well. My current understanding is that CRDTs merely guarantee derministic merging of updates to some basic data structures, where deterministic means that the outcome is well defined and always the same regardless of the order in which updates are merged. That doesn't mean the outcome makes any sense at all in terms of the sort of application level requirements and constraints you would typically find in a transactional database application. Conflicts may still arise on that level. So I think what we need to really fulfill the promise of CRDTs is a way to express those application level constraints on top of them.