crypto-market-structures
Crypto market structures (educational)
Not investment, tax, or legal advice. Verify products in prospectuses and local rules.
Max pain (options, descriptive)
Max pain (retail framing): spot level where open-interest weighting maximizes option holders’ collective losses (many contracts OTM). Computed from OI by strike for an expiry.
Interpretation: structural description, not a price oracle. Competes with macro, liquidations, news. Use with IV, skew, funding.
Covered-call / “premium income” ETFs (conceptual)
Some funds hold spot crypto exposure via ETPs and write calls for premium:
- Income mainly from options premium
- Often caps upside in strong rallies
- Not the same as spot-only exposure—read prospectus
Crypto arbitrage (concepts + risks)
Profit from temporary price gaps across venues/instruments, net of fees.
| Type | Idea |
|---|---|
| Cross-venue | Speed, liquidity, withdrawal rails matter |
| Funding / basis | Spot vs perp; liquidation complexity |
| Flash loans | Atomic borrow/repay; smart-contract skill; also used in exploits |
| P2P / geographic | Local premia; counterparty and legal risk |
Risks: fees, gas, slippage, latency, ToS, bots, custody, contract bugs. Compliance varies by jurisdiction.
Bull / bear flags (TA primer)
Continuation narrative: impulse (pole) → consolidation (flag) → breakout in trend direction if it completes; failure = break the wrong way.
Pennant: converging lines vs parallel flag lines.
Subjective; combine with volume, levels, macro, on-chain—outcomes not guaranteed.
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.
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.
10solana-tracing-specialist
Guides Solana-specific on-chain forensics—ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX/Jito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.
10risk-exposure-screening-concepts
Educational map of risk exposure screening—typical risk indicator taxonomies, exposure value and percentage, address-level vs transaction-level engines, and common template families (entity label, multi-hop interaction, blacklist). Use when the user asks how commercial screening tools reason about labeled addresses, tainted flows, or deposit vs withdrawal checks—not for legal sanctions determinations or substituting a vendor’s live rules.
10