Mention mempool chain limits in release notes #7367
Merged
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.
A user reported an issue with bumping into the chain limits in 0.12 on IRC this evening, and I realized that we don't seem to mention these new policy limits in the release notes.
I wasn't sure exactly what to say here, as we apparently decided to hide the command line options for changing these values as a help-debug option, and even phrasing the exact limits is a bit tedious and technical, so I figured I'd just highlight the main idea of the limits and not explain exactly how they're implemented or how exactly you'd change them (ie with separate ancestor and descendant limits).