[Fortune][Exchange Oracle] Implement caching for public key retrieval in JwtHttpStrategy - #3371
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 5 Skipped Deployments
|
Dzeranov
approved these changes
May 29, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue tracking
None
Context behind the change
Before this change, every authentication request triggered a call to the KVStore to fetch the public key, causing unnecessary network traffic.
Now, an in-memory cache with a 1-day expiration has been added in JwtHttpStrategy, so the public key is only fetched from KVStore once per day per address, significantly reducing redundant requests and improving performance.
How has this been tested?
Deployed locally and made some requests to see if cache works
Release plan
None
Potential risks; What to monitor; Rollback plan
None