-
Notifications
You must be signed in to change notification settings - Fork 226
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
closes: #10992 ## Description `SeenTxs` is currently all transactions ever seen by the contract, but we don't want it to grow without bound. Eventually we'll want to prune old transactions and will need a way of seeing how old each entry is. This turns the set of `txHash` keys into a map in which the value is the `blockTimestamp`. That provides the necessary data for a contract upgrade to add functionality to delete old entries. The doc comment says, "*ever* seen" which is currently accurate. Later it will be a subset of what was ever seen. For this reason I think the store name, "SeenTxs", is still appropriate even if in the future it won't be all of them. ### Security Considerations none ### Scaling Considerations No real additional IAVL costs because the SetStore uses a sentinel value anyway. Definite net win soon by making pruning possible. ### Documentation Considerations none ### Testing Considerations CI suffices ### Upgrade Considerations Not yet deployed. If it were, this would fail an upgrade test.
- Loading branch information
Showing
11 changed files
with
1,803 additions
and
15 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.