Repository navigation
Fuzz verify and the address overview; fix three doc inaccuracies - #61
Merged
Merged
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.
Findings of an independent audit of the docs against the code.
verify_txandget_address_overviewwere not in the arbitrary-JSON target. Both are now. Half of theverifyruns get API answers that agree with each other (the header commits to the Merkle root, the status names the header's hash), so every check up to proof of work is reached, not only the first ones. Locally: about 0.9M runs of the final harness with no crash; replaying the corpus shows verify reaching the proof-of-work checks.1for an unconfirmed transaction applies toverifyonly (txshows it as unconfirmed and exits0).test (3.x)).No change to the package code.