feat!: URI-based proof payload locations with blob publication verification#39
Open
mfw78 wants to merge 1 commit into
Open
feat!: URI-based proof payload locations with blob publication verification#39mfw78 wants to merge 1 commit into
mfw78 wants to merge 1 commit into
Conversation
25 tasks
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.
Proof { string[] uris; bytes32[] blobVersionedHashes }replaces the numeric location registry: URI mirrors are opaque on-chain; every listed blob hash is verified attached to the transaction viablobhash()(BlobNotAttached) — publication atomic with authorizationsetRoot(bytes32(0))is an explicit clear and requires an empty proof (ProofDataMalformed)leafEncoding: "v1"tree-construction vectors: independent implementation verified against the exactMerkleProof.verifycheck_authperforms, including odd-promotion levels (note: the Murky test helper zero-pads odd nodes —_auth-valid but not the payload standard, which is exactly why the construction is pinned)BREAKING:
setRoot/setRootWithContextsignatures andMerkleRootSettopic0 change.Part of #1. Closes #33.