Skip to content
Opt-in Ships disarmed

The Circuit Breaker. Refusal at your own boundary.

Detection is a claim about what is happening. This is the contract that acts on it, and you deploy, own and revoke it. Fuga Labs signs a statement and never touches the brake, which is why a total compromise of us buys an attacker one alert and nothing else.

Default stateDisarmedRungs to armed4Mechanisms2RevocationOne transaction, yoursKeys we holdNone

Two ways to prevent something. Only one is fast enough.

This is the distinction the category is most often sold past. The Circuit Breaker is opt-in and ships disarmed; what follows is what it does once you arm it.

Mechanism 01

Inside your transaction

Your contract asks its own policy contract before it acts. When a transaction fails your rules it reverts inside that same transaction, with no round trip to us and no dependency on us being alive. This is the half that stops an atomic exploit.

Works with Fuga Labs completely offline.

Mechanism 02

By tightening the policy

A finding arrives and the standing policy gets stricter: a lower cap, a restricted account, a paused scope. This is slower than the transaction that triggered it, which is why it answers the other shape of attack, the drains that take minutes rather than microseconds.

Both are real. They answer different attacks.

Anyone who tells you a detection service stops a single-block exploit through an off-chain pipeline is selling the second mechanism described as the first. Both are real, both ship, and they answer different attacks.

Four rungs, and you climb them.

The path a deployment travels. The order is a recommendation; what is enforced sits on the last two rungs, neither of which publishes until the shadow period has earned it.

  1. Step 1

    Disarmed · config:write

    Every deployment starts here and publishes nothing at all. It is also where the kill switch returns it, in one transaction you hold, without asking us and without waiting for us.

  2. Step 2

    Shadow · config:write

    It evaluates everything and still publishes nothing, recording what it would have done against your own live traffic. This is the rung that manufactures the evidence the next two are gated on.

  3. Step 3

    Canary · actuation:arm

    It publishes for an explicit allowlist of subjects under a tightened ceiling. Refused outright until the shadow period clears a measured soak, enough distinct subjects, and no legitimate transaction that would have been reverted.

  4. Step 4

    Armed · actuation:arm

    It publishes for every subject under the policy you set. Each attestation carries a mandatory expiry, so nothing this breaker holds ever becomes a standing authority over your protocol.

The two publishing rungs need a different credential from the two safe ones. Stopping actuation never waits on whoever holds the arming key, and the kill switch returns a deployment to disarmed from any rung.

Which walls can drive it.

One breaker, five sources. A wall does not ship a brake of its own; it reaches the same policy contract you already deployed.

The edge Live Detection
Closed by Owns it. Findings from the pending pool, from forked simulation and from signature time are what the breaker acts on, and the policy contract ships with this wall.
The edge Exposure Map
Closed by Sets how far it may go. Without a blast radius the ladder cannot exceed notify, because a proportional response needs a number and there is not one.
The edge Asset Ratings
Closed by Tightens where the structure is weaker, so the same policy can hold a lower ceiling against a fragile asset than against a robust one.
The edge AI Agent Guardrails
Closed by Reuses the contracts rather than deploying its own. An agent's spending limits are the same bounded-authority modules, already owned by you.
The edge Ops Monitor
Closed by Feeds it the half a chain view cannot see. A signer anomaly or a frontend change reaches the same policy as an on-chain finding does.
Fuga Labs is read-and-attest, never custody-and-execute.
The cardinal ruleThe breaker is the sharpest test of it, and it holds

Nothing is armed until you arm it.

A scoping call decides which wall drives the breaker, what its one bounded action is, and what evidence must accumulate before you arm it. All three are written down first.