dune-sim-onchain-analytics
Dune Sim and Dune Analytics — on-chain analytics skill
This skill is the primary home for Dune-powered workflows in blockint: how to think, what to call when, and how to ship analytics that combine realtime Sim data with historical SQL where appropriate. It is not a thin link list—use it to structure tasks; open docs.sim.dune.com/llms.txt and openapi.json for exact parameters and auth as you implement.
Educational and integration guidance—users remain responsible for API keys, billing, and Terms.
Mental model: two engines
| Engine | Best for | Typical outputs |
|---|---|---|
| Dune Sim | Live wallet and token state—balances, activity feeds, transactions, NFT collectibles, DeFi positions, stablecoin views, webhook subscriptions | Apps, agents, alerts, “what does this address hold / do now” |
| Dune Analytics API | Historical exploration—SQL over Dune’s curated blockchain tables | Research, cohorts, backtests, dashboards backed by queries |
Rule of thumb: Need streaming or low-latency address/token views across many EVM chains or SVM (Solana / Eclipse, etc.) → start with Sim and chain-specific docs under chains/. Need long-horizon or custom aggregations across Dune SQL models → Analytics API and query execution docs.
When to use which surface (decision flow)
- Single address or small set — balances, recent activity, NFTs, token metadata → Sim EVM or SVM endpoints (see overviews below).
- Ongoing monitoring — balance or activity changes for a watchlist → Subscriptions / webhooks (create, update addresses, lifecycle per docs).
More from agentic-reserve/blockint-skills
evm-solidity-defi-triage-agent
Guides EVM Solidity DeFi triage from public verified source or bytecode—access control, proxies, oracle usage, reentrancy and CEI patterns, DEX/router integrations, and common vulnerability classes. Use when the user asks for Ethereum or L2 smart contract security review, Solidity audit triage, OpenZeppelin proxy risks, or EVM-specific DeFi patterns—not for live exploits or private keys.
10crypto-market-structures
Summarizes descriptive concepts for max pain options theory, covered-call style crypto ETFs, crypto arbitrage families and risks, and bull/bear flag chart patterns—always as non-prescriptive education. Use when the user asks about max pain, premium income ETFs, arbitrage, funding rates, flash loans, or bull/bear flags in crypto trading context.
10honeypot-detection-techniques
Educational techniques to assess honeypot-style token risk from verified source, bytecode clues, and observational on-chain history—EVM ERC-20 patterns (transfer gates, fees, blacklists), Solana SPL and Token-2022 hooks, and safe validation paths. Use when the user asks how to detect honeypots, sell-restricted tokens, scam token mechanics, or static review checklists—not for deploying scams, stealing funds, or advising high-risk mainnet test trades on unknown contracts.
10katana-web-crawling
Guides use of ProjectDiscovery Katana for web crawling and spidering in security testing and recon workflows. Covers installation, standard vs headless mode, scope and rate limits, JSONL output, and piping from httpx or URL lists. Use when the user mentions Katana, projectdiscovery/katana, web crawling, spidering, endpoint discovery, attack surface mapping, or chaining crawlers in automation pipelines.
10solana-defi-vulnerability-analyst-agent
Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state—Anchor/native programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad/bonding-curve issues, or evidence-backed severity findings without exploits or private keys.
10crypto-investigation-compliance
Maps high-level crypto crime categories, safe and ethical OSINT plus on-chain investigation workflow, and victim reporting posture. Use when the user asks about scam types, pig butchering, rug pulls, tracing stolen funds ethically, compliance-adjacent investigation, or how to document cases for authorities.
10