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. Troubleshooting

Integration Checklist

PreviousTroubleshootingNextError Messages

Last updated 10 months ago

The checklist below is intended to help prepare a project that integrates Glacis.

  • Extend your contracts with the latest version of Glacis Labs .

  • Deploy your contracts specifying Glacis Router or Glacis Token Mediator addresses as constructor parameters depending if you want to pass only cross-chain messages or cross-chain tokens along with messages. Addresses for Glacis infrastructure contracts can be obtained in

  • If your project requires token transfers with execution you can deploy your token using XERC20 standard and simply add Glacis XERC20 Extension to it. Otherwise, it is unnecessary to integrate this additional standard.

    • In case that you have a legacy ERC20 you can deploy an XERC20LockBox and migrate your legacy ERC20 tokens to your recently deployed XERC20.

Feel free to reach out to the team on !

client
Supported Chains
Telegram