Response

Response on Guardrail is built around standardizing flows and being prepared. Built with similar concepts as our guards (stateless, independent), responses are stored on Guardrail's server and are invokable at any time based on a guard's result, either OK or NOT_OK.

Most commonly, teams either set up an alert to be notified by Guardrail (Slack, Discord, Pagerduty) or use our Webhook to trigger an action on their end. Under specific circumstances, we can also connect to non-standard response flows by working closely with teams to understand these particular cases, their risk appetite, and balancing risk with damage limitation.

Known Risks

Transactions flagged by Guardrail as anomalous, or violating a protocol's key invariant defined ahead of time, serve to inform teams early of risky behavior to limit damage, and, in some cases, to take action on the underlying vulnerability at the first instance of detection.

Operational Security

For ongoing security requirements, responses from Guardrail can serve as an intelligent coordination layer. Examples of this include governance notifications, multisig change notifications, and treasury rebalancing. These flows can be a common entrypoint for bad actors and having events with intelligent context is key to being informed.

Critical Responses

In response to a critical single guard or combination of guards, response actions can be triggered autonomously to take critical protocol actions such as A) modifying a protocol mode, for example limiting funds to be transferred in a single direction, B) moving funds to a predefined address or C) temporarily pausing affected contracts.