Feature and its Use Cases
Problem
Currently, Merkle proofs can only be generated and verified in memory during runtime.
There is no way to:
-
Save a generated proof
-
Share a proof with others
-
Load a proof later for verification
-
Perform standalone verification using a stored proof file
-
This limits practical usage for large dataset distribution and independent auditing.
Additional Context
Impact
Users cannot verify dataset chunks without regenerating proofs, making the system less flexible and less suitable for real-world verification workflows.
Code of Conduct
Feature and its Use Cases
Problem
Currently, Merkle proofs can only be generated and verified in memory during runtime.
There is no way to:
Save a generated proof
Share a proof with others
Load a proof later for verification
Perform standalone verification using a stored proof file
This limits practical usage for large dataset distribution and independent auditing.
Additional Context
Impact
Users cannot verify dataset chunks without regenerating proofs, making the system less flexible and less suitable for real-world verification workflows.
Code of Conduct