Skip to content

Create Light Client Update SSZ Responses based on Attested Header Slot and not Signature Slot #7167

Closed
@Inspector-Butters

Description

@Inspector-Butters

The Fork Digest context in SSZ response for the /light_client/update endpoint is using signature_slot as it's source for calculation and not the update.attested_header.beacon.slot that the beacon API spec mentions.

This line in lighthouse.

Beacon API doc

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