-
Notifications
You must be signed in to change notification settings - Fork 5
Merkle CRDT #160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Merkle CRDT #160
Conversation
Deploying docs-source-network with
|
Latest commit: |
8849d17
|
Status: | ✅ Deploy successful! |
Preview URL: | https://65fc1bc6.docs-source-network.pages.dev |
Branch Preview URL: | https://ashutosh-guides-merkle-crdt.docs-source-network.pages.dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some semantic changes.
Overall, as a note on using LLMs to help you refactor these docs. I am not against it entirely, but there are notable artifacts/issues when using LLMs for these kinds of refactors
- Theyre obsessed with this bullet style formatting, which is super obvious
- In this context, they write like its a document related to our tech, not specifically made for our tech (eg "Tools like DefraDB address these issues through...")
- One big problem is that is doesn't know about the overall style of the rest of the dev docs, so each document feels like its own independent thing instead of a cohesive and curated set of docs
We can discuss a broader approach to how to best utilize LLMs for this use case.
- **Federated machine learning** where models sync asynchronously | ||
- **Edge computing networks** needing fault-tolerant sync | ||
|
||
They are especially powerful in **IPFS-based systems**, where Merkle DAGs are native. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo: Should be IPLD-based
instead of IPFS-based
|
||
## Branching and Merging State | ||
|
||
### Branching in Merkle CRDTs | ||
|
||
Branching occurs when multiple updates happen concurrently from the same base node. Each update becomes a new branch in the DAG. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo: Branching occurs when updates happen concurrently from different nodes. Each node maintains its own independent branch in the DAG.
Update Merkle CRDT for EdgeCompute.