Scoping
We map your attack surface against the five walls and tell you which apply. A wall that does not apply is not in the engagement and not in the price.
Tell us what you run.
The conversation starts with what you hold and who can move it, and ends with a written scope: which walls apply, where each boundary sits, and what it costs. Onboarding is performed by an operator rather than a form, because an address set nobody qualified produces alerts nobody can act on.
What to send.
Write to team@fugalabs.xyz. The more of this you can answer up front, the sooner the first call is useful rather than exploratory.
The edge
What you run, and where.
Closed by
The protocol, its chains, and roughly what it holds. A band is enough to start.
The edge
Who can move it.
Closed by
Multisigs, governors and frontends, as counts rather than addresses. Addresses are qualified later, on a call.
The edge
What you depend on and do not control.
Closed by
Bridges, oracles, verifiers, wrapped assets. Usually where the shortest path to your treasury turns out to be.
The edge
Whether software transacts against you.
Closed by
Agents, bots and keepers, yours or somebody else's. It changes which walls apply and how limits are drawn.
The edge
Your response posture, honestly.
Closed by
Including if it is a group chat. Half of an engagement is a rehearsed path from finding to action.
What happens next.
Provisioning
An operator provisions the tenant and qualifies the address set with you. The preset states its boundary in writing before the first alert is routed.
Go-live
Detection runs from the first block, findings route to the channel your on-call already reads, and every alert is a signed, expiring attestation you can verify without us.
Already covered? Sign in. Want the mechanism first? Start with Live Detection, or read the references.
Fuga Labs is read-and-attest, never custody-and-execute.
On-chain capital has no perimeter.
The only question is whether anything is watching from the walls when it matters.