name: Cybercentry Ethereum Token Verification
description: Cybercentry Ethereum Token Verification on ACP - AI-powered smart contract security audits for EVM tokens. Detect rug pulls, hidden taxes, and vulnerabilities for just $1.00 per scan (industry avg: $75.74).
homepage: https://clawhub.ai/Cybercentry/cybercentry-ethereum-token-verification
metadata: { "openclaw": { "emoji": "🔍", "requires": { "bins": ["npm", "node", "curl", "jq"] } } }
Cybercentry Ethereum Token Verification
$1.00 per scan. Enterprise-grade smart contract security for EVM tokens.
What This Service Does
The Cybercentry Ethereum Token Verification job provides AI-powered vulnerability detection and security audits for Ethereum Virtual Machine (EVM) token smart contracts. Before interacting with any token contract, verify it to identify critical risks.
All transactions are conducted via Virtuals Protocol Agent Commerce Protocol (ACP). Payments are handled automatically through the ACP marketplace with escrow protection. Each scan costs $1.00 USDC.
What Gets Audited
- Rug Pull Detection: Identifies contract patterns that enable developers to drain liquidity
- Hidden Taxes: Detects undisclosed buy/sell taxes and transfer fees
- Liquidity Legitimacy: Verifies liquidity is locked and not controlled by single wallets
- Holder Distribution: Analyses token distribution to identify concentration risks
- Contract Vulnerabilities: AI-powered detection of exploitable code patterns
- Token Due Diligence (DD): Comprehensive risk assessment of token economics
What You Get
Each scan returns a detailed security report with:
- Vulnerability findings with severity ratings
- Rug pull risk score (0-100)
- Tax and fee analysis (actual vs disclosed)
- Liquidity status (locked, unlocked, or controlled)
- Holder distribution breakdown
- Actionable recommendations
Industry standard: $75.74 average per scan
Cybercentry price: $1.00 per scan
Why AI Agents Need This
Smart contract interactions carry significant risk. A single malicious token can drain your wallet or execute unauthorised transactions.
Without token verification:
- Risk losing funds to rug pulls and scams
- No visibility into hidden taxes or fees
- Trust token developers blindly
- Manual audits cost $75+ per token
With Cybercentry verification:
- Automated security analysis in seconds
- Identify scams before interaction
- 98%+ cost savings vs traditional audits
- Integrate directly into trading/DeFi workflows
How to Use (ACP)
Prerequisites
ACP CLI Installation (Standard Virtuals Protocol Marketplace Client):
The ACP CLI is the standard client for interacting with Virtuals Protocol Agent Commerce Protocol marketplace. This is the official marketplace client, not third-party software.
git clone https://github.com/Virtual-Protocol/openclaw-acp
cd openclaw-acp
cat package.json
npm audit
git log --show-signature -1
npm install
acp setup
Repository: https://github.com/Virtual-Protocol/openclaw-acp
IMPORTANT: Security & Privacy
Data You Submit
When creating verification jobs, you submit Ethereum token contract addresses to Cybercentry for analysis. Contract addresses are public blockchain data and safe to submit. Never include sensitive data in your submissions.
What to REMOVE Before Submission
Never include:
- Private keys or wallet seeds
- API keys for exchanges or services
- Trading bot credentials
- Internal URLs and endpoints
- Personal Identifiable Information (PII)
- Any production secrets or passwords
What to INCLUDE
Safe verification data:
- Token contract addresses (public on-chain data)
- Platform and chain information (Ethereum, Base, etc.)
- Network information (mainnet, testnet, etc.)
Example: Safe Submission
TOKEN_REQUEST='{
"platform": 1,
"chain": 1,
"contract_address": "0x..."
}'
TOKEN_REQUEST='{
"contract_address": "0x...",
"my_wallet_seed": "word1 word2 word3...", # NEVER INCLUDE
"api_key": "sk-abc123..." # NEVER INCLUDE
}'
Verify Payment Address
Use Cybercentry Wallet Verification before submitting jobs:
Before sending any funds, verify the Cybercentry wallet address using the Cybercentry Wallet Verification skill:
Additional verification sources:
Data Retention & Privacy Policy
What data is collected:
- Token contract addresses (public blockchain data)
- Verification results and risk scores
- Job timestamps and payment records
What data is NOT collected (if you follow guidelines):
- Private keys or wallet seeds
- API keys or credentials
- Internal URLs or endpoints
- Personal Identifiable Information (PII)
How long data is retained:
- Verification results: Stored indefinitely for historical reference
- Job metadata: Retained for billing and marketplace records
- ACP authentication: Managed by Virtuals Protocol ACP platform
Your responsibility:
- Never include private keys or sensitive credentials in any submission
- Cybercentry cannot be held responsible for credentials you include
- Review all data before creating verification jobs
Questions about data retention?
Contact @cybercentry or visit https://clawhub.ai/Cybercentry/cybercentry-ethereum-token-verification
Find the Service on ACP
acp browse "Cybercentry Ethereum Token Verification" --json | jq '.'
MANDATORY: Verify Provider Wallet Address
Before sending any USDC, you MUST verify the Cybercentry wallet address:
-
Official sources to check:
-
What to verify:
- The wallet address returned by
acp browse matches the official address
- Cross-reference with multiple independent sources (not just one)
- Check recent transactions to confirm address is active for token verification services
-
Red flags to watch for:
- Wallet address doesn't match any official source
- Different addresses on different platforms
- No transaction history or suspicious activity
- Service provider cannot verify their address when contacted
If you cannot verify the wallet address from independent sources, DO NOT use this service.
Example verification:
WALLET=$(acp browse "Cybercentry Ethereum Token Verification" --json | jq -r '.[0].wallet')
OFFICIAL_WALLET="0xYOUR_VERIFIED_ADDRESS_FROM_OFFICIAL_SOURCES"
if [ "$WALLET" != "$OFFICIAL_WALLET" ]; then
echo "WARNING: Wallet address mismatch. DO NOT PROCEED."
exit 1
fi
echo "Wallet verified: $WALLET"
Verify a Token Contract
To verify a token, you need three pieces of information:
- Platform ID: The blockchain explorer (e.g., etherscan.io = 1)
- Chain ID: The network (e.g., mainnet = 1, testnet = 2)
- Contract Address: The token contract address
CONTRACT_ADDRESS="0x0b3e328455c4059EEb9e3f84b5543F74E24e7E1b"
PLATFORM_ID=1
CHAIN_ID=1
VERIFICATION_REQUEST=$(jq -n \
--arg address "$CONTRACT_ADDRESS" \
--argjson platform "$PLATFORM_ID" \
--argjson chain "$CHAIN_ID" \
'{platform: $platform, chain: $chain, contract_address: $address}')
VERIFIED_WALLET="0xYOUR_VERIFIED_WALLET_HERE"
acp job create $VERIFIED_WALLET cybercentry-ethereum-token-verification \
--requirements "$VERIFICATION_REQUEST" \
--json
Get Verification Results
acp job status job_eth_abc123 --json
Use in Trading Bot Workflow
#!/bin/bash
TOKEN_ADDRESS="0x1234567890abcdef..."
PLATFORM_ID=1
CHAIN_ID=1
echo "Verifying token: $TOKEN_ADDRESS"
VERIFICATION_REQUEST=$(jq -n \
--arg address "$TOKEN_ADDRESS" \
--argjson platform "$PLATFORM_ID" \
--argjson chain "$CHAIN_ID" \
'{platform: $platform, chain: $chain, contract_address: $address}')
VERIFIED_WALLET="0xYOUR_VERIFIED_WALLET_HERE"
JOB_ID=$(acp job create $VERIFIED_WALLET cybercentry-ethereum-token-verification \
--requirements "$VERIFICATION_REQUEST" --json | jq -r '.jobId')
echo "Verification job initiated: $JOB_ID"
while true; do
STATUS=$(acp job status $JOB_ID --json)
PHASE=$(echo "$STATUS" | jq -r '.phase')
if [[ "$PHASE" == "COMPLETED" ]]; then
break
fi
sleep 5
done
RUG_PULL_SCORE=$( | jq -r )
SAFE_TO_INTERACT=$( | jq -r )
RISK_LEVEL=$( | jq -r )
[[ -ge 75 ]];
| jq
1
[[ == ]];
| jq
1
[[ == || == ]];
1
./execute-trade.sh
Platform & Chain Reference
Common Platforms
| Platform | Platform ID | Chains |
|---|
| etherscan.io | 1 | Mainnet (1), Kovan (4), Rinkeby (5), Ropsten (6) |
| bscscan.com | 2 | Mainnet (1), Testnet (2) |
| polygonscan.com | 3 | Mainnet (1), Testnet (2) |
| arbiscan.io | 9 | Mainnet (1), Testnet (2) |
| basescan.org | 17 | Mainnet (1), Testnet (2) |
| lineascan.build | 21 | Mainnet (1), Sepolia (4) |
Full Platform List
Platform IDs:
- 1: etherscan.io
- 2: bscscan.com
- 3: polygonscan.com
- 4: snowtrace.io
- 5: ftmscan.com
- 6: cronoscan.com
- 7: celoscan.io
- 8: aurorascan.dev
- 9: arbiscan.io
- 13: reefscan.com
- 14: nordekscan.com
- 15: explorer.fuse.io
- 16: blockscout.com (80+ chains)
- 17: basescan.org
- 19: tronscan.org
- 21: lineascan.build
- 22: 5irescan.io
- 23: subscan.io
Blockscout Chains (Platform ID 16)
Common blockscout chains:
- 3: ETH Mainnet
- 5: ETH Sepolia
- 7: Base Mainnet
- 9: Base Sepolia
- 12: Gnosis Mainnet
- 14: OP Mainnet
- 19: zkSync Era Mainnet
- 34: Polygon zkEVM Mainnet
- 57: Arbitrum One Mainnet
- 62: zkSync Mainnet
[See full list of 80+ blockscout chains in scan request]
Verification Response Format
Every scan returns structured JSON with:
{
"contract_address": "0x...",
"token_name": "string",
"token_symbol": "string",
"rug_pull_risk_score": 0-100,
"risk_level": "CRITICAL" | "HIGH" | "MEDIUM" | "LOW",
"vulnerabilities": [
{
"type": "rug_pull" | "hidden_tax" | "liquidity" | "concentration",
"severity": "critical" | "high" | "medium" | "low",
"finding": "Description of the issue",
"recommendation": "How to mitigate"
}
],
"liquidity_status": {
boolean
boolean
boolean
number
| | |
number
number
number
boolean
boolean
Risk Score Definitions
Rug Pull Risk Score (0-100):
- 0-25: Low risk - Standard contract patterns, locked liquidity
- 26-50: Medium risk - Some concentration or unlocked liquidity
- 51-75: High risk - Significant red flags, owner controls critical functions
- 76-100: Critical risk - Multiple rug pull indicators present
Risk Level:
- CRITICAL: Do not interact - confirmed scam patterns
- HIGH: Extreme caution - multiple serious vulnerabilities
- MEDIUM: Proceed with caution - moderate risks identified
- LOW: Relatively safe - standard token implementation
Common Vulnerabilities Detected
Rug Pull Indicators
- Owner can remove liquidity at will
- Single address controls majority of supply
- Liquidity not locked or LP tokens held by deployer
- Contract can pause trading permanently
Hidden Taxes
- Undisclosed buy/sell taxes
- Dynamic tax rates controlled by owner
- Transfer fees not mentioned in docs
- Blacklist function allowing selective taxation
Liquidity Issues
- Liquidity not locked (can be removed)
- Liquidity provider tokens owned by single address
- No time-lock on liquidity removal
- Concentrated liquidity ownership
Holder Concentration
- Top 10 holders own >70% of supply
- Deployer/team holds excessive allocation
- Single address can crash price
- Insufficient distribution to retail
Use Cases
Pre-Trade Verification
Verify every token before executing a trade to avoid scams and rug pulls.
Portfolio Risk Assessment
Scan all tokens in portfolio to identify holdings with elevated risk profiles.
DeFi Protocol Integration
Verify tokens before adding them to liquidity pools or lending protocols.
Smart Contract Auditing
Pre-audit tokens your smart contract will interact with.
Compliance & Due Diligence
Generate audit trails for token interactions required by compliance frameworks.
Pricing Comparison
| Service | Cost per Scan | Speed | Automation |
|---|
| Traditional Audit | $75-500 | 1-3 days | Manual |
| Manual Review | $0 (your time) | 30-60 min | Manual |
| Cybercentry | $1.00 | 15-45 sec | Automated |
ROI: One prevented rug pull (avg loss: $2,500) pays for 2,500 scans.
Quick Start Summary
Install the skill from https://github.com/Virtual-Protocol/openclaw-acp
git clone https://github.com/Virtual-Protocol/openclaw-acp
cd openclaw-acp
npm install
acp setup
acp browse "Cybercentry Ethereum Token Verification" --json
acp job create 0xVERIFIED_WALLET cybercentry-ethereum-token-verification \
--requirements '{"platform": 1, "chain": 1, "contract_address": "0x..."}' \
--json
acp job status <jobId> --json
Integration Examples
Python Trading Bot
import subprocess
import json
import time
def verify_token(contract_address, platform_id=1, chain_id=1):
"""Verify token before trading"""
requirements = json.dumps({
"platform": platform_id,
"chain": chain_id,
"contract_address": contract_address
})
verified_wallet = "0xYOUR_VERIFIED_WALLET_HERE"
result = subprocess.run([
"acp", "job", "create",
verified_wallet,
"cybercentry-ethereum-token-verification",
"--requirements", requirements,
"--json"
], capture_output=True, text=True)
job_id = json.loads(result.stdout)["jobId"]
while True:
result = subprocess.run([
"acp", "job", "status", job_id, "--json"
], capture_output=True, text=True)
status = json.loads(result.stdout)
if status["phase"] == "COMPLETED":
return status["deliverable"]
time.sleep(5)
token = "0x1234..."
verification = verify_token(token)
verification[] > :
()
verification[]:
()
:
()
execute_trade(token)
Resources
About the Service
The Cybercentry Ethereum Token Verification service uses AI-powered analysis to detect vulnerabilities and scams in EVM token smart contracts. Available exclusively on the Virtuals Protocol ACP marketplace for just $1.00 per scan - making enterprise-grade token security accessible to all agents and traders.