Wallet Tracker

Multi-chain wallet asset tracker — monitor EVM and Solana wallets, aggregate portfolio, and detect holding changes. Use when you need wallet tracker capabili...

Security Scan

The skill appears to implement a multi-chain wallet tracker, but the README (SKILL.md) and the shipped scripts are inconsistent about filenames, environment variables, and configuration — these mismatches make the package suspicious and warrant caution before use.

Purpose & Capability

The code (scripts/wallet.sh) implements EVM and Solana balance checks using public block explorer APIs, which aligns with the stated purpose. However, SKILL.md references a different script name (scripts/wallet-tracker.sh) and advertises env var behavior (WALLET_TRACKER_RPC_<CHAIN>) that the included wallet.sh does not implement. An extra script (scripts/script.sh) appears unrelated to the advertised functionality.

Instruction Scope

SKILL.md instructs running a script name (scripts/wallet-tracker.sh) that is not present; the real script is scripts/wallet.sh. SKILL.md claims support for custom RPC env vars (WALLET_TRACKER_RPC_<CHAIN>), but wallet.sh does not use those variables. The code reads ETHERSCAN_API_KEY (and may use WALLET_TRACKER_DIR in the other script) even though SKILL.md does not document ETHERSCAN_API_KEY as required. The scripts make outbound requests to public block-explorer and RPC endpoints (expected), and write snapshots/wallets to the user's home directory (~/.wallet-tracker).

Install Mechanism

No install spec; this is an instruction-only skill with bundled scripts. That is low installation risk — nothing is downloaded at runtime by the skill itself. The scripts will create files under the user's home directory when run.

Credentials

The skill package does not declare required env vars, yet the code optionally reads ETHERSCAN_API_KEY and script.sh references WALLET_TRACKER_DIR; SKILL.md suggests WALLET_TRACKER_RPC_<CHAIN> despite no implementation. The env vars the code uses are plausible for the purpose (API keys, RPC overrides), but the mismatches between documentation and code are concerning and could confuse users into setting unrelated credentials.

Persistence & Privilege

The skill does not request elevated or persistent platform privileges (always:false). It writes configuration and snapshot files into the user's home directory (~/.wallet-tracker or under XDG_DATA_HOME), which is normal for a CLI tool but should be expected by the user.

What to consider before installing

This package mostly does what it claims (queries public blockchain APIs and stores snapshots locally), but there are several inconsistencies you should resolve before trusting it: 1) SKILL.md calls a script that doesn't exist (scripts/wallet-tracker.sh) while the real script is scripts/wallet.sh — run the real script only after inspection. 2) The documentation mentions WALLET_TRACKER_RPC_<CHAIN> support, but wallet.sh doesn't use it; conversely the code reads ETHERSCAN_API_KEY even though that isn't documented. 3) An extra script (scripts/script.sh) appears unrelated; review it and decide whether you need it. Recommended steps: inspect the scripts locally (they're plain text), run them in an isolated environment or container, avoid supplying any private keys or unrelated credentials, and only set ETHERSCAN_API_KEY if you understand and trust the tool. If you plan to use custom RPC endpoints, verify the script actually uses them or modify the code to respect your RPC env vars. If possible, ask the publisher for an updated SKILL.md that matches the shipped files.

Track multiple wallets across EVM chains and Solana. Aggregate your portfolio, monitor holding changes, and get alerts when significant movements happen.

Scenarios & Use Cases

Scenario 1: Personal Portfolio Overview

You hold assets across 5 wallets on Ethereum, Polygon, and Solana. You want a single dashboard.

bash scripts/wallet-tracker.sh portfolio \
  --wallets "0xABC123...,0xDEF456...,5KtPn1..." \
  --chains "ethereum,polygon,solana"

Output: An HTML report showing total value, per-chain breakdown, and per-wallet holdings.

---

Scenario 2: Whale Watching

Track a known whale wallet for large movements:

bash scripts/wallet-tracker.sh watch \
  --wallet "0xWhale..." \
  --chain ethereum \
  --threshold 100000 \
  --interval 300

Output: Console alerts when transfers exceed $100K threshold.

---

Scenario 3: Airdrop Farming Tracker

You're farming airdrops across multiple wallets. Track activity and eligibility:

bash scripts/wallet-tracker.sh activity \
  --wallets-file my-wallets.txt \
  --chain ethereum \
  --since 2024-01-01

Output: Transaction count, unique contracts interacted, active days, and volume per wallet.

---

Scenario 4: Team Treasury Monitoring

Monitor a DAO treasury wallet for unauthorized withdrawals:

bash scripts/wallet-tracker.sh monitor \
  --wallet "0xTreasury..." \
  --chain ethereum \
  --alert-on decrease \
  --output treasury-report.html

---

Scenario 5: Cross-Chain Balance Snapshot

Take a point-in-time snapshot across all chains for accounting:

bash scripts/wallet-tracker.sh snapshot \
  --wallets-file all-wallets.txt \
  --output snapshot-2024-Q1.json

Supported Chains

Chain	Type	Native Token	RPC Default
Ethereum	EVM	ETH	Public RPC
Polygon	EVM	MATIC	Public RPC
Arbitrum	EVM	ETH	Public RPC
Optimism	EVM	ETH	Public RPC
BSC	EVM	BNB	Public RPC
Avalanche	EVM	AVAX	Public RPC
Solana	SVM	SOL	Public RPC

💡 Tip: Set custom RPCs via environment variable WALLET_TRACKER_RPC_<CHAIN>=https://... for better rate limits.

Configuration File

Create ~/.wallet-tracker.json for persistent config:

{
  "wallets": [
    {"address": "0xABC...", "label": "Main ETH", "chains": ["ethereum", "polygon"]},
    {"address": "5KtPn...", "label": "Solana Hot", "chains": ["solana"]}
  ],
  "refresh_interval": 600,
  "alert_threshold_usd": 1000,
  "output_dir": "./wallet-reports"
}

Commands

Command	Description
add	Add
list	List
check	Check
remove	Remove
history	History
export	Export

Privacy Note

This tool queries public blockchain data only. No private keys are ever required or requested. All data is processed locally.

💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com