-
Notifications
You must be signed in to change notification settings - Fork 46
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
Fix: update OFAC filename #266
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -154,5 +154,8 @@ | |
"0xfac583c0cf07ea434052c49115a4682172ab6b4f", | ||
"0xfd8610d20aa15b7b2e3be39b396a1bc3516c7144", | ||
"0xfec8a60023265364d066a1212fde3930f6ae8da7", | ||
"0xffbac21a641dcfe4552920138d90f3638b3c9fba" | ||
"0xffbac21a641dcfe4552920138d90f3638b3c9fba", | ||
"0xc5801cd781d168e2d3899ad9c39d8a2541871298", | ||
"0x0992E2D17e0082Df8a31Bf36Bd8Cc662551de68B", | ||
"0x8aa07899eb940f40e514b8efdb3b6af5d1cf7bb" | ||
Comment on lines
+157
to
+160
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Codebase verification Invalid Ethereum address format detected The address
🔗 Analysis chainVerify the newly added addresses. The following addresses have been added:
Please ensure these addresses are from official OFAC sources. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Verify the format of the newly added Ethereum addresses
# Test: Check if all addresses are valid Ethereum addresses (40 hex chars)
for addr in "0xc5801cd781d168e2d3899ad9c39d8a2541871298" "0x0992E2D17e0082Df8a31Bf36Bd8Cc662551de68B" "0x8aa07899eb940f40e514b8efdb3b6af5d1cf7bb"; do
if ! echo "$addr" | grep -qE "^0x[0-9a-fA-F]{40}$"; then
echo "Invalid address format: $addr"
fi
done
# Test: Check if addresses are unique in the file
rg -c "$addr" injective_data/ofac.json client/chain/injective_data/ofac.json
Length of output: 1012 |
||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Update local filename to match remote OFAC list source
The verification confirms that there is an inconsistency between the remote source (
ofacAndRestricted.json
) and local storage (ofac.json
). The code downloads fromDefaultOfacListURL
and saves locally usingOfacListFilename
. This mismatch should be fixed to maintain consistency and prevent confusion.client/chain/ofac.go
: UpdateOfacListFilename
fromofac.json
toofacAndRestricted.json
to match the source URL🔗 Analysis chain
Verify consistency between URL and local filename
The URL has been updated to fetch "ofacAndRestricted.json", but the local
OfacListFilename
variable still uses "ofac.json". This inconsistency could lead to confusion and potential issues.Apply this diff to maintain consistency:
Let me gather more information about how this filename is used in the codebase to understand the potential impact.
Let me check how the OFAC list is actually loaded and used to understand if this filename mismatch could cause issues.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 1226
Script:
Length of output: 640
Script:
Length of output: 707