You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering if a better implementation strategy might be to have the script do two passes: first, to look for <FeatureType/> starting with "Digital Currency Address - ", to build up the list on lines 13-15, and, second, to proceed as usual. of course, i'd still keep what's on lines 13-15, just as a safety.
Your thoughts?
The text was updated successfully, but these errors were encountered:
I'm not actively monitoring for new coins being added to the SDN list - for me personally, only XBT is relevant. However, I accept PRs (#7, #6) to add new coins and will review and merge them.
As the CI is already running each night to check if there are new entries for the existing coins, there could also be a job that runs after uploading potential new entries - failing or otherwise alerting that there are new coins. Happy to create an issue for each new coin when the CI fails. Someone (not necessarily me, but I might do it if I have the time) can then create a PR to add the new coin.
My guess from reading https://github.com/0xB10C/ofac-sanctioned-digital-currency-addresses/blob/main/generate-address-list.py#L12 is that someone periodically fetches the XML file, does a grep and then compares that to the list at https://github.com/0xB10C/ofac-sanctioned-digital-currency-addresses/blob/main/generate-address-list.py#L13-L15
I am wondering if a better implementation strategy might be to have the script do two passes: first, to look for
<FeatureType/>
starting with "Digital Currency Address - ", to build up the list on lines 13-15, and, second, to proceed as usual. of course, i'd still keep what's on lines 13-15, just as a safety.Your thoughts?
The text was updated successfully, but these errors were encountered: