Skip to content

Review peer scoring impact of partial messages #447

Description

@lucassaldanha

Scope split

MVP (in scope here):

  • Wire the PartialMessagesPeerFeedback.reportFeedback(topic, peer, kind) side-channel into the existing gossip scoring infrastructure.
  • INVALID feedback hooks into notifyRouterMisbehavior (the same path used by the existing v1.3 Control-Extensions handshake penalty).
  • USEFUL / IGNORED feedback: decide whether these should affect score, or remain informational for now. Lean informational for MVP unless evidence suggests otherwise.

Deferred (post-MVP, pending spec guidance):

  • Defining partial-message-specific scoring rules (spec is currently silent; go-libp2p also does not score partial-message traffic).
  • Penalties for protocol-level misbehaviour specific to partial messages (e.g. inconsistent metadata, metadata regression, excessive metadata-only spam).

Revisit once the libp2p spec adds scoring guidance or we see concrete interop issues.

Reference

Design: docs/partial-messages.md §4.4, §7.2 (lands with the first PR on #435).
go-libp2p: no partial-specific scoring in score.go at the reference pin.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions