Skip to content

should be able to get non-canonical blocks #16342

@potuz

Description

@potuz

Describe the bug

My node received this block, it has it in db, getting it by hash should work

curl -s localhost:3500/eth/v2/beacon/blocks/0xf3a1ad5ac0c6012835a0683ea42def591836451de7b9578213e9125b9dfc496e
{"message":"could not reconstruct full execution payload to create signed beacon block: failed to build full block from execution payload for block hash 0xa945d94a103b4070bbc8b5e1d186eea27457cf8b0742d20b802a0da5b1f712b3: payload 0xffd3072453ada1084c370d75a6de5b4a1dad1962de4fe547ef55a09caea51c17 and header 0xd4bfdc29a20c14688c5afbe2d8180496e757a068a277df1afaee18907d0cb05b roots do not match","code":400}

Has this worked before in a previous version?


🔬 Minimal Reproduction

No response

Error


Platform(s)

No response

What version of Prysm are you running? (Which release)

No response

Anything else relevant (validator index / public key)?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions