[TOB] DEV-3794: Timestamp Attestations for Collaterals #23
Conversation
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
Merged
preston4896
changed the title
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
preston4896
force-pushed
the
development
branch
from
33baea4 to
838a536
Compare
|
This issue has been labelled as fully resolved by TOB. cc @Liao1 |
Liao1
approved these changes
Feb 28, 2025
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.
This PR adds an entry to store the validity timestamps (
issueDatevsnextUpdate, or similar terms) for all collaterals.All DAOs now have the
getCollateralValidity()method that can be called by a reader to quickly determine the expiration status of the corresponding collateral, by providing the indexing key of the collateral.This PR also partially addresses issue ID-5 regarding CRL expiration check.