docs: clarify outdated code comments - #6914
Open
GrothenDI wants to merge 1 commit into
Open
Conversation
Clarify trigger behavior, log retention, Solidity API availability, and account-name rules.
GrothenDI
marked this pull request as ready for review
August 13, 2026 01:03
bombaycubza-svg
approved these changes
Aug 13, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What does this PR do?
Clarify several outdated or ambiguous comments across event triggers, Solidity HTTP APIs, log retention, and account-name rules.
Why are these changes required?
The existing comments no longer match the configured behavior or current Mainnet rules. Updating them makes the code easier to understand without changing runtime behavior.
This PR has been tested by:
./gradlew :framework:checkstyleMain :protocol:protoLintgit diff --checkFollow up
None.
Extra details
This is a documentation-only change with no runtime impact.