bft-json-crdt

I'm quite surprised by the [benchmarks versus Automerge JS & Rust](https://github.com/jackyzha0/bft-json-crdt#benchmarks) when it comes to memory: > Ours (Basic) 27.6MB > Ours (BFT) 59.5MB > Automerge (Rust) 232.5MB I would expect adding the public key tracking to use more memory; I wonder how Automerge is spending so much more memory. Possibly on a bunch of internal caches or memoization that give the order-of-magnitude improvement in speed? > Ops: 100k > Ours (Basic) 9.321s > Ours (BFT) 38.842s > Automerge (Rust) 0.597s

From the article, this appears to be an implementation of Making CRDTs Byzantine Fault Tolerant [0] in Rust [1]. [0]: https://martin.kleppmann.com/papers/bft-crdt-papoc22.pdf [1]: https://github.com/jackyzha0/bft-json-crdt