Limit blockchain payload size #1282
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
neekolas
approved these changes
Oct 30, 2025
Base automatically changed from
mkysel/remove-BlockUntilDesiredCursorReached
to
main
October 30, 2025 18:39
b45ae06 to
d827b28
Compare
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.
Enforce a 200000-byte blockchain payload limit by adding
payer.Service.maxPayerMessageSizeand validating inpayer.Service.PublishClientEnvelopesAdd a configurable max payload size for blockchain-bound messages and validate message bytes in
payer.Service.PublishClientEnvelopes, wiring the limit from config and updating constructors and tests to pass the new parameter.📍Where to Start
Start with the validation in
payer.Service.PublishClientEnvelopesin service.go, then review the new config option in options.go and the constructor changes in builder.go.📊 Macroscope summarized d827b28. 4 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted
🗂️ Filtered Issues
No issues evaluated.