Add logic to output ofac-sanctioned-digital-currency-addresses.json #81
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.
Generates a new file
ofac-sanctioned-digital-currency-addresses.json
, that looks like this:It's just a flat list of addresses to not send transfers to, and includes every coin type (e.g. bitcoin, EVM, and Solana addresses are all included in the one array).
The list is generated by parsing the
lists
branch of this repo https://github.com/brave-intl/ofac-sanctioned-digital-currency-addresses/tree/lists. That repo has a daily job that scrapes the digital currency addresses from the OFAC website, and outputs them insanctioned_addresses_*.json
files at the top level of the github repo.In order to fetch those files from our github repo, the code in this change uses the github API, which requires an authentication token
GITHUB_TOKEN
, which must be added as an environment variable to this repo.That list is parsed clientside and checked prior to regular transfers and token transfers in brave-core in this pull request.
Security review - https://github.com/brave/reviews/issues/1273.