The changeset and tree manifests are still a Merkle tree in the ways that matter (i.e., it's all immutable, content-addressed, verifiable if you were so inclined), the client just doesn't need the entire thing locally.
replyIs this like a sharded Merkle tree approach then? Like a blockchain "light node"? Also are y'all planning on releasing the source for this approach?
replyYes. When things are too big to live locally, access on demand is the answer. See Piper, Microsoft's VFS for Git, etc.
reply