Skip to content
This repository was archived by the owner on May 22, 2024. It is now read-only.
This repository was archived by the owner on May 22, 2024. It is now read-only.

Pyrmont scenario testing #59

@djrtwo

Description

@djrtwo

Now that the Altair fork is complete and stable on Pyrmont, we are inducing a number of behaviors on the soon-to-be-deprecated Pyrmont.

The following list are the low hanging fruit. Feel free to do additional tests.

  • Operations (many of each)
    • Validator deposit
    • Validator exit
    • Proposer slashing [1000 completed]
    • Attester slashing (double)
    • Attester slashing (surround)
  • Sync committees
    • Produce (valid) block with empty sync committee
  • Sync (for each client)
  • Stress
    • Turn off 50% of nodes, observe non-finality, turn them back on, observe finality [completed]
  • Bad network data
    • Gossip invalid blocks
    • Gossip invalid attestations

Original doc

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions