Skip to content

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Merkle CRDT #160

wants to merge 3 commits into from

Conversation

ashutosh-src
Copy link
Contributor

Update Merkle CRDT for EdgeCompute.

@ashutosh-src ashutosh-src self-assigned this Apr 4, 2025
@ashutosh-src ashutosh-src requested review from jsimnz and addobot April 4, 2025 18:58
Copy link

cloudflare-workers-and-pages bot commented Apr 4, 2025

Deploying docs-source-network with  Cloudflare Pages  Cloudflare Pages

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

View logs

Copy link
Member

@jsimnz jsimnz left a 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

  1. Theyre obsessed with this bullet style formatting, which is super obvious
  2. 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...")
  3. 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.
Copy link
Member

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.
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants