feat: cache spot metadata in database to reduce API calls #105
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
Implements persistent caching of ERC20 contract address to spot token ID mappings in the database to minimize API requests and improve performance. Changes: - Add SpotMetadata database table for persistent storage - Implement load_spot_metadata_cache() to initialize cache on startup - Add init_spot_metadata() for init-state command to pre-populate cache - Extract store_spot_metadata() helper to DRY serialization logic - Enable on-demand API fetches with automatic database persistence - Integrate cache loading in main node startup flow The cache falls back to on-demand API fetches if database is empty, with automatic persistence of fetched data for future use.
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.
Resolves #72
Implements persistent caching of ERC20 contract to spot token mappings to minimize API requests and improve performance.
Changes:
Falls back to on-demand API fetches when database is empty, with automatic persistence for future use.