refactor!: use chainhook to listen for chain events instead of a direct stacks api connection #200
Conversation
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
|
Vercel deployment URL: https://token-metadata-rmwxyxke0-hirosystems.vercel.app 🚀 |
This was
linked to
issues
Mar 3, 2024
rafaelcr
changed the title
Codecov ReportAttention: Patch coverage is 📢 Thoughts on this report? Let us know! |
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 replaces the direct connection between this API and the Stacks Blockchain API DB with a Chainhook predicate that feeds every Stacks block for analysis. This API then checks for token contract deployments, metadata notifications, and token mints in order to fetch their metadata.
Also:
ON DELETE CASCADEto related tables for re-org (chainhook rollback) managementThis PR significantly changes the DB schema so it represents a breaking change.