Skip to content

Clarify validator custody with PeerDAS #4182

@ralexstokes

Description

@ralexstokes

The validator custody requirements spec should be clear that:

  1. the beacon node automatically detects the required custody based on any attached validators, without any input from the user

  2. the beacon node should respond to changes in the amount of stake associated with any attached validators (again without any input from the user)

Exact implementations can be omitted, but adding the above points will help ensure the soundness of this part of PeerDAS.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions