Awesome Solana: curated lists that actually help — security map and the rest of the shelf
How to use Solana “awesome” lists as a builder map. Lead example: accretion-xyz/awesome-solana-security — start-here path, tools, CTFs, audits — plus the other high-signal awesome repos (AI, NFTs, OSS, Blinks, MCP).
devrels.xyz/a/186short linkAwesome Solana: curated lists that actually help — starting with Accretion’s awesome-solana-security, then the rest of the shelf builders keep open in a second tab.
Example list: github.com/accretion-xyz/awesome-solana-security. Accretion: accretion.xyz. X: @accretionxyz. Format origin: awesome.re.
What an “awesome” list is (and is not)
An awesome list is a community-maintained, often opinionated index of links — courses, tools, papers, postmortems — usually under a single GitHub README with the Awesome badge. It is a map, not a standards body.
- Is: a fast way to find primary sources and known-good starting points for a domain.
- Is not: an endorsement, a security guarantee, or a substitute for reading the actual docs and code.
- Quality signals: clear scope, start-here path, link checks CI, CONTRIBUTING rules, honest “commercial” labels, preference for primary sources over SEO blogs.
Lead example: Awesome Solana Security (Accretion)
accretion-xyz/awesome-solana-security describes itself as an opinionated map for building, reviewing, breaking, and defending Solana systems. It favors primary sources, reproducible research, public reports, and tools useful in real review work — and it says inclusion is not endorsement.
Responsible-use banner is upfront: only test what you own or have permission to assess; respect bounty/CTF scope.
Start-here path (their order)
- Solana Program Security Course — concepts first; verify APIs against current docs (course archived).
- Hitchhiker’s Guide (Helius)
- 100 Solana Tips (Accretion)
- Sealevel Attacks
- Solana Common Attack Vectors (Ackee)
- Verified Builds
- security.txt
How the rest of the list is organized
Awesome Solana Security (map)
├── Secure program development
│ accounts / PDA / CPI / Token-2022 / arithmetic / deploy+upgrade
├── Security tools
│ AI review · static/formal · fuzz/sim · RE · Rust hygiene
├── CTFs, workshops, vulnerable programs
├── Research papers & ecosystem studies
├── Security blogs & research teams
├── Hacks, postmortems, disclosures
├── Public audit reports
├── Operational security & IR
├── Bug bounties & audit competitions
└── Related / historical listsThat structure matches how reviews actually run: threat model and account checks first, tools second, historical failures third, ops last. Tooling section is explicit that scanners accelerate review — they do not prove safety.
How to use any awesome list as a builder
- Pick the domain list — security vs AI vs NFT vs OSS — don’t mash them.
- Read the start-here / TOC before deep-linking random tools.
- Prefer primary sources (docs, repos, reports) over summary threads.
- Pin commits when you install agent skills or CLI scanners from a list.
- Check CI badges (broken-link bots) — dead links are the main failure mode of awesome repos.
- Mark commercial vs open in your own notes; lists sometimes mix both.
The broader Solana awesome shelf
Accretion’s security list is new and focused. These are the other high-signal shelves that show up constantly in Solana DevRel work (stars as of research time — check live):
| List | Domain |
|---|---|
| 0xMacro/awesome-solana-security | Long-running security resource collection |
| az0mb13/awesome-solana-security | Another security-oriented curated set |
| helius-labs/solana-awesome | Broad factual hub (infra, clients, ecosystem) |
| solana-foundation/awesome-solana-ai | AI tooling to build on Solana |
| sendaifun/awesome-solana-mcp-servers | MCP servers for agent workflows |
| ilmoi/awesome-solana-nfts | NFT protocols and tools |
| StockpileLabs/awesome-solana-oss | Open-source Solana repos |
| solana-developers/awesome-blinks | Blinks / Actions |
| paul-schaaf/awesome-solana | Classic general Solana awesome |
| openSVM/awesome-svm | SVM-wide resources |
For security work, start with Accretion + 0xMacro and cross-check; for product discovery, Helius / Foundation AI / Blinks lists; for agents, MCP + AI awesomes.
When to contribute (or fork)
- Dead link with a known replacement
- Primary source missing (official doc, not a blog remix)
- New public audit report or postmortem with real technical content
- Tool became commercial or deprecated — update the label, don’t ghost it
Fork when you need a private team checklist (e.g. internal review gate). Keep the public PR path for things that help the whole ecosystem.
DevRels angle
Awesome lists are DevRel infrastructure: onboarding maps, workshop handouts, “where do I start with X?” answers. Better to link a maintained list + a 5-item start path than paste 40 URLs into a Discord reply. When you publish a deep dive on DevRels, ask whether it belongs on the relevant awesome shelf — and whether your article points back to primary sources the list already tracks.
Resources
- accretion-xyz/awesome-solana-security
- 100 Solana Tips
- 0xMacro security awesome
- helius-labs/solana-awesome
- awesome-solana-ai
- awesome.re
- Range (risk/compliance) · Accretion on DevRels
Bottom line
Treat Awesome lists as living maps with maintainers and opinions. Accretion’s Solana security list is a strong modern entry point: start-here path, tool caveats, CTFs, audits, ops. Keep the rest of the shelf for AI, NFTs, OSS, and Blinks. Always click through to primary sources — the list is the index, not the lesson.
Keep reading
An audit report is worthless if you can't confirm the deployed bytecode is what was audited. Solana verified builds fix that: a Docker-pinned toolchain produces a deterministic .so, its hash is compared to the on-chain program data, and the result is written to a PDA anyone can read. Solana Explorer shows a verified badge. Here's the full workflow.
Cold storage reduces malware risk; it does not invent randomness. Pick Solana-capable hardware, generate seeds on-device, and treat entropy like tier-0 security.
Agents already call APIs — and already fail with 400s, leaked keys in mcp.json, and poisoned skill files. Gecko is the comprehension layer: docs → first-call-correct tools, keys injected only at call time, recorded mode before you spend. Here is the product map for Solana builders.
Get new articles in your inbox
Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.
