Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report malice on sibling blocks from the same validator #196

Merged
merged 4 commits into from
Oct 22, 2019

Commits on Oct 21, 2019

  1. Aura: Report malice on sibling blocks from the same validator

    This was originally written by @vkomenda, then squashed for
    easier rebasing on master. Cleanup of `received_step_hashes`
    was moved to `verify_block_family`, since `on_prepare_block`
    does not exist on master, and a unit test was added.
    Original commit messages:
    
    added the map of received block header hashes
    
    do not return an error and remove older received block records
    
    optimised older record removal
    
    block hash comparison optimisation and the weak client ref fix
    
    SIBLING_MALICE_DETECTION_PERIOD constant
    
    review comments
    
    using step numbers instead of block numbers
    vkomenda authored and afck committed Oct 21, 2019
    Configuration menu
    Copy the full SHA
    4e4a077 View commit details
    Browse the repository at this point in the history
  2. Add docs; use map_or.

    afck committed Oct 21, 2019
    Configuration menu
    Copy the full SHA
    4e1e383 View commit details
    Browse the repository at this point in the history
  3. Update step hash record comment.

    Co-Authored-By: David <[email protected]>
    afck and dvdplm committed Oct 21, 2019
    Configuration menu
    Copy the full SHA
    45c5d53 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    f23133f View commit details
    Browse the repository at this point in the history