investigate the access witness issue #82
Closed
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
When creating the proof, the values that find themselves in the access witness are wrong, they correspond to a state later than that of the post state. For example, in
TestProcessStateless, a comparison of the first block's prestate with that of the access witness show:Analysis
There are several bugs here:
nil, but sincenilisn't recognized as a value, it is replaced with00000000000000000000000000000000000000000000000000000000000000001000000000000000000(000064a7b3b6e00din little endian hex form), but the first value that is inserted is0043fdd2679be00d, which is little-endian hex for999969987500000000. That is an incorrect value, which probably comes from the fact that this is the sender account and that the sending costs is charged before the account witness is created.