ChainLight

• Name: ChainLight
• URL: https://chainlight.io/
• Category: blockchain security company / public audit-and-research operator / digital-asset risk-intelligence workflow shell
• Tags: ethereum-ecosystem
• Summary: ChainLight belongs in companies/, not only projects/, because the useful question is not what protocol did ChainLight build? but which named operator packages audits, public track-record curation, DART risk scoring, and ecosystem-security research into one workflow boundary that downstream teams may start treating as practical assurance infrastructure? The strongest first-party evidence still points to an operator shell: the company sells tailored audits, frames a five-phase review process, curates a public record through the Theori-linked web3-publications repository, and extends into DART as a separate risk-management product. That is a company control surface, not a standalone protocol.
• What it does:
  • Performs smart-contract and broader blockchain security audits with a staged workflow spanning intake, strategy, examination, consultation, and final reporting
  • Maintains a public track-record and publications corpus through the theori-io/web3-publications repository, including disclosed audit work, competition results, and broader security credentials
  • Operates DART (Digital Asset Risk Tracker) as a separate risk-management and monitoring surface for users, exchanges, and builders
  • Publishes security and ecosystem research that frames ChainLight as an ongoing risk-intelligence operator rather than only a one-off audit vendor
  • Packages white-hat reputation, competition pedigree, disclosed reports, and live risk tooling into one branded trust shell
• Key claims:
  • The homepage says ChainLight was established in 2016 and presents an award-winning team of white-hat hackers providing tailored security solutions for smart contracts and blockchain products, which is explicit company-boundary language rather than protocol language
  • The homepage says ChainLight has a proven track record of zero client compromises and positions DART as revealing concealed threats beyond standard risk assessments and audits, which matters because it frames one named operator as both auditor and ongoing risk-intelligence vendor
  • The security-audit page describes a five-phase process covering request intake, audit strategy and quote, real-time security analysis, consultation and fix review, and a final certified report, showing that ChainLight is packaging a repeatable workflow rather than publishing isolated reports
  • The public web3-publications repository explicitly describes itself as Web3 Audits, Publications, and Track records by ChainLight of Theori, says the team entered the Web3 security market in earnest after exchange-security consulting, and uses the repo as the public archive of disclosed work and track record
  • The same repository ties ChainLight to public results such as Ethereum bug-bounty placement, Paradigm CTF success, and disclosed reviews for KLAYswap, Orbit Bridge, MESHswap, Klaytn governance contracts, and Blur Blend, reinforcing that public reputation curation is part of the company surface
  • Taken together, the useful analytical unit is not a ChainLight protocol; it is a named security operator deciding what to audit, what to publish, how to frame its track record, and how to expand from audits into risk-management products like DART
• Whitepaper: No classic standalone company whitepaper is the point here. The clearest current primary materials are the official site, the security-audit page, and the public web3-publications repository; the earlier source bundle remains ../whitepapers/chainlight-primary-sources-2026-05-04.md.
• Sources:
  • https://chainlight.io/
  • https://chainlight.io/security-audit
  • https://raw.githubusercontent.com/theori-io/web3-publications/master/README.md
  • ../whitepapers/chainlight-primary-sources-2026-05-04.md

Internal linkages

• Project-layer alias: chainlight.
• Useful adjacent company reads: chainsecurity, dedaub, and slowmist.
• Useful contrast where the emphasis shifts from one operator’s review-and-risk shell to a more contest-centric marketplace workflow: codehawks.

Protocol / company boundary

• There is no especially useful standalone ChainLight protocol doing the analytical work here.
• The meaningful surface is the company-run review and risk-intelligence shell: audit workflow, public track-record curation, DART-style risk presentation, and the security research framing attached to the brand.
• That is why ChainLight belongs in companies/: the practical questions are about who publishes findings, curates trust signals, defines the review process, and packages risk outputs into an ongoing operator relationship.

Control surface

• Practical leverage sits in what ChainLight chooses to review, publish, certify, score, and present as meaningful security or risk signal.

• The sticky dependency is workflow authority: once a team, exchange, or user starts treating ChainLight reports, certifications, or DART outputs as operational truth, the company becomes part of the effective assurance perimeter even without controlling onchain admin keys.

• Read ChainLight as a security-review and risk-intelligence company first, not as a standalone protocol or product primitive.

• Last reviewed: 2026-08-12 UTC