feat: cargo axiom prove --deferred-proof for deferral jobs - #185
Merged
Conversation
A deferral submission is multipart/form-data on the same POST /proofs
endpoint: the 'input' form field carries the JSON body string and each
--deferred-proof file becomes a child_proofs file part (flag order =
circuit packing order). Plain submissions keep the JSON body byte-for-byte.
Files must be the openvm-codec encoding (VersionedVmStarkProof::
encode_to_vec); the API rejects JSON parts, so the CLI sniffs '{'-leading
files and fails before uploading megabytes, with conversion instructions.
A codec stream's leading bytes are the version-string length prefix and
can never be '{' (unit-tested).
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
1 participant
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.
A deferral submission is multipart/form-data on the same POST /proofs endpoint: the 'input' form field carries the JSON body string and each --deferred-proof file becomes a child_proofs file part (flag order = circuit packing order). Plain submissions keep the JSON body byte-for-byte.
Files must be the openvm-codec encoding (VersionedVmStarkProof:: encode_to_vec); the API rejects JSON parts, so the CLI sniffs '{'-leading files and fails before uploading megabytes, with conversion instructions. A codec stream's leading bytes are the version-string length prefix and can never be '{' (unit-tested).