Skip to content

Latest commit

 

History

History
77 lines (56 loc) · 2.11 KB

File metadata and controls

77 lines (56 loc) · 2.11 KB
name description
wallet-alpha-scanner
Analyze crypto wallet addresses for risk signals and alpha opportunities. Use when user asks to scan/analyze a wallet, check if a wallet is safe, identify airdrop farmers, find alpha signals, or assess wallet risk exposure. Supports EVM addresses (0x...) and Solana addresses.

Wallet Alpha & Risk Scanner

Provide quick risk + alpha analysis of crypto wallets. Not forensic audits — fast heuristic signals.

Analysis Framework

1. Wallet Profile

  • Age: When first transaction occurred
  • Activity: Transaction frequency (dormant / casual / active / hyperactive)
  • Chains: Which networks the wallet uses
  • Type: Likely degen, farmer, whale, or normie

2. Alpha Signals (bullish indicators)

  • Early minter on successful projects
  • Interaction with protocols before they trend
  • Cross-chain activity (bridge usage)
  • Consistent NFT minting patterns
  • Following known alpha wallets

3. Risk Signals (red flags)

  • Approvals to unverified contracts
  • Interaction with flagged/scam tokens
  • Drainer contract exposure
  • Dust attack tokens in wallet
  • High-frequency small transfers (wash trading pattern)

Data Sources

Use on-chain explorers and APIs:

  • EVM: Etherscan, Polygonscan, Basescan, DeBank, Arkham
  • Solana: Solscan, Solana.fm
  • Cross-chain: DeBank portfolio view

When browser access available, fetch recent transactions and token holdings.

Output Format

## Wallet: [address_short]

**Profile**: [type] | [age] | [activity_level]
**Chains**: [list]

### Alpha Signals
- [signal 1]
- [signal 2]

### Risk Signals
- [signal 1]
- [signal 2]

**Summary**: [1-2 sentence assessment]

⚠️ *Heuristic analysis only. DYOR before trusting any wallet.*

Keep it:

  • Bullet-based
  • Non-technical friendly
  • Actionable

Rules

  • Never say a wallet is "safe" — say "no major red flags detected"
  • Never give financial advice
  • Present findings as signals, not conclusions
  • Encourage user to verify independently
  • If data is limited, say so

Methodology

See references/methodology.md for detailed signal definitions.