feat(examples): add Base64 decoding async example#2860
Open
Amit5601 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The
examplesdirectory currently lacks a Base64 decoding implementation. Base64 is a highly common data encoding format in Web3 and cryptography, making it a valuable reference for developers learning how to serialize, deserialize, and process string data across the Host/Guest zkVM boundary.Solution
Implemented an end-to-end Base64 decoding execution pipeline.
Implementation Details:
program): Implemented standard Base64 decoding logic inside the zkVM, ensuring it successfully cross-compiles to the newriscv64im-succinct-zkvm-elftarget.script): Upgraded the host implementation to align with the latest async architecture, utilizingProverClient::from_env().await, the updatedProvingKeyverification traits, and thesp1_sdk::Elf::Static()wrapper.Note on testing: The Rust logic and Host/Guest serialization compile flawlessly with 0 errors/warnings. My local hardware hits an OOM memory limit when attempting to generate the execution trace matrix locally via
.execute()or.prove(), so I am relying on the CI/CD pipeline to generate the final execution/proof verification.PR Checklist