Usual Tech Docs
Usual WebsiteGeneral DocsContract DeploymentsAuditsAccess dApp
  • 🚀GM GM
    • Usual Tech Hub
  • 🔭Overview
    • Usual Protocol Primer
    • Features
      • Mint & Redeem Engine
      • USD0
      • USD0++
      • USUAL
      • USUAL*
      • USUALx (USUAL staking)
      • USUAL distribution
      • USUAL Airdrop
      • Usual USD0++ Investment Vault
    • Architecture
      • Role Management
      • USUAL Distribution Model
  • ⛓️Smart Contracts
    • Protocol Contracts
      • DaoCollateral
      • Swapper Engine
      • USUAL staking
      • USUAL* Vested Allocation Staking
      • USUAL Distribution
        • Distribution Module
        • Yield Module
      • Airdrop Module
    • Token Contracts
      • USD0
      • USD0++
      • USUAL
      • USUAL*
      • USUALx
      • Usual USD0++ Investment Vault
        • VaultRouter
    • Utility Contracts
      • ClassicalOracle
      • Abstract Oracle
      • Chainlink Oracles
      • Pyth Oracles
      • RedStone Oracles
    • Real World Assets
      • USYC (by Hashnote)
      • M (by M0)
        • UsualM
      • USDtb
    • Contract Deployments
  • 🛡️Security & Audits
    • Security Practices
    • Testing Framework
    • Monitoring Framework
    • Audits
    • Bug Bounty
  • 🧩Integrations
    • Integrate USD0++
      • Reward redistribution by integration partner
      • Claim Address Redirect
      • Daily Distribution powered by Brevis (coming soon)
  • 📚Resources
    • Community & Support
    • References
  • 📖Support
    • FAQ
    • Glossary
  • ⚖️Legal
    • Terms of Services
    • Legal Notice
    • Privacy Policy
Powered by GitBook
On this page
  • Passive Monitoring
  • Active Monitoring

Was this helpful?

  1. Security & Audits

Monitoring Framework

Our security operations provides 24/7/365 monitoring of the Usual protocol. This ensures that any potential issues or anomalies are detected and addressed promptly.

Passive Monitoring

This foundational level focuses on monitoring the critical components that form the backbone of our protocol's security:

  • Critical Role Monitoring: Continuous tracking of all accounts with elevated privileges within the system.

  • Multisig Activity: Real-time monitoring of all multisignature wallet activities to ensure proper authorization of significant actions.

  • Key Event Tracking: Vigilant observation of crucial events such as:

    • Changes in role assignments

    • Updates to proxy implementations

    • Administrative changes

Any activity at this level triggers immediate notifications to our security team for verification and response.

Active Monitoring

This level involves monitoring the operational aspects of our protocol to detect any deviations from expected behavior:

  • Contract State Changes: Tracking significant state changes across all protocol contracts.

  • Mechanism Monitoring: Continuous oversight of key protocol mechanisms, including:

    • Collateral Backing Ratio (CBR) activations and deactivations

    • Pausing and unpausing of contract functionalities

    • Activities within the DaoCollateral and SwapperEngine contracts

  • Threshold Alerts: Notifications triggered by unusual transaction volumes, large token movements, or unexpected price fluctuations.

Anomalies detected at this level prompt immediate investigation by our security and development teams.

Automated defense mechanisms

Our highest level of security involves automated circuit breakers that immediately pause contract operations in response to critical security events:

  • Asset Protection: Automatic pause triggers in response to suspicious movement of protocol funds

  • Protocol Integrity: Immediate response to unexpected changes in core protocol metrics, balances, and under collateralization.

  • Access Security: Detection and response to potential security access anomalies

  • Smart Contract Safety: Automated protection against suspicious contract interactions that could impact protocol security

These automated defense mechanisms serve as the protocol's last line of defense, automatically pausing relevant contract operations when critical security thresholds are breached. This "circuit breaker" approach ensures the protocol can enter a safe state while our security team investigates and responds to potential threats.

PreviousTesting FrameworkNextAudits

Last updated 6 months ago

Was this helpful?

🛡️
Page cover image