Neodyme

• Name: Neodyme
• URL: https://neodyme.io/en/
• Category: security engineering company / Solana-heavy audit operator / public security-report library
• Tags: solana-ecosystem
• Summary: Neodyme belongs in companies/, not only projects/, because the useful question is not just which report did they publish? but which named operator turns Solana-core expertise, public audit publication, consulting, training, and broader security research into part of the practical review workflow teams may rely on? The practical leverage sits less in one PDF than in who curates the report archive, packages specialist review capacity, and keeps shaping how downstream teams interpret Solana-heavy security work.
• What it does:
  • Performs smart-contract and core-blockchain audits, with visible work across DeFi, NFT, liquid-staking, cross-chain, and validator-heavy systems
  • Maintains a first-party public reports index with downloadable reviews spanning projects such as Firedancer, Squads v4, Neon EVM, Marinade, Lido on Solana, Jito MEV Validator, Orca Whirlpools, and Mango v3
  • Publishes broader security research, CVEs, and technical engineering writing beyond the audit pages
  • Positions itself as an early Solana security specialist with long-running core-protocol bug-finding experience
  • Packages audits, consulting, and training under one company boundary rather than as unrelated side activities
• Key claims:
  • The important cut is Solana and core-protocol depth. Neodyme’s public materials lean hard on that lane, and the company boundary matters because specialist review workflow is the real product.
  • The public reports archive is real and current. It stretches into 2026 and covers validators, AMMs, infrastructure, and protocol components rather than a stale handful of marketing samples.
  • Neodyme is more than a PDF shop. The blog and research trail show a broader security practice with genuine technical output.
  • Public claims like auditing Solana since 2020 and reporting 100+ core blockchain bugs are best read as support for the specialist framing, not as evidence that Neodyme should anchor the whole security graph.
• Whitepaper: No classic standalone company whitepaper is the point here. The clearest current sources of truth remain the homepage, blockchain security pages, public reports index, and research blog already captured in ../whitepapers/neodyme-primary-sources-2026-05-04.md.
• Sources:
  • https://neodyme.io/en/
  • https://neodyme.io/en/blockchain/
  • https://neodyme.io/en/reports/
  • https://neodyme.io/en/blog/

Internal linkages

• Project-layer alias: neodyme.
• Useful adjacent company reads: sec3, ottersec, and sigma-prime.
• Useful contrast where the emphasis shifts harder toward formal-methods-heavy tooling: certora.

Protocol / company boundary

• There is no especially useful standalone Neodyme protocol boundary doing the analytical work here.
• The meaningful surface is a company-run security and research workflow: specialist audits, report publication, training, consulting, and the broader authority that comes from being a recognized Solana-core review shop.
• That is why this note belongs in companies/: the sharper question is who supplies and packages the specialist review capacity, not whether Neodyme names a reusable protocol primitive.

Control surface

• Practical leverage sits in reviewer specialization, public-report publication, training and consulting workflow, research agenda, and the implicit security norms teams inherit when Neodyme becomes part of the release process.

• The sticky dependency is workflow authority: once a protocol team treats Neodyme review or advisory posture as part of launch readiness, the company becomes part of the practical assurance perimeter even without holding onchain admin power.

• Read Neodyme as a security-engineering company and specialist review operator first, not as a protocol artifact.

• Last reviewed: 2026-08-11 UTC