Skip to content

Consensus: Peer Stats on Faulty Behavior #6118

@alexanderbez

Description

@alexanderbez

Summary

ref: #5969 (review)

I guess the only qualm I have is that we have two stats that we use to keep track of peer behavior (votes and blocks) but the peer manager is never informed when anything bad happens i.e. invalid proposal or invalid vote.

While the peer manager and scoring system is still, at this moment, being fleshed out, we should consider if it is worthwhile to introduce stats, and as a result, peer updates to adjust peers scores when a given peer sends an invalid proposal or vote.

Currently, we only track "good" behavior and not any "bad" behavior.

/cc @cmwaters @ebuchman @brapse @melekes


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned

Metadata

Metadata

Assignees

No one assigned

    Labels

    C:consensusComponent: ConsensusS:proposalStatus: Proposalstalefor use by stalebot

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions