compliance: compliance-server: Fallback to chainalysis API if not cached #3
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
joeykraut
force-pushed
the
joey/chainalysis-api
branch
from
772fd48
to
145b57b
Compare
akirillo
approved these changes
Jun 29, 2024
compliance/compliance-server/migrations/2024-06-28-231756_create_compliance_table/up.sql
Show resolved
Hide resolved
joeykraut
force-pushed
the
joey/chainalysis-api
branch
from
145b57b
to
2b08225
Compare
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.
Purpose
This PR implements the fallback to using the chainalysis API in the case that a wallet's risk assessment is not cached in the DB. If chainalysis delivers a successful risk assessment, we then insert it into our DB.
Testing