Glacis

What is Glacis?

Glacis is a middleware protocol that simplifies, secures, and standardizes cross-chain messaging and token transfers. It aggregates leading General Message Passing (GMP) protocols such as Axelar, Wormhole, and LayerZero to provide a unified framework for developers building interchain applications.

---

What is Airlift?

Airlift is a powerful extension of Glacis that provides a universal token registry and abstraction layer for multi-chain native token transfers available exclusively via LI.FI.

Traditionally, each burn-and-mint token standard—like OFT, NTT, ITS, CCT, WarpRoutes, and xERC20—requires custom configuration, integration, and testing. Although these standards may use uniform transport protocols under the hood, the parameters for sending, receiving, and securing assets are inconsistent, which imposes a high integration burden.

Airlift solves this by:

• Abstracting each bridge and token standard's special configurations into a single canonical interface

• Providing an API for retrieving token configuration metadata and quoting routes

• Automatically unlocking hundreds of new bridging routes for integrators like LI.FI and Jumper

For developers and integrators, this means:

• No need to manually configure or test each new token or bridge

• Seamless access to the latest standards and highly efficient cross-chain routes

• Instant integration into dApps, wallets, or protocols with no overhead

---

Benefits for LI.FI Users

Through Glacis and Airlift, LI.FI users get:

• Access to highly optimized cross-chain token routes without any additional setup

• Support for hundreds of tokens via multiple bridge standards like OFT, xERC20, etc.

• Unified messaging and token transfer logic under the hood

This integration enhances LI.FI’s position as a robust cross-chain liquidity and messaging aggregator—empowering developers to build truly chain-agnostic applications.

Integration Options

1. LI.FI Widget

If you're using the LI.FI Widget, no additional setup is needed. Glacis routes (via Airlift) are automatically included where available if no "allowBridges" parameter is used.

2. LI.FI SDK

If you're using the LI.FI SDK, make sure your routing request includes:

• The desired source and destination chains

• Tokens involved in the transfer

• Any additional routing preferences (e.g., max slippage, integrator name)

Glacis will be automatically considered as a bridging option where relevant token routes are available if no "allowBridges" parameter is used.

3. LI.FI API

For direct API usage, Glacis routes will appear in the /quote and /routes endpoints. To explicitly confirm a route is powered by Glacis:

• Check for "bridge": "glacis" or similar in the response

• Tokens supported via Airlift will typically be listed in the metadata

No Manual Setup Required

Glacis and Airlift are fully abstracted inside the LI.FI platform. Integrators don’t need to manage:

• GMP routing configuration

• Token registry integration

• Gas estimations or execution

References

• Glacis Smart Contracts
• Glacis Governance Model
• Glacis Security Model