So at this point I'm successfully performing validations from a wasm component compiled from the protocol
crate. Was looking at doing inclusion proofs as well, which are in the client
crate. Would there be downsides to moving some of that logic out of the client
crate?
caveat related to validations working, I'm not sure if the issue is me, jco
, cargo-component
, or wit-bindgen
but there is one value in the generated js bindings that I have to hardcode, (a string length specifically) because for some reason it has a different value on the guest side otherwise, but other than that, validations are working when passing logs from the browser. Hope to figure that out soon.
warg-protocol
already pulls in warg-transparency
so your wrapper crate should be able to also perform any operations on proofs/proof bundles that you need. I think it's fine to call the proof functions from your wrapper and also in the client.
Last updated: Dec 23 2024 at 13:07 UTC