Error on finalized flag for `/eth/v2/beacon/blocks/{block_id}` about prysm

[rkapka]

Hi @ignaciofd , I am currently working on a solution for this because I agree it shouldn't work like this.

[rkapka]

Hi @ignaciofd , I did some digging into our codebase and this behavior is expected if the block is from the last finalized epoch.

Note: beacon blocks from the latest finalized epoch return true, whether or not they are considered canonical in the "head view" of the beacon node.

After the next epoch finalizes, you should get a 404.

[ignaciofd]

Thank you very much for the reply. However, this does not seem to be good behaviour since the finalized field is not telling if a slot is final or not which I assumed was the intention of the field. Now I know that I should not take into account that flag and I need to reconstruct the chain to filter out the forks.