Skip to content

[Research] Check if node can handle spam correctly #175

Open
@MegaRedHand

Description

@MegaRedHand

Other implementations (lighthouse and prysm, at least) use different types of queues (i.e. FIFO, LIFO) for inter-"process" communication. This enables them to prioritize, for example, newer attestations and older slashing. Since the BEAM handles all of the message passing, we should check (in the future) if its queues (and maybe also libp2p's):

  • drop messages when full (and if the how it's configurable)
  • fill quicker than we process messages
  • the order in which the messages are received (FIFO or LIFO), and if it's configurable

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs elaborationThis is an idea or reminder, but it's very broad or non-specific.questionFurther information is requested

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions