fix: remove EXTRA_DATA_MAX_SIZE limit
#225
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix: update `EXTRA_DATA_MAX_SIZE` limit
chore: remove `EXTRA_DATA_MAX_SIZE` limit
rjan90
changed the title
EXTRA_DATA_MAX_SIZE limitEXTRA_DATA_MAX_SIZE limit
rvagg
approved these changes
Oct 20, 2025
github-project-automation
bot
moved this from 🔎 Awaiting review
to ✔️ Approved by reviewer
in FS
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #224
This PR removes the
EXTRA_DATA_MAX_SIZElimit on extraData across all PDPVerifier functions, implementing option 1 from the discussion in #224.Background
The current 2KB limit is insufficient for handling multiple pieces and KVs (Key-Values). After discussion in the daily sync, we aligned on removing the limit entirely since: