Cowrie Research

ackee-blockchain

4 min read

Ackee Blockchain

  • Name: Ackee Blockchain
  • URL: https://ackee.xyz/
  • Category: smart-contract security company / security-tooling steward / blockchain-security education operator
  • Tags: ethereum-ecosystem solana-ecosystem
  • Summary: Ackee Blockchain belongs in companies/, not projects/, because the useful question is not what audit report exists? or even what fuzzer exists? It is which named operator packages audit workflow, reusable tooling, signed report publication, and structured training into one company-run security shell that downstream teams may start treating as part of their normal review baseline. The practical leverage sits less in any one engagement than in who maintains Wake and Trident, who publishes the signed report corpus, and who teaches the developer-and-auditor pipeline around those tools.
  • What it does:
    • Performs smart-contract and protocol security reviews across Ethereum, Solana, and other EVM-based systems
    • Maintains Wake, a Python-based Solidity development, testing, and fuzzing framework with built-in detectors, printers, GitHub Actions support, and IDE tooling
    • Maintains Trident, a manually guided fuzzing framework for Solana programs written in Rust with flow-based stateful fuzzing and regression-testing support
    • Publishes a public archive of signed audit reports, which turns the company into a reusable report-and-methodology surface rather than only a private services firm
    • Runs structured education and training programs such as School of Solana, tying auditor training and developer onboarding directly to Ackee’s tools and review workflow
  • Key claims:
    • Ackee’s homepage says its mission is to strengthen the blockchain ecosystem through security services, tooling, and education, which is the clearest first-party framing for why this belongs as an entity note
    • The same homepage says Ackee performs comprehensive audits for Solana, Ethereum, and EVM-based projects and highlights clients such as Lido, Safe, Axelar, 1inch, and Trezor, reinforcing that the company sits in real production review paths
    • Wake’s docs describe a Python-based Solidity framework with pytest-style testing, property-based fuzzing, detectors, printers, static-analysis extensibility, GitHub Actions support, and a language server, showing that Ackee maintains a substantial developer-tooling surface rather than a one-off internal script
    • Trident’s README describes the framework as a manually guided Solana fuzzer with stateful and flow-based fuzzing, Anchor-like macros, and regression testing, and it explicitly says the tool is built and maintained by Ackee Blockchain Security
    • The public-audit-reports repository says it collects public security audit reports produced by Ackee Blockchain Security and includes matching signature files for report verification, which is unusually strong evidence of a durable publication-and-authenticity workflow
    • School of Solana’s README says the course is certified by Ackee Blockchain and positions the curriculum as a free structured path for learning Rust, Solana development, and security, which makes the training pipeline a first-class operating surface
  • Whitepaper: No classic standalone Ackee company whitepaper is the important artifact here. The clearest current primary materials are the official Ackee site plus the Wake, Trident, public-audit-reports, and School of Solana repos/docs; see ../whitepapers/ackee-blockchain-primary-sources-2026-04-30.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • There is no especially clean standalone Ackee protocol boundary doing the analytical work here.
  • The meaningful surface is the company-run mix of audits, Wake, Trident, signed report publication, and structured training that sits around other teams’ build-and-review workflows.
  • That is why Ackee Blockchain belongs in companies/: the practical questions are about who stewards the tooling, who publishes the reports teams may reuse, and who shapes the security education pipeline other builders inherit.

Control surface

  • Practical leverage sits in which bug classes Ackee codifies into Wake or Trident workflows, which audit findings get preserved in its signed public corpus, and which review habits or Solana/EVM security lessons get normalized through its training pipeline.

  • The company does not directly control the protected protocols, but it can shape what teams test, how auditors reason, and which security practices become routine before deployment.

  • Read Ackee as a company-run security-tooling, report-publication, and education boundary first, not as a neutral protocol primitive.

  • Last reviewed: 2026-08-07 UTC

Graph View

Backlinks