Merge pull request #3164 from Marcofann/fix/fix

chore: Standardization of Security Check Identifiers across GoPlus plugin
elizaOS · Feb 3, 2025 · 1ec365f · 1ec365f
2 parents 23ffbd4 + b3b7ccc
commit 1ec365f
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/packages/plugin-goplus/README.md b/packages/plugin-goplus/README.md
@@ -68,7 +68,7 @@ The plugin supports various networks including:
 - `APPROVAL_SECURITY_CHECK`: Smart contract approval analysis
 
 ### Account & Address Security
-- `ADRESS_SECURITY_CHECK`: Malicious address detection
+- `ADDRESS_SECURITY_CHECK`: Malicious address detection
 - `ACCOUNT_ERC20_SECURITY_CHECK`: ERC20 token security
 - `ACCOUNT_ERC721_SECURITY_CHECK`: NFT asset security
 - `ACCOUNT_ERC1155_SECURITY_CHECK`: Multi-token asset security

diff --git a/packages/plugin-goplus/src/lib/GoPlusManage.ts b/packages/plugin-goplus/src/lib/GoPlusManage.ts
@@ -4,7 +4,7 @@ export const GoPlusType = {
     SUITOKEN_SECURITY_CHECK: "SUITOKEN_SECURITY_CHECK",
     RUGPULL_SECURITY_CHECK: "RUGPULL_SECURITY_CHECK",
     NFT_SECURITY_CHECK: "NFT_SECURITY_CHECK",
-    ADRESS_SECURITY_CHECK: "ADRESS_SECURITY_CHECK",
+    ADDRESS_SECURITY_CHECK: "ADDRESS_SECURITY_CHECK",
     APPROVAL_SECURITY_CHECK: "APPROVAL_SECURITY_CHECK",
     ACCOUNT_ERC20_SECURITY_CHECK: "ACCOUNT_ERC20_SECURITY_CHECK",
     ACCOUNT_ERC721_SECURITY_CHECK: "ACCOUNT_ERC721_SECURITY_CHECK",

diff --git a/packages/plugin-goplus/src/services/GoplusSecurityService.ts b/packages/plugin-goplus/src/services/GoplusSecurityService.ts
@@ -58,7 +58,7 @@ export class GoplusSecurityService extends Service implements IGoplusSecuritySer
                 case GoPlusType.NFT_SECURITY_CHECK:
                     checkResult = await goPlusManage.nftSecurity(obj.network, obj.token);
                     break;
-                case GoPlusType.ADRESS_SECURITY_CHECK:
+                case GoPlusType.ADDRESS_SECURITY_CHECK:
                     checkResult = await goPlusManage.addressSecurity(obj.wallet);
                     break;
                 case GoPlusType.APPROVAL_SECURITY_CHECK:

diff --git a/packages/plugin-goplus/src/templates/index.ts b/packages/plugin-goplus/src/templates/index.ts
@@ -94,14 +94,14 @@ Available actions:
 \`\`\`
 
 
-- [ADRESS_SECURITY_CHECK]
+- [ADDRESS_SECURITY_CHECK]
     Description: Analysis of specific address security status, detecting known malicious addresses, scam addresses or high-risk addresses
     Keywords: wallet security, malicious address, scam address, blacklist
     Respond with a JSON markdown block containing only the extracted values:
 
 \`\`\`json
 {
-"type": "ADRESS_SECURITY_CHECK"
+"type": "ADDRESS_SECURITY_CHECK",
 "network": "1", //default: 1 (Ethereum:1, Optimism:10, Cronos:25, BSC:56, Gnosis:100, HECO:128, Polygon:137, Fantom:250, KCC:321, zkSync Era:324, FON:201022, Arbitrum:42161, Avalanche:43114, Linea Mainnet:59144, Tron:tron, Scroll:534352, opBNB:204, Base:8453, Solana:solana)
 "wallet": "" | null,
 }
@@ -206,4 +206,4 @@ Instructions:
 3. **Formulate a Clear Response**: Combine the action type, extracted information, and an analysis of the results. Provide a clear, concise response based on the security context. Focus on delivering the most relevant answer without unnecessary detail.
 - Only reply with your conclusion.
 - Do not discuss the safety aspects of the action; just focus on identifying and pointing out any risks.
-- Tailor your response to the user’s request, focusing on their specific query.`
+- Tailor your response to the user’s request, focusing on their specific query.`