Saga Docs
Back to Saga
  • Introduction
    • Pegasus Overview
    • Saga Overview
      • Saga Topology
      • Saga Chainlets
      • Saga Shared Security
      • Validator Orchestration Tools
      • Token Mechanism and Economics
      • Validator Selection
      • Partnership Models
      • Paying for Chainlets
      • Staking on Saga
        • Staking your Saga on Keplr
        • Auto-compound your staking rewards with Restake.app
  • Saga Web App
    • Getting Access
    • Quickstart Guide
      • Testnet Quickstart Guide
      • Mainnet Quickstart Guide
    • Account Management
      • Requesting Tokens from Saga Faucet
      • Deposit Funds into Escrow
      • Withdraw Funds from Escrow
      • View Escrow Account Information
    • Working with Chainlet
      • Launch your Chainlet on Testnet
      • Launch your Chainlet on Mainnet
      • Get Chainlet Information
      • View Listing of Chainlets Launched
      • Chainlet APIs & BlockExplorer
      • Configuring Metamask Network
      • Chainlet Billing
      • Restarting a Stopped Chainlet
  • Sagacli
    • Getting Access
    • Quickstart Guide
      • Testnet Quickstart Guide
      • Mainnet Quickstart Guide
    • Download Saga CLI
    • Install Saga CLI
    • Configure Saga CLI
    • Key Management
      • Adding Keys
      • Listing Keys
      • Display Key Details
      • Deleting Keys
      • Renaming Keys
    • Account Management
      • Checking Account Balances
      • Requesting Tokens from Saga Faucet
      • Deposit Funds into Escrow
      • Withdraw Funds from Escrow
      • View Escrow Account Information
    • Working with Chainlet
      • View Listing of Chainlet Types
      • Launch your Chainlet on Testnet
      • Launch your Chainlet on Mainnet
      • Get Chainlet Information
      • View Listing of Chainlets Launched
      • Chainlet APIs & BlockExplorer
      • Configuring Metamask Network
      • Update Chainlet Version
      • Chainlet Billing
      • Restarting a Stopped Chainlet
    • Configuring sagacli - A Deep Dive
    • Searching for Transactions
  • Get Help & Support
Powered by GitBook
On this page
  1. Introduction
  2. Saga Overview

Saga Shared Security

PreviousSaga ChainletsNextValidator Orchestration Tools

Last updated 1 year ago

One of the challenges of deploying a Cosmos-based application specific chain is the complexity around securing the chain. Each application chain requires gathering validators, distributing staking tokens and designing a token mechanism that helps secure the chain. Saga uses shared security to remove this barrier to entry. Every Saga Chainlet is secured by the Saga Mainnet validators using shared security.

There are many flavors of shared security. Saga uses a model similar to the Cosmos Hub’s version 1 interchain staking called Optimistic Coordination to ensure security of each of the Chainlets.

  • Every validator on the Saga Mainnet is required to validate every Chainlet provisioned

  • Validators agree on a set of SLA for Chainlet provisioning and maintenance such as timely deployments, guaranteed compute capacity, minimum uptime, honest consensus participation, and inter-blockchain communication relaying

  • An auditor monitors the Chainlet and creates a governance case in the event that a validator fails to meet service obligations

  • Saga Mainnet enforces any consequences needed for validators violating SLA

With Optimistic Coordination, Chainlets automatically inherit the security of the Saga Mainnet. However, to make provisioning Chainlets as simple as possible, Saga requires a suite of tools to facilitate Chainlet orchestration for validators.