Spearbit

• Name: Spearbit
• URL: https://spearbit.com/
• Category: security-review network / curated auditor collective / legacy premium-report lineage inside Cantina
• Summary: Spearbit belongs in companies/, not projects/, because it was never a protocol or product surface doing the main analytical work. The useful question is which named researcher network admitted auditors, packaged high-trust reviews, published a recognizable report corpus, and now survives as a premium review lineage inside Cantina. That entity boundary matters because reviewer selection, report authorship, and the commercial packaging of Spearbit reports were operator choices, not neutral protocol behavior.
• What it does:
  • Operated a curated network of security researchers performing bespoke reviews and other security services for web3 teams
  • Published a substantial first-party public report corpus through the portfolio repository, with recent engagements linking out to Cantina-hosted portfolio pages
  • Maintained educational and researcher-development material through the public armory repository rather than existing only as a private client-service brand
  • Now presents itself as living inside Cantina, where the Spearbit label persists as a recognizable report and expert-network lineage rather than a fully separate platform
• Key claims:
  • The Spearbit homepage currently resolves to a minimal message that Spearbit now lives on Cantina, which is the cleanest first-party statement that the standalone brand has been folded into a broader operator shell
  • Cantina’s current materials still preserve Spearbit as a distinct historical/security-workflow lineage, which matters because users and protocols still encounter Spearbit reports as a meaningful trust label even after the merge
  • The public portfolio repository describes Spearbit as a network of expert security engineers offering reviews and other security-related services to web3 projects, with experience ranging from protocol design to smart contracts and the Solidity compiler
  • The same repository says Spearbit enabled expert freelance auditors seeking flexibility to work on interesting projects together, which makes the operator boundary useful: this was a curated auditor network and workflow shell, not merely a report website
  • The armory repository frames itself as a one-stop educational corpus for blockchain security researchers, reinforcing that Spearbit also shaped researcher training and public security knowledge distribution
  • Recent portfolio entries route to cantina.xyz/portfolio/... report pages, showing that the live report-publication and customer-facing workflow surface has migrated into Cantina even while the Spearbit label remains analytically useful
• Whitepaper: No canonical Spearbit whitepaper is the point here. The strongest primary materials are the redirecting homepage, Cantina’s current platform surface, the Spearbit public portfolio, and the armory repository; see ../whitepapers/spearbit-primary-sources-2026-04-28.md.
• Sources:
  • https://spearbit.com/
  • https://cantina.xyz/welcome
  • https://github.com/spearbit
  • https://github.com/spearbit/portfolio
  • https://raw.githubusercontent.com/spearbit/portfolio/master/README.md
  • https://github.com/spearbit/armory

Internal linkages

• Project-layer alias: spearbit.
• Current operator shell that absorbed the brand: cantina.
• Useful adjacent security-marketplace contrast: sherlock.
• Useful audit-network comparison from a more traditional operator shape: trail-of-bits.

Protocol / company boundary

• There is no especially useful standalone Spearbit protocol boundary doing analytical work here.
• The meaningful surface was always the curated expert network, reviewer selection, report-publication lineage, and the operator-managed trust label attached to those reviews.
• That is why this note belongs in companies/: the practical question is who assembled the experts and packaged the output, not which neutral primitive users integrated.
• The current wrinkle is that much of the live workflow shell now sits inside cantina, so this note should be read as an entity / lineage note rather than as a separate active platform competing on equal footing with Cantina.

Control surface

• Practical leverage sat in who got admitted to the network, who led or staffed reviews, how findings were packaged into public reports, and how the Spearbit label signaled review quality to protocols and downstream readers.

• Today, that leverage is partly historical and partly inherited by Cantina’s broader operator shell, because report hosting and the current commercial workflow moved there.

• The taxonomy win is simply keeping Spearbit out of projects/: this is an operator and brand boundary in the security-review market, not a protocol or mechanism note.

• Last reviewed: 2026-08-13 UTC