Conversation
karlem
changed the title
cryptoAtwill
reviewed
Jun 3, 2025
Contributor
cryptoAtwill
left a comment
cryptoAtwill
left a comment
There was a problem hiding this comment.
@karlem is it possible to add a comment or doc somewhere explaining what happens to circulation for different msg kind, especially if it is a result message of a failed execution.
Contributor
Author
|
@cryptoAtwill not sure what you mean. Given the PR makes all messages equal. Can you explain? |
Contributor
|
@karlem I misunderstood, it should be fine. |
cryptoAtwill
approved these changes
Jun 3, 2025
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
2 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.
Prevent xnet call messages with non-zero value from inflating child subnet circulating supply