Repository navigation
Conversation
Recognize ALLOW_OPTIMIZE_TVM_STORAGE_KEY after fork 4.8.2.4, activate its own dynamic property, and expose it in node APIs. Match java-tron storage behavior: 99 or 102 selects optimized keys, while 102 protects aliased legacy reads with OUT_OF_TIME and leaves read-only legacy rows unmigrated. Cover proposal validation/activation, old and new storage layouts, alias protection, dirty/zero writes, and the RPC parameter list.
zhenkas
changed the title
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
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.
Recognize ALLOW_OPTIMIZE_TVM_STORAGE_KEY after fork 4.8.2.4, activate its own dynamic property, and expose it in node APIs. Match java-tron storage behavior: 99 or 102 selects optimized keys, while 102 protects aliased legacy reads with OUT_OF_TIME and leaves read-only legacy rows unmigrated.
Cover proposal validation/activation, old and new storage layouts, alias protection, dirty/zero writes, and the RPC parameter list.