Skip to content

fix: getPoolAttestationsV2 should return an empty array when no attestations are available#9675

Open
markolazic01 wants to merge 3 commits into
ChainSafe:unstablefrom
markolazic01:fix/aggregated-attestation-return
Open

fix: getPoolAttestationsV2 should return an empty array when no attestations are available#9675
markolazic01 wants to merge 3 commits into
ChainSafe:unstablefrom
markolazic01:fix/aggregated-attestation-return

Conversation

@markolazic01

Copy link
Copy Markdown
Contributor

Motivation

Initially this endpoint returned 500 when there are no attestations for a specified slot, instead it should return an empty list.

Description

Simple single-line change replacing 500 with an empty array return - as described in the issue itself.

Closes #9669

@markolazic01
markolazic01 requested a review from a team as a code owner July 17, 2026 21:39
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@markolazic01 markolazic01 changed the title fix: getPoolAttestationsV2 should return an empty array when no attestations are available fix: getPoolAttestationsV2 should return an empty array when no attestations are available Jul 17, 2026
@nflaig

nflaig commented Jul 18, 2026

Copy link
Copy Markdown
Member

did you double check against the spec? I am not sure this is correct, I feel like the issue that lodekeeper reported is due to the fact that we cannot serve attestations from pool which we should in that case. for some context, vouch queries to pool to determine whether the main instance is active or not, so the hot standby can be activated. I would need to dig more into why we returned 500 in the first place so the pool should have an attestation since the vouch instance itself submitted it. anyhow this doesn't really fix the root cause

@markolazic01

Copy link
Copy Markdown
Contributor Author

got it, I added this only as I started inspecting the topic, returning 500 seemed wrong so I went with it (seems spec aligns with using 500 only for when internal errors occur).
there is a separate issue created which focuses on the root cause of this #9677.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

getPoolAttestationsV2 returns 500 instead of empty list when pool has no attestations for slot

3 participants