Blaize

Blaize Security is the security audit arm of the Blaize development company, offering smart contract, dApp, blockchain network and wallet audits along with incident investigation and monitoring. Its public GitHub report repository shows unusually broad language coverage for a firm of its stated size, including Solidity, Move on Sui (for Mysten Labs and Blockus) and Cairo (StarkDeFi). The main caution for buyers is recency: the newest public report and blog post found in this pass date from late 2024.

At a glance

Founded	not verified (not stated on the firm's security pages)
Headquarters / jurisdiction	not published on the security site
Engagement model	private firm audit, with post-audit consulting and monitoring (process)
Core specialties	smart contract, dApp, network and wallet audits; technical due diligence; incident investigation (homepage)
Ecosystems / languages	EVM (Solidity, Vyper), Rust (NEAR, Solana), Move (Sui, Aptos), Cairo, others per FAQ; public reports evidence Solidity, Move and Cairo
Public report index	GitHub: blaize-security-audits; linked portal audits.blaize.tech did not resolve
Open-source tooling	none found (GitHub org)
Published pricing	not published; FAQ says a quotation is prepared within 24 hours

What they do

The homepage lists smart contract audits, dApp security audits, blockchain network audits, wallet audits, enterprise solution audits, technical due diligence, security CI/CD building, security incident investigation and proactive protection/monitoring (homepage). It states the team has 25+ auditors (the homepage's figure) and has secured 230 projects across 25 ecosystems; these are self-reported (homepage). The directory team size is 40+.

The published process has four stages (strategy, deep code analysis, testing, report) and lists manual review, static analysis, business-logic verification, fuzz and mutation testing, unit-test coverage analysis and fix verification. The firm says auditors keep consulting the client until issues are resolved and offers secondary audits and code-update reviews after the engagement (process). The FAQ says reports belong to the client and are published only with permission, and that scheduling waits are no longer than a week (FAQ).

Specialties and ecosystem coverage

The FAQ claims support for Solidity and Vyper on any EVM chain, Rust (NEAR, Solana, Secret Network), Substrate, Move (Aptos, Sui), Cairo (StarkNet) and Motoko (FAQ). The public GitHub repository evidences a subset: EVM work (1inch, Everstake, FortiFi on Avalanche, AvaxApes), Sui/Move work (Sui Multisig and Sui SDK by Mysten Labs, Blockus), Cairo work (StarkDeFi), NEAR-ecosystem work (Aurora, Rainbow Bridge) and Dusk's Kadcast networking layer (report repo). The Blockus case study confirms a Move audit on Sui (Blockus case study).

Against the directory: the notable audits listed (Everstake, Rainbow Bridge, Mysten Labs, StarkDefi, Dusk) all have public reports in the repository. The directory's chain list is EVM-only; the public record also shows Sui, StarkNet and NEAR-ecosystem work that the list omits. Base and Optimism are not evidenced in report titles.

Recent public work

Pulled from the file listing of the GitHub report repository, newest first (dates are those in the file names). No reports dated after December 2024 were found.

• Aut Labs (token repfi), December 4, 2024
• Lockon Finance (Adjuster), November 15, 2024
• LFIT v2, August 30, 2024
• BrainStarter, August 28, 2024
• WEPC, July 18, 2024
• DigitalOriginal, June 28, 2024
• E Money Network, June 7, 2024
• Kadcast by Dusk, April 17, 2024
• Blockus (Sui), March 12, 2024 (case study): 1 low and 4 informational findings, all resolved
• StarkDeFi Locker, February 19, 2024

Research, tooling and methodology

No open-source security tooling was found; the GitHub organization shows the reports repository and one other repository (GitHub org). The process page cites OWASP and CCSSA standards as references for code analysis (process). Case studies end with a numeric "final score" (Blockus received 10/10) (Blockus case study); a full severity scheme was not found on the pages loaded. The blog's most recent post is a 2024 year-in-review dated December 26, 2024 (blog).

Track record and incidents

No reputable post-audit incident naming Blaize as the auditor of exploited code was found in this pass.

Who should consider them — and who might look elsewhere

The public record fits teams on less common stacks who want one vendor across them, such as Sui/Move, Cairo or NEAR-ecosystem bridges alongside EVM contracts, and teams that also want due diligence or CI/CD security help. Buyers who weigh recent public output heavily should ask for current references, since no public reports or research after December 2024 were found. There is no public evidence of open-source tooling or formal verification.

How to engage

The site lists security@blaize.tech as its contact address and says a quotation is prepared within 24 hours (homepage, FAQ). Ask up front whether the report will be published, since the FAQ says publication requires client consent.

Gaps and unverified claims

• No public reports or blog posts dated after December 2024 were found; the GitHub reports repository's last push was 2024-12-06 (per the GitHub API, checked 2026-09-24).
• The report portal audits.blaize.tech, linked from the firm's site, did not resolve (DNS lookup failure) on 2026-09-24.
• Founding year (the directory lists 2018) and headquarters are not stated on the security site.
• The homepage's self-reported team size is 25+ auditors (the homepage's figure). The directory team size is 40+. Project count (230) is self-reported.
• The repository file listing had 57 PDF files on 2026-09-24, of which 4 are compressed/uncompressed duplicates, giving 53 distinct reports; the README says other cases are confidential.
• No public reports, blog posts or news dated 2025 or 2026 were found as of 2026-10-14; the site's own copyright notice ends at 2024 (homepage). The site is live and carries no closure notice, but confirm the firm is taking engagements before planning around it.

Sources

1. Blaize Security homepage, accessed 2026-09-24
2. Blaize Security audit process, accessed 2026-09-24
3. Blaize Security FAQ, accessed 2026-09-24
4. GitHub: blaize-security-audits, accessed 2026-09-24
5. GitHub: blaize-security organization, accessed 2026-09-24
6. Blockus audit case study, accessed 2026-09-24
7. Blaize Security blog, accessed 2026-09-24