Fix proof field forging for reveal #391
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
A proof field has been introduced in the protocol Seoul. Its encoding is described here: https://gitlab.com/tezos/tezos/-/blob/octez-v23.0/src/proto_023_PtSeouLo/lib_protocol/operation_repr.ml#L686 If proof is required: - A `ff` tag (True) need to be added in the same way as the `00` tag (False) is added if proof is absent. - A 4-bytes size representing the size of the proof is need.
spalmer25
changed the title
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.
Context
A proof field has been introduced in the protocol Seoul.
Its encoding is described in tezos/tezos
I may wrongly understand how forging are handled in pytezos, but the
prooffield seems wrongly encoded inforge_revealSolution
fftag (True) need to be added in the same way as the00tag (False) is added if proof is absent.