2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill solana- _meta.json269 B
- SKILL.md3.4 KB
Overview
This skill helps you construct, inspect, and troubleshoot Solana transactions, token accounts, priority fees, and program interactions. It explains rent-exemption, ATA handling, fee mechanics, transaction lifecycle, common error messages, and recommended RPC usage. Use it to avoid common pitfalls and to optimize success during network congestion.
How this skill works
The skill inspects account rent status, detects missing Associated Token Accounts (ATAs), calculates base and priority fees, and suggests compute unit adjustments for heavy programs. It analyzes transaction preflight results and common RPC errors, then provides actionable fixes like recreating ATAs, adding priority fees, or refreshing blockhashes. It also points to appropriate RPC providers and explorer tools for deeper debugging.
When to use it
- Creating or sending SPL tokens to a wallet that may lack an ATA
- Building complex program transactions that need higher compute limits or priority fees
- Recovering from common errors like 'Account not found' or 'Blockhash not found'
- Optimizing transactions during congested periods (NFT drops, DEX activity)
- Closing unused token accounts to recover rent
Best practices
- Ensure new accounts are funded to the rent-exempt minimum before sending SOL or creating token accounts
- Always create or verify the recipient's ATA before attempting an SPL token transfer
- Use preflight simulation to catch contract errors; only disable skipPreflight when you understand the risk
- Add a priority fee (SetComputeUnitPrice) when congestion is likely; monitor getRecentPrioritizationFees
- Use paid RPC providers for production to avoid strict public rate limits and dropped requests
Example use cases
- Preparing a minting transaction for an NFT drop: add compute unit price and increase compute limit to avoid drops
- Troubleshooting a failed token transfer: detect missing ATA and create it, then retry the transfer
- Recovering funds: identify and close unused token accounts to reclaim rent deposits
- Fixing expired transactions: refresh blockhash, re-sign, and re-submit when you see 'Blockhash not found'
FAQ
New addresses require a rent-exempt balance. If the amount sent doesn’t cover the minimum or an ATA is missing, the transfer will fail.
What’s the difference between dropped and failed transactions?
Dropped means the transaction never made it into a block and expired (blockhash too old). Failed means it was included but the program reverted.
How do I improve success during congestion?
Set a priority fee via SetComputeUnitPrice, monitor getRecentPrioritizationFees, and consider paid RPCs to reduce rate-limit drops.