$1,000,000 in security audit grants are live now, Apply here →
Industries · Onchain Teams

The audit ends. The protocol keeps shipping.

Your contracts were reviewed at a commit. Since then you have upgraded twice, added a signer, pointed at a new oracle, and deployed to another chain. Guardian covers the code, the offchain surface around it, and the operational reality that keeps changing after the report is signed.

  • Smart contract audits
  • Pentests
  • Managed Security
What actually has to hold live estate
DEPLOYED CONTRACTS 14 addresses · 4 chains 2 UNREVIEWED SINCE UPGRADE WHO CAN CHANGE THEM S1 S2 S3 S4 S5 3 of 5 multisig one signer left in June WHAT DRIVES THEM Keepers Relayers Oracles Frontend REAL-TIME OPERATIONAL RISK inventory, signers, and exposure tracked as they change

Almost none of this was in the audit scope, and all of it can move funds.

01 · Smart Contract Audits

Three independent passes over the same code.

Two competing teams review the same scope in parallel — one driving expert manual analysis, one driving billions of tokens of frontier AI — while an exhaustive invariant suite fuzzes underneath both. Independent passes find different things. Run together, they leave far less unreached than any one of them does alone.

  • Launches Pre-production review for new protocols, markets, chains, and token systems, scoped by what the code can move.
  • Upgrades and hot fixes Migrations, parameter changes, and governance actions reviewed against deployed state, not only against the diff.
  • Invariant fuzzing An exhaustive suite driving the system through states a reviewer would not think to write down, kept runnable after the engagement.
  • Economic paths Liquidation, pricing, and incentive behaviour tested where being directionally right is still expensive.
  • Incidents Rapid analysis when you need exposure, blast radius, and recovery paths in hours rather than days.
The Guardian Standardthree passes, one scope
Exhaustive Fuzzing All reachable states, edge cases, regressions 0.0%
Team A Expert manual analysis 0.0%
Team B Frontier AI, billions of tokens 0.0%
Your codebase
0.0% Combined coverage

Each figure is that pass's unique contribution: the ground only it reached. What one pass reaches alone is what the other two would have shipped.

02 · Pentests

Nothing onchain has to fail for the funds to move.

The contracts are one surface. The cloud account that can redeploy them, the frontend that decides what a user signs, the keeper that fires a transaction, and the SDK your integrators install are all on the same path to the same assets.

Offchain surface5 engagements
OFFCHAIN Extension Web app API SDK / client libraries Cloud, CI/CD & keepers CHAIN BOUNDARY ONCHAIN Contracts, custody, and the assets themselves A single reachable surface above the line is enough.

Each engagement scales with what the surface can actually do, not with how large it is.

  • Infrastructure pentest Cloud posture and IAM, secrets handling, build and deploy integrity, containers and clusters, and the vendor consoles that can change production.
  • WebApp pentest What the frontend trusts from the API, what a user is actually shown before signing, supply-chain exposure in the bundle, and the flows that move value.
  • API pentest Key scoping, per-object authorization, abuse resistance, and the endpoints that fire relayers, bots, or onchain transactions.
  • SDK audit Transaction construction, key and credential handling, response trust, and the gap between the repository and the published package.
  • Offchain automation pentest Keepers, sequencers, risk engines and oracle update scripts: what fires each run, and what a mistimed, skipped, or duplicated run does onchain.
$45B+In digital assets secured across Guardian engagements
300+Critical vulnerabilities reported and resolved
150+Teams trusting Guardian with their contracts
25+Global security competition wins
03 · Managed Security

Everything the audit scope never covered.

An audit is a point in time over a subset of your system. Managed Security is the rest of it, held continuously: who can sign, what is actually deployed, what faces the internet, and what changed this week that nobody reviewed.

  • Operational security and controls Access and permissions across every system, secrets handling, release and change control, environment separation, and incident runbooks rehearsed before they are needed.
  • Shield Continuous coverage of internet-facing surfaces and networks: hosts, ports, storage, TLS and certificates, edge rules, DNS and registrar control, each finding verified by an engineer.
  • Multisig management Signer set and threshold reviewed as people join and leave, signer device hygiene, transaction simulation before approval, and recovery that has been tested rather than assumed.
  • Contract inventory Every address you have deployed, on every chain, with its owner, its upgrade path, and whether the code running today is the code that was reviewed.
  • Real-time operational risk tracking Changes to the estate surfaced as they happen: a new deployment, a rotated signer, a permission granted, an unreviewed upgrade going live.
Operational risk, trackedlive
CONTRACT INVENTORY 16 addresses · 4 chains 2 running unreviewed code SIGNER SET 3 of 5 · threshold unchanged 1 departed, key still valid CHANGE FEED · LAST 7 DAYS Vault implementation upgraded — not reviewed OPEN New keeper address granted operator role OPEN Oracle source swapped on the perps market CLEARED Staging host exposed on 0.0.0.0, closed CLEARED

The question this answers is the one an audit cannot: is what is running right now still the thing that was reviewed.

Bring us your highest-value system.

Whether that is the next launch, the upgrade going out on Thursday, or the estate you have not had a clear picture of in a year.

Get an audit