solana-rpc
Skill2 starsChanged 3 months agoMITView on GitHub
Expert assistant for Solana JSON-RPC — works with any provider: QuickNode, Helius, Triton, Ankr, Chainstack, or public endpoints. Standard JSON-RPC methods are identical across providers; only the URL differs.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- Serennity007/claude-trading-skills-67their own version, first seen Aug 25, 2026
- agiprolabs/claude-trading-skillstheir own version, first seen Mar 11, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- agiprolabs/claude-trading-skills★ 366same name
- IngAs8/ClaudeSkill★ 0same name
- Serennity007/claude-trading-skills-67★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- coinmarketcapSkill
- dexscreenerSkill
- duneSkill
- mev-bundlesSkill
- nansenSkill
- pumpfunSkill
- solscanSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 3 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 49
When in doubt: check references/helius-extensions.md first — if Helius has a purpose-built endpoint, use it.
- Very specific: line 75
If you're querying NFTs or tokens by collection/owner: use DAS instead (getAssetsByGroup, getAssetsByOwner).
- Distinctive: line 81
All Solana RPC calls need a URL.
- Distinctive: line 101
If user has both Helius and QuickNode, you can configure fallback:
- Very specific: line 110
Read account data → getAccountInfo, getMultipleAccounts
- Very specific: line 111
Read tx → getTransaction (raw) or Helius Enhanced (parsed)
- Very specific: line 112
Read history → getSignaturesForAddress + batch getTransaction, OR Helius getTransactionsForAddress
- Very specific: line 113
Read token balances/NFTs → DAS getAssetsByOwner (preferred) or getTokenAccountsByOwner
- Distinctive: line 119
If > 3 items of same method → batch them in one HTTP request.
- Very specific: line 122
Default confirmed for reads
- Very specific: line 124
Never processed for production (may revert)
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Solana RPC Skill
Reference files:
references/core-methods.md— standard Solana JSON-RPC methods, parameters, response shapesreferences/helius-extensions.md— DAS API, Enhanced Transactions, Priority Fee, Sender, LaserStreamreferences/quicknode-extensions.md—qn_estimatePriorityFees, Metaplex DAS addon, Jitoreferences/patterns.md— batching, rate limits, resume, cost optimizationreferences/examples/— working Python scripts
🚨 Rule #1: use the provider's parsed/enhanced APIs when available
The biggest credit waste on Solana RPC is fetching raw data and parsing it yourself when the provider offers a parsed endpoint. Matrix:
| Task | Cheap option | Expensive / broken option |
| Wallet NFTs + tokens | Helius DAS getAssetsByOwner | getTokenAccountsByOwner + metadata lookups |
| Complete tx history | Helius getTransactionsForAddress | getSignaturesForAddress + N × getTransaction |
| Parsed DEX swap details | Helius Enhanced Tx or Solscan | getTransaction + manual program parsing |
| NFTs by collection | DAS getAssetsByGroup / searchAssets | getProgramAccounts (expensive + slow) |
| Priority fee estimate | getPriorityFeeEstimate (Helius) or qn_estimatePriorityFees (QuickNode) | getRecentPrioritizationFees (raw, needs math) |
| Compressed NFT history | DAS getSignaturesForAsset | getSignaturesForAddress (doesn't work for cNFTs) |
When in doubt: check references/helius-extensions.md first — if Helius has a purpose-built endpoint, use it.
🚨 Rule #2: batch JSON-RPC requests
Single HTTP request can carry an array of JSON-RPC calls:
[
{"jsonrpc":"2.0","id":1,"method":"getTransaction","params":["sig1",{"encoding":"jsonParsed","maxSupportedTransactionVersion":0}]},
{"jsonrpc":"2.0","id":2,"method":"getTransaction","params":["sig2",{"encoding":"jsonParsed","maxSupportedTransactionVersion":0}]},
...up to ~100 items
]Response is an array. Most providers count each call individually but save massive HTTP overhead. Always batch when fetching N items of same shape.
See references/patterns.md for semaphore tuning and provider-specific batch limits.
🚨 Rule #3: never getProgramAccounts without tight filters
getProgramAccounts scans ALL accounts under a program. On popular programs (SPL Token, Token 2022, NFT programs) it's catastrophically slow and expensive, often times out.
Always apply:
dataSizefilter (exact byte length)memcmpfilter (matches at specific offset) — typically for mint address, owner, or discriminator
If you're querying NFTs or tokens by collection/owner: use DAS instead (getAssetsByGroup, getAssetsByOwner).
Setup: provider URL
All Solana RPC calls need a URL. Configure via env var:
# Helius
export SOLANA_RPC_URL="https://mainnet.helius-rpc.com/?api-key=YOUR_KEY"
# QuickNode
export SOLANA_RPC_URL="https://YOUR-ENDPOINT.solana-mainnet.quiknode.pro/YOUR-TOKEN/"
# Ankr
export SOLANA_RPC_URL="https://rpc.ankr.com/solana/YOUR_KEY"
# Public (DON'T use for production)
export SOLANA_RPC_URL="https://api.mainnet-beta.solana.com"Scripts read from SOLANA_RPC_URL. Never hardcode. If user has separate endpoints for archive vs. frontend (common on QuickNode), support SOLANA_RPC_URL_ARCHIVE additionally.
Multi-provider fallback (optional)
If user has both Helius and QuickNode, you can configure fallback:
SOLANA_RPC_URL_PRIMARY— first choiceSOLANA_RPC_URL_FALLBACK— used when PRIMARY hits 429 or errors 5×× persistently
Script pattern in references/examples/.
Step-by-step workflow
1. Classify the task
- Read account data →
getAccountInfo,getMultipleAccounts - Read tx →
getTransaction(raw) or Helius Enhanced (parsed) - Read history →
getSignaturesForAddress+ batchgetTransaction, OR HeliusgetTransactionsForAddress - Read token balances/NFTs → DAS
getAssetsByOwner(preferred) orgetTokenAccountsByOwner - Submit tx →
sendTransactionor Helius Sender (better landing rate) - Estimate fee →
getPriorityFeeEstimate(Helius) orqn_estimatePriorityFees(QuickNode) - Stream real-time → WebSocket / LaserStream (not polling)
2. Check for batch opportunities If > 3 items of same method → batch them in one HTTP request. Don't loop.
3. Pick commitment level
- Default
confirmedfor reads finalizedfor financial audit / history- Never
processedfor production (may revert)
4. Execute (MCP or script)
- Single call: curl or httpx inline
- Batch: Python script with aiohttp + JSON-RPC array, output JSONL
5. Present results
- Lamports → divide by 1e9 for SOL
- Token amounts → divide by 10^decimals
- Timestamps:
block_timeis unix seconds (no sub-second precision ongetBlockTime)
Common mistakes & error codes
| Error | Cause | Fix |
-32009 "Slot ... skipped" | Asked for a slot that wasn't produced | Use getBlock with commitment: "confirmed" and skip error silently |
-32602 Invalid params | Wrong encoding / missing maxSupportedTransactionVersion: 0 | Add "maxSupportedTransactionVersion": 0 to all tx reads |
| 429 Too Many Requests | Rate limit | Respect provider's Retry-After, lower semaphore |
Response timeout on getBlock | Large response (~MBs) | Set HTTP timeout ≥ 30s; consider transactionDetails: "signatures" or accounts if full tx not needed |
Empty result on getSignaturesForAddress | No sigs in the range OR wrong before/until cursors | Verify cursor with getSignatureStatuses |
| DAS methods missing | Not Helius/QuickNode with DAS addon | Fall back to raw RPC or enable addon |
Memory updates
Old memory says:
- "QuickNode
getTransaction: ~10k/min, ~15KB response, 3x faster than Solscan for single-tx" — ✅ still valid - "
getBlock: ~30s timeout needed, large response" — ✅ still valid - "
getBlockTime: seconds precision only" — ✅ still valid
Add:
maxSupportedTransactionVersion: 0is required for modern tx reads — otherwise you get "Transaction version (0) is not supported" errors on v0 tx- Helius DAS now supports fungible tokens too (
showFungible: trueongetAssetsByOwner) - Priority fee: prefer
getPriorityFeeEstimate(Helius) over rawgetRecentPrioritizationFees
Reference files
references/core-methods.md— standard Solana JSON-RPC: accounts, blocks, transactions, feesreferences/helius-extensions.md— DAS, Enhanced Tx, Priority Fee, Sender, Webhooks, LaserStreamreferences/quicknode-extensions.md— qn_estimatePriorityFees, DAS addon, Jitoreferences/patterns.md— batching details, rate limits, fallback, costreferences/examples/fetch_tx_batch.py— batchedgetTransactionfor N signaturesreferences/examples/wallet_full_history.py— HeliusgetTransactionsForAddresswith paginationreferences/examples/wallet_holdings_das.py— DASgetAssetsByOwnerwith full token metadata
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

