Merklizing the key/value store for fun and profit

What’s worth mentioning is that IPFS is built on top of a data model named IPLD.<p><a href="https:&#x2F;&#x2F;ipld.io&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;ipld.io&#x2F;</a><p>If you are planning on doing your own experiments with Merkle tree and such, I can strongly recommend using IPLD as well. The IPLD project has standard libraries for a bunch of programming languages.<p>The advantage of using IPLD is that you can use regular IPFS tooling to inspect the data and make backups&#x2F;restores. Regardless of your desire to share the data over IPFS.

As someone following German politics I had to read the headline twice :) Haven&#x27;t seen it used without tree.<p>(Yes, the spelling is not the same, but we are talking associations, not exact science.)

Wouldn&#x27;t it be simpler to use a trie over the hashes instead? It seems to me like it would have the properties desired here. I think the parent&#x2F;child rule described here might actually result in some kind of trie.

I read this with great interest. Sometimes technologies come around that make me seriously wonder if I should embrace them or continue on the path I’ve already designed.<p>They include: CRDTs, PouchDB, hypercore, etc.<p>What I currently have is my own, PHP-based implementation of essentially a history of “collaborative documents that evolve through time” — with each document having one machine as a source of truth:<p><a href="https:&#x2F;&#x2F;qbix.com&#x2F;platform&#x2F;guide&#x2F;streamsConcepts" rel="nofollow noreferrer">https:&#x2F;&#x2F;qbix.com&#x2F;platform&#x2F;guide&#x2F;streamsConcepts</a><p>So basically, I think that syncing and CRDTs (y.js and automerge) can be excellent for collaborating on documents, but not so great for chatrooms and smart contracts &#x2F; crypto where order of operations matters. For those, you can implement <i>optimistic interface updates</i> but when conflicts (rarely) arise, your interface may roll back changes it displayed. This is especially true after a netsplit.<p>I thought about using PouchDB but the thing is that CouchDB is an extra process people have to run and we want our stuff to run anywhere Wordpress does. Ditto for hypercore. These are great technologies, but it seems what we have is great for fhe very reason tht it’s in PHP - still the most widely supported commodity hosting environment in the world by far. What are the stats these days for PHP vs Node, Go etc.?

Question:since doing this requires hashing your entire tree, what are the implications of doing this hashing operation on possibly millions of entries (which I&#x27;m estimating is the scale at which comparing linearly really start being noticably slow)?<p>I&#x27;m guessing you need to choose a hashing function correctly, but is hashing 2n elements then comparing in log(n) actually that much faster than comparing in n? Evidently, with the right settings yes, or we wouldn&#x27;t be here, but I&#x27;m just wondering if the hashing step doesn&#x27;t actually end up costing a lot more than we think by saying &quot;oh we just hash it&quot;

If you are excited about these data structures you might be interested in my new database engine using prolly trees and designed to be used by React developers.<p>Blog: <a href="https:&#x2F;&#x2F;fireproof.storage&#x2F;posts&#x2F;from-mlops-to-point-of-sale:-merkle-proofs-and-data-locality&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;fireproof.storage&#x2F;posts&#x2F;from-mlops-to-point-of-sale:...</a><p>React hook: <a href="https:&#x2F;&#x2F;use-fireproof.com" rel="nofollow noreferrer">https:&#x2F;&#x2F;use-fireproof.com</a>

Does anyone know a good resource on how to efficiently build a Merkle tree from a big k&#x2F;v store? for example, should you cache intermediate nodes?

Does anyone know how a tool like Figma or Miro handle conflict resolution or synchronization so efficiently in real-time? For example: the position of a simple colored box being manipulated by 2 or more people at the same time. Is this article even remotely relevant for such a use case?