armaniferrante-x-status-solana-reference
X post — @armaniferrante (status 1411589629384355840)
Reference skill. This file does not mirror the full text, images, or replies of the post. Open the live URL (or a reputable archive if the post is unavailable) before quoting or summarizing.
Canonical URL
- https://x.com/armaniferrante/status/1411589629384355840
- Query params such as
?s=20are optional; the status id identifies the post.
Author (public roles, for orientation only): Armani Ferrante is widely known in the Solana ecosystem for work including Anchor and Coral-adjacent tooling (verify current bio and affiliations on X).
How to use
- Read primary source — Open the link in a browser (logged-in if required) to capture exact wording, date, and any quote-tweets or media.
- Cite carefully — Social posts are not protocol specifications; pair with repos and docs for engineering truth.
- If the post is unavailable — Prefer Internet Archive snapshots or quoted academic/technical citations; label secondary sources as such.
How to combine with blockint
| Need | Skill |
|---|---|
| Solana program vulnerability patterns (examples) | sealevel-attacks-solana |
| DeFi/Anchor review posture | solana-defi-vulnerability-analyst-agent |
| Solana infra and doc indexes | solana-onchain-intelligence-resources |
Guardrails
- Do not fabricate or “recall” tweet text from memory—verify on X or an archive.
- Not legal or compliance authority — social posts do not replace regulators, contracts, or qualified counsel.
- Harassment — do not use the author’s posts to coordinate doxxing or pile-ons.
Goal: a stable permalink skill for this @armaniferrante status so agents attach correct citations instead of guessing content.
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.
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.
10