Nomad Docs
  • Nomad 101
    • Funds Recovery
    • Introduction
    • Our Mission
    • Getting Started
  • The Nomad Protocol
    • Overview
    • Cross-chain Messaging
      • Lifecycle of a Message
    • Verification Mechanisms
      • Background on Verification
      • Native Verification
      • External Verification
      • Optimistic Verification
      • Comparing Mechanisms
    • Security
      • Root of Trust
        • Fraud
          • Optimistic Timeout Period
          • Fraud Recovery
        • App-Governed Root of Trust
        • Liveness Assumptions
      • Attack Vectors
        • Key Compromise
        • Economic Attacks
        • Smart Contract Bugs
      • Long-Term Security
        • Permissionless Watchers
        • Financial Controls
        • Cross-Domain MEV
    • Smart Contracts
      • Home
      • Replica
      • XAppConnectionManager
    • Off-chain Agents
      • Updater
      • Watchers
      • Relayer
      • Processor
  • Token Bridge
    • Overview
    • How to Bridge
      • Using Etherscan
      • Nomad Bridge App
      • Testnet Bridge App
    • Asset Issuers
      • Custom Representations
    • Deployed Tokens
      • Mainnet
      • Testnet
    • Smart Contracts
      • BridgeRouter
      • TokenRegistry
      • BridgeToken
      • BridgeMessage
    • Architecture
    • FAQ
  • Governance Bridge
    • Overview
    • Zodiac: Nomad Module
    • Smart Contracts
      • NomadModule
    • Architecture
  • Developers
    • Quickstart
      • Send Messages
      • Receive Messages
    • Environments
      • Domain (Chain) IDs
    • Application Developers
      • Building xApps
      • SDK
        • Contracts SDK
        • Typescript SDK
      • Examples
        • Ping Pong
        • Example Bridge GUI
        • xApp Example
      • Advanced
        • Router Pattern
    • Node Operators
      • Running Agents Guide
        • Troubleshooting
      • Running a Watcher
      • Agent Operations
      • Agent Gas Values
      • The Keymaster
    • Core Developers
      • Upgrade Setup
      • Deploying Contracts
        • Development
        • Production
  • Operational Security
    • Audits
    • Bug Bounty
    • Governance
    • Contracts
    • Agent Operations
  • Resources
    • Awesome Interoperability
    • Brand Kit
    • FAQ
    • Glossary
    • GitHub
    • Discord
    • Twitter
    • Website
Powered by GitBook
On this page
  1. The Nomad Protocol
  2. Security

Root of Trust

PreviousSecurityNextFraud

Last updated 2 years ago

The root of trust is the lynchpin of an interoperability protocol's security. As the name suggests, it lies at the heart of the system — any trust assumptions are only as strong as the root of trust itself.

Nomad's mechanism is its root of trust. The mechanism ensures that state is not corrupted, and must be bulletproof for any application building on top of Nomad.

There are two primary components when it comes to Nomad's root of trust security:

  1. — Nomad enables Watchers to monitor the system and flag fraud if they detect anything abnormal. Nomad requires only one honest Watcher to maintain liveness to protect the system. This ensures that malicious Updaters are not able to confirm corrupt messages within Nomad.

  2. — Unlike other cross-chain messaging systems that offer monolithic security for all applications, Nomad enables application governance to decide which Watchers they permit to flag fraud and notify their application on-chain.

This section and its associated pages will break down the various components of Nomad's root of trust including:

  • How fraud is prevented with the optimistic mechanism

  • Why application governed root of trust returns consent to users

  • Inherent liveness and economic security assumptions of optimistic verification

optimistic verification
Fraud Detection
App-Governed Root of Trust