fix: last updated setting in x/marketmap
keeper
#799
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.
Closes CON-1839
SetLastUpdated
for anySet
orRemove
calls in the keeper. (previously these calls were only done during the MsgServer which meant that hooks, or any keeper calls that are not part of a MsgServer call were not updating LastUpdated)LastUpdated
field. Use randomized blockheights instead of constantsNote, this fix is only for on-chain code, so a full upgrade would be needed. This is also state-breaking, so we will need to make a new
v3.x
release as anyv1
orv2
version of the code will result in disparate states (last updated will be updated differently).I will make another PR that will only updates the sidecar, which can be rolled out more quickly.