Architecture
The Unified Transfer Protocol
Stargate is engineered as the definitive omnichain asset transfer protocol, the end game for bridging. It leverages appropriate underlying Messaging Protocols like LayerZero or Circle’s CCTP to execute the cross-chain token transfers.
Consider an analogy to traditional finance. SWIFT standardizes messaging for international fiat transfers between diverse banks, enabling communication despite different internal systems and regulations. Similarly, Stargate provides a unified protocol layer that orchestrates transfers across disparate blockchains and asset standards, managing the underlying variations.
By managing route selection and utilizing varied execution strategies, Stargate abstracts the inherent complexity of cross-chain assets transfers.
| Layer | Description |
|---|---|
| Routes Layer | Defines the distinct pathways (e.g., Stargate V1/V2, OFT, CCTP) employed to execute asset transfers, selected based on the asset type. |
| Messaging Layer | Utilizes secure messaging protocols (e.g., LayerZero, CCTP) to facilitate reliable cross-chain communication required for various routes. |
| Asset Standards Layer | Ensures compatibility by supporting diverse token standards (e.g., ERC20, OFT, Gas Tokens), enabling broad asset coverage. |
The set of available networks for each asset is defined by its configured mesh. Consequently, when initiating a transfer, Stargate presents the set of compatible pathways and destinations valid for that asset’s specific mesh.
Stargate abstracts routing complexity for cross-chain token transfers by providing seamless, efficient routes for consistent and reliable asset movement.
Stargate Routes
Routes Layer comprises the distinct implementations (strategies) for executing cross-chain asset transfers. Each Route leverages specific messaging protocols and is selected based on the asset type.
Stargate continuously integrates new Routes to maximize asset and network support and aims to create a standardized integration framework, allowing seamless interaction with diverse transfer mechanisms through the unified Stargate protocol and API.
| Route | Description | Messaging Protocol |
|---|---|---|
| Stargate V1 | Unified Liquidity Pools & Delta (Δ) Algorithm | LayerZero |
| Stargate V2 | Locks native assets in core pools to mint OFT representations on Hydra-enabled chains | LayerZero |
| OFT Route | Direct Interaction with OFT Contract Logic (Burn/Mint or Lock/Release) | LayerZero |
| CCTP Route | Circle’s Dedicated Burn/Mint Infrastructure | Circle CCTP |
The integration and activation of entirely new route types represent significant protocol evolution and thus require formal approval from the Stargate DAO.
Messaging Layer
The Messaging Layers are Stargate’s fundamental communication infrastructure, acting as the backbone for cross-chain asset transfers. They securely transmit and verify instructions between chains, ensuring source actions trigger corresponding destination actions.
Continuing our analogy to SWIFT for fiat transfers, just as TCP/IP protocols provide the essential foundation for secure information exchange, Stargate’s Messaging Protocols provide the underlying secure transport necessary for its routes to operate.
Stargate utilizes different messaging protocols depending on the specific route being executed.
| Messaging Protocol | Description |
|---|---|
| LayerZero | Provides the core messaging backbone for Stargate’s native V1/V2 routes and the OFT route, enabling instant guaranteed finality and OFT logic execution. |
| Circle CCTP | Serves as the dedicated messaging and attestation protocol specifically utilized by the CCTP route for native USDC transfers. |
Similarly to routes, adding support for entirely new underlying Messaging Protocols is a major protocol change that requires formal approval through Stargate DAO governance.
Asset Standards
The Asset Standards Layer within Stargate’s architecture represents the protocol’s capability to natively understand and interact with various ways fungible tokens are represented on blockchains. Supporting multiple standards ensures broad compatibility for both existing and new tokens.
Crucially, a token’s specific standard dictates which Stargate routes are available for its transfer, allowing the protocol to handle a wide range of assets seamlessly.
| Asset Standard | Description |
|---|---|
| Fungible Tokens | The standard interface for fungible tokens on EVM or Non-EVM chains. Stargate supports transfers via native pools (V1/V2 routes) or specific OFT Adapter routes if applicable. |
| OFT (Omnichain Fungible Token) | A LayerZero-based standard for tokens with native cross-chain logic (direct or via Adapters). Stargate utilizes the OFT route to interact directly with these. |
| Gas Tokens | Native network assets (e.g., ETH, AVAX). Stargate handles their cross-chain transfer via specialized OFT Gas Adapters, integrating them into the OFT or Pool route framework. |
Adding tokens varies by standard. OFTs can often be user-added, but other types require Foundation post-acceptance (distinct from DAO approval for core protocol changes).