are the fields in chain_reorg event response reversed?

[hwhe]

Describe the bug

I use this cmd curl http://ip:port/eth/v1/events?topics=chain_reorg to listen for events from prysm node. J I'm a little confused about the response.

event: chain_reorg
data: {"slot":"8969720","depth":"2","old_head_block":"0xb5e227e007f2c091af70f9256923b53d95f218f8620cb754ffceb53b4a559a64","old_head_state":"0xd2f0fc145245295dbd8f6fcf2dc0bf6e8a97a10d8a9d8393a06401a8efde6ffd","new_head_block":"0xa49517e908c18a949bc580b37175c5efa7a6a003e6eed81aa841722ae8561852","new_head_state":"0x2a83e6b60f1cce7a307abeb7e08b907963162963780a5c5b86f22d9a559f6bae","epoch":"280303","execution_optimistic":false}

event: chain_reorg
data: {"slot":"8970120","depth":"2","old_head_block":"0xe26e7a7b98ec77279216b08916be22d1e4714e26a6198d7f70b41c194a29d6a6","old_head_state":"0x6b6728284cf37bf2e85cdce073676e2c846a4ca814186cbd51f659a25e6e1ef7","new_head_block":"0x0ec08fad03438a929394bc7804cac44cd3bb6f2b4cbb86515f27d57f7a7ff32c","new_head_state":"0x711efae7c94e3a75cea3b753430ce933514313f374b2af2f92b2beca88e0cf2e","epoch":"280316","execution_optimistic":false}

It feels like old_head_state and new_head_block are reversed. Is there a bug in the logic. Or did I misunderstand?

Has this worked before in a previous version?

Didn't pay much attention.

🔬 Minimal Reproduction

No response

Error

No response

Platform(s)

Linux (x86)

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

v5.0.0

Anything else relevant (validator index / public key)?

No response

[rkapka]

Hi @hwhe , I don't see anything wrong in the code. Can you provide more details why you think the field values are reversed?