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?
  • Architecture Overview
  • Operation Overview
  • Send & Execute
Powered by GitBook
On this page
  1. Glacis Core
  2. Troubleshooting

FAQ

Does my application contract have to inherit from a specific contract to work with Glacis?

Although Glacis provides client contracts to facilitate the interactions with the router, they only requirement for a contract to use Glacis is to implement the GlacisClient interface.

Can I send tokens with Glacis?

Glacis supports passing cross-chain tokens of the XERC20 standard via the SimpleTokenMediator. If you would like to send preexisting tokens, check out the Airlift product.

PreviousError MessagesNextReferences

Last updated 20 days ago