[oracle] add timestamp to oracle exchange rates #1073
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.
Describe your changes and provide context
This adds
last_update_timestamp
to the data stored for exchange rates. This allows for calculating stalesness of oracle prices based on timestamp for use by smart contracts.For this change, no migration is necessary because we don't have the tiemstamps of previously updated oracle prices available, and the timestamp will only be present as 0 for one oracle window prior to the next oracle update. There won't yet be contracts reading that values until after the timestamps have been established.
Testing performed to validate your change
Updated unit tests + verified compatibility for existing cosmwasm version + verified compatibility with updated sei-cosmwasm struct to have the timestamp field.