# A Conflict-Free Replicated JSON Datatype

arXiv: https://arxiv.org/abs/1608.03960 · HTML: https://mlsanity.com/paper/1608.03960/

## Key facts

- Cited by 6 papers in the map (data through 14 Oct 2026).
- First posted on arXiv 13 Aug 2016.

## Built on by (most cited first, 6 of 6)

- [StateFuse: Deterministic Conflict-Preserving Memory for Multi-Agent Systems](https://mlsanity.com/paper/2607.05844/) (2026)
- [Conflict-Free Replicated Data Types for Neural Network Model Merging: A Two-Layer Architecture Enabling CRDT-Compliant Model Merging Across 26 Strategies](https://mlsanity.com/paper/2605.19373/) (2026)
- [Position: Multi-Agent Systems Should Prioritize Concurrency Control](https://mlsanity.com/paper/2608.18092/) (2026)
- [The MMM Data Model -- A Normative Specification for Knowledge Interoperability in a Decentralisable Knowledge Commons](https://mlsanity.com/paper/2607.00032/) (2026)
- [MELD: A Protocol for Merging Knowledge Across Distributed Agentic Memories](https://mlsanity.com/paper/2608.16357/) (2026)
- [AgentRoom: Concurrent Multi-Agent Coding in a CRDT-Backed Shared Workspace](https://mlsanity.com/paper/2608.23740/) (2026)

## Abstract (arXiv)

Many applications model their data in a general-purpose storage format such as JSON. This data structure is modified by the application as a result of user input. Such modifications are well understood if performed sequentially on a single copy of the data, but if the data is replicated and modified concurrently on multiple devices, it is unclear what the semantics should be. In this paper we present an algorithm and formal semantics for a JSON data structure that automatically resolves concurrent modifications such that no updates are lost, and such that all replicas converge towards the same state (a conflict-free replicated datatype or CRDT). It supports arbitrarily nested list and map types, which can be modified by insertion, deletion and assignment. The algorithm performs all merging client-side and does not depend on ordering guarantees from the network, making it suitable for deployment on mobile devices with poor network connectivity, in peer-to-peer networks, and in messaging systems with end-to-end encryption.