Glacis
  • Overview
  • Glacis Core
    • Why Glacis?
    • Getting Started
    • Concepts
      • Architecture
      • Components
      • Features
        • Abstraction
        • Access Control
        • Redundancy
        • Retry Management
        • Routing
        • xERC20s
      • Governance Model
      • Upgrade Model
      • Security Model
    • Messaging Fees
      • Protocol Fees
      • Gas Overhead
    • Troubleshooting
      • Integration Checklist
      • Error Messages
      • FAQ
    • References
      • Smart Contracts
        • GlacisRouter
        • GlacisClient
        • SimpleTokenMediator
      • Supported Chains
      • Supported GMPS
  • Airlift
    • Why Airlift?
    • Supported Chains & Tokens
  • Architecture Overview
    • On-Chain Interface
    • Off-Chain Interface
  • Operation Overview
  • Send & Execute
Powered by GitBook
On this page
  1. Glacis Core
  2. Concepts

Architecture

PreviousConceptsNextComponents

Last updated 1 year ago

Glacis is a pure on-chain protocol, that means that all its components are Smart Contracts, these components can be aggregated in two groups:

  • Infrastructure Components: Maintained by Glacis and deployed on each supported chain.

    • Router

    • Adapters

    • Mediators

  • Client Components: Maintained by Glacis,accessible as package and deployed by user through the use of inheritance on his own contracts.

    • Clients

All components have different behavior depending if they act as a source chain component or a destination chain component.

Component diagram

This diagram represents the complete flow between components in Glacis Architecture.