Skip to content

[TOB] DEV-3794: Expiry Check on collateral reads via PCCSRouter #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 28, 2025

Conversation

preston4896
Copy link
Collaborator

@preston4896 preston4896 commented Feb 10, 2025

Changes made in this PR:

  • PCCS Router checks expiration of all collateral reads.
  • For full collateral data reads, block.timestamp is used.
  • For collateral hash reads, the user has the option to either use block.timestamp or with a specified timestamp by calling *withTimestamp() methods.
  • verifyAndAttestWithZKProof no longer bypasses the timestamp value provided in the Output data. timestamp is then passed onto *withTimestamp() methods to check the expiration status of corresponding collaterals.

This PR partially addresses issue ID-5.

@preston4896 preston4896 mentioned this pull request Feb 13, 2025
@preston4896 preston4896 marked this pull request as ready for review February 13, 2025 06:53
@preston4896 preston4896 changed the title DEV-3794: Expiry Check on collateral reads via PCCSRouter [TOB] DEV-3794: Expiry Check on collateral reads via PCCSRouter Feb 13, 2025
@preston4896 preston4896 changed the base branch from main to development February 18, 2025 06:36
@preston4896
Copy link
Collaborator Author

This issue has been labelled as fully resolved by TOB. cc @Liao1

@preston4896 preston4896 requested a review from Liao1 February 27, 2025 07:50
@preston4896 preston4896 merged commit 2470ce7 into development Feb 28, 2025
4 checks passed
@preston4896 preston4896 deleted the DEV-3794 branch February 28, 2025 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants