Cross-Chain Interoperability
Specter is a sovereign blockchain, but data and value do not exist in isolation. Users need to move assets between Specter and other chains — both within the Cosmos ecosystem and across to Ethereum, L2 rollups, and other EVM-compatible networks. Specter supports two bridge mechanisms, each suited to a different connectivity domain.
Bridge Architecture Overview
IBC (Inter-Blockchain Communication)
Overview
IBC is the native cross-chain communication protocol of the Cosmos ecosystem. Specter inherits full IBC support through the Cosmos SDK v0.53.2 application framework and ibc-go v10.
IBC provides trustless cross-chain communication — it does not rely on multisigs, validators, or trusted relayers for security. Instead, it uses light client verification: each chain maintains a light client of the counterparty chain, and cross-chain messages are verified against the counterparty's consensus state. If the counterparty chain has honest consensus, the bridge is secure.
How IBC Works
IBC Capabilities on Specter
| Capability | Status | Description |
|---|---|---|
| ICS-20 token transfers | Supported | Standard fungible token transfers between IBC-connected chains |
| IBC channels | Supported | Bidirectional communication channels with any ibc-go compatible chain |
| Light client verification | Supported | Trustless verification via CometBFT light clients |
| Timeout and refund | Supported | Automatic refund if destination chain does not acknowledge within timeout |
Trust Model
IBC's trust model is fundamentally different from bridge multisigs:
| Property | IBC | Typical Bridge Multisig |
|---|---|---|
| Trust assumption | Counterparty chain has honest consensus (>2/3 validators) | M-of-N bridge signers are honest |
| Verification | On-chain light client proof verification | Off-chain signature aggregation |
| Failure mode | Byzantine counterparty consensus (extremely unlikely) | Key compromise of M signers (historically common) |
| Liveness | Depends on relayers submitting packets (permissionless role) | Depends on bridge operators |
Future: Private Cross-Chain Transfers
The long-term vision for IBC on Specter is private cross-chain transfers — data is vanished on the source chain and summoned on the destination chain, with the IBC packet carrying only a commitment and proof rather than plaintext asset information.
This is a Phase 4 roadmap item. The protocol infrastructure (IBC channels, light clients, packet relay) is already operational; the privacy layer (commitment encoding in IBC packets, cross-chain Merkle proof verification) is under research.
Hyperlane
Overview
Hyperlane is a modular interoperability protocol that connects Specter to non-Cosmos chains — Ethereum mainnet, L2 rollups (Arbitrum, Optimism, Base), and other EVM-compatible networks. Unlike IBC, which relies on light client consensus verification, Hyperlane uses a pluggable security model based on Interchain Security Modules (ISMs).
Contract Architecture
Specter deploys a set of Hyperlane-specific contracts for bridging:
HypGhostERC20Collateral
Deployed on the remote chain (e.g., Ethereum). When a user bridges tokens to Specter:
- The user deposits tokens (USDC, WETH, LABS, etc.) into the collateral contract.
- Tokens are locked in the contract.
- A cross-chain message is dispatched via the Hyperlane Mailbox.
When tokens are bridged back:
- A cross-chain message arrives from Specter.
- The collateral contract unlocks and returns the original tokens to the user.
HypGhostERC20Synthetic
Deployed on Specter. When a cross-chain message arrives from a remote chain:
- The ISM verifies the message authenticity.
- The synthetic contract mints Ghost-wrapped tokens (e.g., gUSDC, gWETH, gLABS) to the recipient.
When tokens are bridged out:
- The synthetic contract burns the Ghost-wrapped tokens.
- A cross-chain message is dispatched to the remote chain to unlock collateral.
HyperlaneTokenRegistry
A registry contract that maps warp routes — the correspondence between a token on one chain and its synthetic representation on another. This enables the bridge contracts to resolve which synthetic token to mint for a given collateral deposit, and vice versa.
Interchain Security Modules (ISMs)
Hyperlane's pluggable security model allows Specter to choose the verification mechanism for cross-chain messages:
| ISM Type | Description | Trust Assumption |
|---|---|---|
| TrustedRelayerISM | A single designated relayer attests to message validity | Trust in one relayer entity |
| MultisigISM | M-of-N validators must sign to attest message validity | Trust in M of N validators being honest |
The current deployment uses TrustedRelayerISM for testnet simplicity. The production configuration will migrate to MultisigISM with a geographically and organizationally diverse validator set.
Bridge Tokens
The following Ghost-wrapped synthetic tokens are currently supported:
| Synthetic Token | Underlying Asset | Source Chain | Collateral Type |
|---|---|---|---|
| gUSDC | USDC | Ethereum / L2s | ERC-20 |
| gWETH | WETH | Ethereum / L2s | ERC-20 |
| gLABS | LABS | Ethereum / L2s | ERC-20 |
Ghost-wrapped tokens (prefixed with g) are standard ERC-20 tokens on Specter. They can be:
- Held and transferred like any token.
- Vanished into the Ghost Protocol for private storage or transfer.
- Summoned back from the Ghost Protocol to any address.
- Bridged back to the original chain by burning the synthetic and unlocking collateral.
Integration with Ghost Protocol
The bridge and the privacy protocol compose naturally:
A user can bridge USDC from Ethereum, receive gUSDC on Specter, vanish it into the Ghost Protocol, summon it to a fresh address, and bridge it back to Ethereum — achieving full transaction graph breakage across chains.
Comparison of Bridge Mechanisms
| Property | IBC | Hyperlane |
|---|---|---|
| Target chains | Cosmos ecosystem | EVM chains (Ethereum, L2s) |
| Trust model | Light client verification (trustless) | ISM-dependent (trusted relayer or multisig) |
| Latency | ~10-30 seconds (finality-dependent) | ~2-15 minutes (depending on source chain finality) |
| Token model | ICS-20 vouchers | Collateral lock / synthetic mint |
| Maturity | Production (years of mainnet operation) | Production (deployed across multiple chains) |
| Privacy integration | Future (Phase 4) | Future (Phase 4) |
| Native to Specter | Yes (Cosmos SDK built-in) | Via deployed Solidity contracts |