Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

template(comet): lower mempool.max_tx_bytes from 1MiB to 30KiB #4632

Merged
merged 1 commit into from
Jun 17, 2024

Conversation

dynst
Copy link
Contributor

@dynst dynst commented Jun 17, 2024

Describe your changes

Set the individual transaction size limit to be smaller than the entire block size, but to a still lax, permissive value.

Issue ticket number and link

#4629

Checklist before requesting a review

  • If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

    the mempool is outside consensus; and this only edits a template file

@conorsch
Copy link
Contributor

Merging to land the config change, will follow up with migration scripting in #4614.

@conorsch conorsch merged commit 958a6a9 into penumbra-zone:main Jun 17, 2024
13 checks passed
conorsch added a commit that referenced this pull request Jun 28, 2024
During team sync today we decided that this new value is superior.

Follow-up to related work in #4614, #4627, and #4632.
conorsch added a commit that referenced this pull request Jun 28, 2024
During team sync today we decided that this new value is superior.

Follow-up to related work in #4614, #4627, and #4632.
erwanor pushed a commit that referenced this pull request Jun 28, 2024
## Describe your changes
During team sync today we decided that this new value is superior.



## Issue ticket number and link
Follow-up to related work in #4614, #4627, and #4632.

## Checklist before requesting a review

- [x] If this code contains consensus-breaking changes, I have added the
"consensus-breaking" label. Otherwise, I declare my belief that there
are not consensus-breaking changes, for the following reason:

> This change does affect consensus and so should be treated carefully.

Co-authored-by: Conor Schaefer <conor@penumbralabs.xyz>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants