solana-data
/solana-data
Grok The Block (understand what actually happened on-chain, in plain English). Shared read-only Solana data layer for every Grok The Block skill: public Solana RPC with failover, DexScreener, RugCheck, an optional HELIUS_API_KEY, and a local JSON cache. Use it when another CryptOSINT skill needs setup or when Solana RPC calls fail.
- Author
- outerheaven199X ↗
- Repository
- groktheblock ↗
- Licence
- MIT
- Last repository change
- 01.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Grok The Block (understand what actually happened on-chain, in plain English). Shared read-only Solana data layer for every Grok The Block skill: public Solana RPC with failover, DexScreener, RugCheck, an optional HELIUS_API_KEY, and a local JSON cache. Use it when another CryptOSINT skill needs setup or when Solana RPC calls fail.
Original author description
Grok The Block (understand what actually happened on-chain, in plain English). Shared read-only Solana data layer for every Grok The Block skill: public Solana RPC with failover, DexScreener, RugCheck, an optional HELIUS_API_KEY, and a local JSON cache. Use it when another CryptOSINT skill needs setup or when Solana RPC calls fail.
How it works
- Setup (once per machine)
- Data source order
- How it works
- Troubleshooting
- Rules
SKILL.md preview
---
name: solana-data
description: Grok The Block (understand what actually happened on-chain, in plain English). Shared read-only Solana data layer for every Grok The Block skill: public Solana RPC with failover, DexScreener, RugCheck, an optional HELIUS_API_KEY, and a local JSON cache. Use it when another CryptOSINT skill needs setup or when Solana RPC calls fail.
---
# Solana data layer
Every CryptOSINT script imports the shared library at `lib/cryptosint/` (repo root; `data.py` is the data layer). You do not call it directly. This skill covers setup and troubleshooting.
## Setup (once per machine)
1. `cd` to the repo root and run `python3 -m venv .venv && .venv/bin/pip install -r requirements.txt`.
2. Optional: `export HELIUS_API_KEY=...` for higher rate limits. Never ask the user to paste a key into chat. If they want one, have them set it in their own environment.
3. Optional: `export SOLANA_RPC_URL=https://a,https://b` to use your own RPC list.
## Data source order
1. With `HELIUS_API_KEY` set: Helius `getTransactionsForAddress` with `sortOrder: asc`. This jumps straight to the launch of any coin, 100 full transactions per call (tested: Fartcoin launch, 740 days back, in one call). If the key's plan doesn't allow that method, it falls back automatically.
2. A signature walk on Helius RPC, 10 times deeper than on public RPC.
3. A signature walk on public RPC.
Each scan's JSON records which one it used in `scanWindow.dataSource`. Never print or log the key. Errors never include the RPC URL.
## How it works
- RPC calls go to `api.mainnet-beta.solana.com` first and fail over to `solana-rpc.publicnode.com` on 403, 413 ("data allowance"), 429, or 5xx errors.
- Finalized transactions are cached forever under `cache/tx/`. Signature lists are cached for 2 minutes, and DexScreener and RugCheck responses for 5 to 10 minutes.
- `get_token_transactions(mint)` walks signatures back from newest to find the launch window. Public RPC only pages backwards, so for tokens with more than about `sig-pages × 1000` transactions it cannot reach the launch, and it reports `reachedLaunch: false`.
- `cache/wallet_history.jsonl` replaces the original Cloudflare KV. Token and wallet scans write to it, and the leaderboard and reputation read from it.
## Troubleshooting
- Repeated "data allowance" or 429 errors: wait a minute, lower `--max-tx`, or set `HELIUS_API_KEY`.
- To clear stale market data, delete `cache/dexscreener` and `cache/rugcheck`.
## Rules
- Read-only. Never sign transactions, connect wallets, trade, or ask for a seed phrase or private key.
- Say "coordinated pattern", "flagged wallet", or "signal". Do not say "bot", "scammer", or "fraud" about a named account or wallet.
- The tool never whitelists or skips any coin, including any coin tied to the author.
Versions
The database has no other skills named solana-data.
Database snapshot: 13.11.2026 · package version 1334c44fa320 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100threat-feed
Grok The Block (understand what actually happened on-chain, in plain English). Build a threat digest across recently scanned and watched Solana tokens: LP pulls, coordinated insider dumps, RugCheck 'rugged' flags, and enabled mint or freeze authority. Routine-ready, and silent… - 100wallet-reputation
Grok The Block (understand what actually happened on-chain, in plain English). Score one or more Solana wallets 0-100 for suspicion from their scan history, using the original CryptOSINT weights (INSIDER 25, AGENT 10, SNIPER 8, COPY 3, with multipliers for early entry, young… - 87goldrush-json-rpc
GoldRush JSON-RPC: multi-chain EVM and Solana JSON-RPC endpoints. An analytics-driven router scores every (provider, chain, endpoint) triple by success rate, latency, error class, and cost, and dispatches each call to whichever upstream is currently winning that route. Use this… - 100goldrush-solana
GoldRush API for Solana. Use this skill whenever the user wants SPL token balances for a Solana wallet (REST). REST is at `https://api.covalenthq.com/v1/solana-mainnet/...` (kebab-case chain name). SPL transfer history, Solana transactions, NFTs (Metaplex + Bubblegum cNFTs), and…