-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blocking crypto currency algorithms #362
Comments
@adamdecaf I would like to help out with this. Could you assign it to me? I won't be able to jump on it immediately but am keen to help build out the lists |
@mauriceLC92 Sure! Can you design the endpoint(s) or brainstorm a design? I've got a rough idea in my head, but curious what you're thinking. |
Hey @adamdecaf I reached out to you via your email that I found on your site (gmail). Can we pick up comms there about logistics before discussing design? |
BTW - https://github.com/0xB10C/ofac-sanctioned-digital-currency-addresses/ is an example script that can scrape them from OFAC |
@michaelneale Do you know of other sanction lists with crypto currency addresses included? |
@adamdecaf not off hand, only in the advanced xml of sanctions OFAC: https://github.com/0xB10C/ofac-sanctioned-digital-currency-addresses/?tab=readme-ov-file#ofac-sanctioned-digital-currency-addresses |
I see it in sdn_comments.csv which is where we're pulling from currently. |
v0.28.0 of Watchman adds a Are there other lists that people would like crypto addresses pulled from and made available in search? Edit: Found one on OpenSanctions - https://www.opensanctions.org/search/?datasets=ransomwhere&schema=CryptoWallet&scope=default |
I wasn't able to find any on a quick search. Lots of mentions of sanctioned wallets etc - but seems either OFAC or case by case for now. |
Often crytpocurrencies have addresses which should be blocked. This can be for various reasons (deny transactions against Satoshi's addresses, block terrorists, randomware, etc).
Could watchman offer such lists?
Examples:
The text was updated successfully, but these errors were encountered: