Lombard
  • Unlocking Bitcoin's Potential
    • Introducing Lombard & LBTC
      • Our Value Proposition
      • The State of Bitcoin
      • Lombard's Mission & Vision
  • Lombard's Partners
    • Babylon's Bitcoin Staking
    • Lombard's Security Consortium
  • Bitcoin Staking Partners
  • LBTC: Liquid Bitcoin
    • Introduction to LBTC
    • DeFi Vaults
      • Lombard DeFi Vault
        • LBTC/LBTCv
      • Bitcoin Bera Vault
      • Sentora DeFi Vault
    • Lux & Luminary Program
      • Referral Program
      • Nov. '24 The Golden Bull
      • Dec. '24 Flash Event
    • Staking Yield Distribution
    • Supported Blockchains
    • User Guides
      • Staking BTC & Minting LBTC
      • Unstaking LBTC
      • Lombard DeFi Vault: Depositing & Withdrawing
      • Claiming BABY
      • LBTC Bridging to Sui
  • Technical Documentation
    • Smart Contracts
    • Protocol Fees
    • Protocol Architecture
      • Lombard Ledger (Consortium)
      • CubeSigner: Key Management
      • Bascule Drawbridge
      • LBTC Design
      • Babylon Staking
      • PMM Module
      • Trustless Relayer
    • Oracles
    • Audits & Bug Bounties
    • Sanctions & Risk Monitoring
    • Transaction Tracing
  • Frequently Asked Questions
    • FAQs
      • BABY FAQs
  • Developers
    • Lombard SDK V3
    • SDK FAQ
    • Lombard SDK V2 (deprecated)
  • Quick Links
    • Lombard Website
    • Lombard X (Twitter)
    • Lombard Dune Dashboard
    • Lombard Dune PoR
    • Lombard Discord Server
  • Legals
    • Terms of Service
    • Privacy Policy
    • UK Residents
Powered by GitBook
On this page
  1. Technical Documentation
  2. Protocol Architecture

Trustless Relayer

Lombard operates several non-critical APIs and services to aid in communication between blockchain networks and enhance the user experience.

These APIs have limited elevated privileges (Operator and Claimer roles, see LBTC Design), as well as permission to submit transactions on the Lombard Ledger.

  1. Monitor the Bitcoin network, and report any suspected Lombard Protocol related deposits to Lombard Ledger.

  2. Monitor Supported Blockchains and report any CCIP bridge events to Lombard Ledger.

  3. Monitor Lombard Ledger, and automatically mint LBTC for depositors, after authorization from Security Consortium.

    1. Note: After Consortium authorization, a user can always mint their own LBTC, e.g. in the instance when auto-mint is disabled due to a period with high transaction costs.

  4. Record all Lombard Protocol related Bitcoin deposit addresses on an on-chain registry (on Base), used for Proof-of-Reserve attestation validation.

  5. Request on Lombard Ledger to (un)stake into Babylon. This is temporary, until automation on Lombard Ledger in a future upgrade.

  6. Monitor the performance of Lombard Ledger and the LBTC ecosystem.

PreviousPMM ModuleNextOracles

Last updated 3 months ago