Skip to content

limit number of attestation data in blocks#536

Merged
anshalshukla merged 1 commit intoleanEthereum:mainfrom
anshalshukla:anshalshukla/max-attestation-data
Apr 8, 2026
Merged

limit number of attestation data in blocks#536
anshalshukla merged 1 commit intoleanEthereum:mainfrom
anshalshukla:anshalshukla/max-attestation-data

Conversation

@anshalshukla
Copy link
Copy Markdown
Collaborator

🗒️ Description

🔗 Related Issues or PRs

✅ Checklist

  • Ran tox checks to avoid unnecessary CI fails:
    uvx tox
  • Considered adding appropriate tests for the changes.
  • Considered updating the online docs in the ./docs/ directory.

Copy link
Copy Markdown
Collaborator

@tcoratger tcoratger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess a bunch of tests are failing because we have more than 8 attestations in those tests.

Where does the 8 come from? This looks super small and restrictive no?

@anshalshukla anshalshukla force-pushed the anshalshukla/max-attestation-data branch from 849d311 to 8535142 Compare April 8, 2026 16:49
@anshalshukla anshalshukla force-pushed the anshalshukla/max-attestation-data branch from 8535142 to 0d86ee9 Compare April 8, 2026 16:57
@anshalshukla
Copy link
Copy Markdown
Collaborator Author

Where does the 8 come from? This looks super small and restrictive no?

It's random value, I've increased it to 16. I think this number roughly denotes the number of network fractions we have with the given justified slot, on a stable network where every validator is attesting every slot 16 should be more than enough but I'm to increasing this as well.

cc: @g11tech

@g11tech
Copy link
Copy Markdown
Contributor

g11tech commented Apr 8, 2026

Where does the 8 come from? This looks super small and restrictive no?

It's random value, I've increased it to 16. I think this number roughly denotes the number of network fractions we have with the given justified slot, on a stable network where every validator is attesting every slot 16 should be more than enough but I'm to increasing this as well.

cc: @g11tech

increasing beyond 16 doesn't make sense, beacon consensus has it capped at 8, for the validity of the test suite we can have 16 for now, else we should target it 8 (and lets make an issue for this so that we dont forget this)

its best to make it a config.yaml value, which clients can pick and we can use 16 here for testcases and use 8 for our networks

@g11tech
Copy link
Copy Markdown
Contributor

g11tech commented Apr 8, 2026

why 8? because if majority to the newwork agrees, it will have same attestation data (1) and other 7 are good enugh to pack previous slot votings which arrived late and/or branches

(its common that some 3-4% of validators get their attestations included a slot later than the next slot in which they are expected to be packed because of timing games) giving this number from my estimates of running a mainnet beacon node where block comes with delay 3-4% of times

@anshalshukla anshalshukla added this to the pq-devnet-4 milestone Apr 8, 2026
@anshalshukla anshalshukla merged commit 0c9528a into leanEthereum:main Apr 8, 2026
24 of 25 checks passed
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.

3 participants