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. Verification Mechanisms

External Verification

PreviousNative VerificationNextOptimistic Verification

Last updated 2 years ago

have not gained traction because of their aforementioned challenges, namely engineering complexity, low reusability, and high operational costs.

However, externally verified constructions have proliferated given the market need for interoperability. Unlike light client relays, externally verified systems are easy to develop, highly reusable, and quite cheap / easily subsidized.

Source:

Examples of externally verified systems include custodians, multi-sig addresses, validator / proof-of-stake (PoS) systems, and oracle networks. All fundamentally work the same way — they introduce an external verifier or set of verifiers who must collectively sign cross-chain messages beyond some threshold to be deemed valid on the destination chain.

Oftentimes, externally verified systems will use more complex language like MPC or TSS. Their meaning is simple:

  • MPC (Multi-party Computation) — there are multiple signers who are responsible for verifying cross-chain messages. Essentially a multi-sig wallet address.

  • TSS (Threshold Signature Scheme) — the multi-sig signers must reach some quorum or threshold to verify messages. Examples include Synapse (3-of-5) or Wormhole (13-of-19).

The drawback to external verification is that while it is expedient, it outsources security to third parties (ie. folks other than the validators of the two chains). If these validators' collective security is weaker than the underlying chains they bridge, then they become the weakest link in the system.

Natively verified systems
The Interoperability Trilemma