-
Notifications
You must be signed in to change notification settings - Fork 22
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
Serde serialization. #30
Comments
That would indeed be nice to have, though I wonder if there is indeed a better way to handle proof deserialization without having What do you think? |
Good idea! Supporting the constants in |
This adds the `serialization-serde` feature, which implements serde's `Serialize` and `Deserialize` traits for `Proof` and `Lemma`. Fixes SpinResearch#30
This adds the `serialization-serde` feature, which implements serde's `Serialize` and `Deserialize` traits for `Proof` and `Lemma`. Fixes SpinResearch#30
This adds the `serialization-serde` feature, which implements serde's `Serialize` and `Deserialize` traits for `Proof` and `Lemma`. Fixes #30
@afck Thank you for the PR! Just published v1.7.0 to crates.io with your changes :) |
We're using
merkle
'sProof
s in messages that need to be serialized, and want to support Serde in addition to protobuf, so I added a very crudeserialization-serde
feature in my fork: afck@dd41698Unfortunately
Proof
can't just be deserialized, so we added aProofData
that doesn't contain thealgorithm
field, and conversion functions.Would you be interested in merging something like that into master? Is there a better way to handle proof deserialization?
The text was updated successfully, but these errors were encountered: