Use Cases
Flows from our customers and research to best leverage Guardrail's capabilities
For most teams with live products, monitoring on-chain contracts is an extension of monitoring other parts of their application stack (frontend, backend, api etc).
If you're interested in learning how to set up monitoring effectively, we have
a monitoring 101 guide on our blog
past hacks detailed with guards to detect them, and
guides we share during onboarding to ensure maximum coverage and efficent set ups.
Every team on Guardrail has access to our suite of detection and response options. Teams can implement a single guard and single response or set up complete security workflows for any scenario.
Detection
Guard categories and examples
Guardrail supports different detection mechanisms, mostly covered by Invariants, Health Checks, or Suspicious Transactions. These are built using a team's experience in security and protocol design and our researched guards for every protocol component. More details in Creating Guards.
Response
Guardrail acts as a workflow engine for executing response actions tied to each guard.
Critical Cases (e.g., treasury drains, admin changes): Guardrail can page your team, adjust protocol settings, propose pauses, or trigger custom actions via webhook.
Operational Security (e.g., token changes, governance approvals): Guardrail sends info alerts to community members or team members with relevant context for each trigger.
Unauthorized Protocol Activity: Guardrail flags suspicious attempts, functioning like Two-Factor Authentication for critical protocol changes.
Monitoring Dependencies: Guardrail triggers fallbacks and alerts for critical components when necessary.
User or Protocol Risk Workflows: These alerts update protocol parameters or notify protocol users based on guards.
Other supported security flows include: Rugpull Detection, Airdrop Security Scans, Off-Chain Security Checks; all these can be integrated into custom response flows tailored to your design.
Guardrail's Success Criteria: Our platform is built around four key principles:
Consolidation: Unify your security processes in one place.
Simplification: Streamline complex workflows.
Standardization: Apply consistent practices across your protocol.
Automation: Reduce manual intervention through automation
Last updated