Skip to content
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

[FEATURE]: Evaluate using Merkle Tree as a form of integrity check #8886

Open
MichelDiz opened this issue Jun 26, 2023 · 0 comments
Open

[FEATURE]: Evaluate using Merkle Tree as a form of integrity check #8886

MichelDiz opened this issue Jun 26, 2023 · 0 comments
Labels
dgraph Issue or PR created by an internal Dgraph contributor. kind/feature Something completely new we should consider.

Comments

@MichelDiz
Copy link
Contributor

Use case

Merkle Trees are exceptional at ensuring the integrity of large sets of data. By using cryptographic hashes, they can quickly verify whether the data has been altered or tampered with. It is being used in Blockchains, p2p networks and databases.

Unlike traditional methods, Merkle Trees don't require the entire dataset to be downloaded for verification. Only a subset of hashes is necessary to prove the integrity of the data, making the process significantly faster and more scalable, especially for large datasets.

If any portion of the data is corrupted or inaccessible, Merkle Trees enable the retrieval of the remaining data without compromise. This ensures high availability and resilience, which are critical attributes for any data-driven project.

With Merkle Trees, auditing data changes and maintaining historical records is streamlined and efficient. The hierarchical structure allows easy tracing of any changes or updates, fostering accountability within the system.

By reducing the resources needed for data verification and lowering the risk of data corruption, Merkle Trees can significantly cut down on operational costs, making them a cost-effective solution for ensuring data integrity.

Links to Discuss, RFC or previous Issues and PRs

No response

Links to examples and research

No response

Current state

No response

Solution proposal

No response

Additional Information

No response

@MichelDiz MichelDiz added kind/feature Something completely new we should consider. dgraph Issue or PR created by an internal Dgraph contributor. labels Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dgraph Issue or PR created by an internal Dgraph contributor. kind/feature Something completely new we should consider.
Development

No branches or pull requests

1 participant