Solera
  • Introduction
    • 💡About Solera
  • 🔗Links
  • Overview
    • 🌅Getting Started
      • Core Concepts
      • Market Types
    • 🤝Lending & Borrowing
      • Supplying Collateral
      • Interest Rates
      • Collateral & Liquidations
      • Oracles
    • 🦋Morpho Markets
      • Earning
      • Borrowing
    • 💹Strategies
    • 🏦Vaults
    • 💱Swap
  • 🌱Liquid Staking
  • 📲Savings Accounts
  • Protocol
    • 📊Parameters
    • 🕵️‍♂️Audits
    • ‼️Risks
      • Smart Contract Risk
      • Bad Debt Risk
      • Oracle Risk
    • 🔒Risk Management
      • Risk Parameters
        • Asset-level
        • Account-level
      • Liquidations
      • Operational Security
  • Developers
    • 🟠sTokens
    • ⌨️Solera SDK
    • 💾Contract Addresses
    • 🤖Operating a Liquidator Bot
  • Operations
    • Disclaimer
    • Terms of Service
    • Restriced Geolocations
Powered by GitBook
On this page
  1. Protocol
  2. Risk Management

Operational Security

How Solera protocol contributors work to reduce operational risks

Multi-Party control

Every code upgrade and treasury transaction must be approved by a 3/3 multisig. This is enforced through a multisignature contract which only allows code upgrades when all signers have signed the upgrade with a cold storage wallet.

2FA

All accounts of the protocol, administrators, and moderators are secured by two factor authentication using an authenticator app, reducing the likelihood of access being granted to a malicious actor via methods such as sim-swapping.

Audits

Our auditors have checked for centralization risks when auditing . This means that potential backdoors, deliberate exploit opportunities and other risks are reported by the auditor with or without the contributor's approval.

Visit Audits to learn more

PreviousLiquidationsNextsTokens

Last updated 1 month ago

🔒