# Bridge

***

### Bridge-agnostic by design

Because **xSPACE uses xERC20 (ERC-7281)**, adding or replacing a bridge is an **integration choice**, not a token redesign: you can authorize a new bridge module and enforce **per-bridge mint/burn limits**, then revoke access if that route becomes unsafe or unmaintained. ([The Block](https://www.theblock.co/post/328907/interoperability-may-be-turning-a-corner-with-hyperlane-co-founder-jon-kol?utm_source=chatgpt.com))

This is what enables future optional integrations (e.g., alternative messaging/bridge stacks) without creating new “wrapped SPACE” variants.

***

### What is Hyperlane

**Hyperlane** is a **permissionless interoperability framework**: it lets developers connect chains and build cross-chain applications without requiring approvals from a central operator. ([Hyperlane](https://www.hyperlane.xyz/post/permissionless-interoperability?utm_source=chatgpt.com))

At a high level, Hyperlane provides:

* **Cross-chain messaging** (send data/messages across chains)
* **Token bridging** via **Warp Routes** (modular bridges deployed per route) ([Hyperlane Docs](https://docs.hyperlane.xyz/docs/protocol/warp-routes/warp-routes-overview?utm_source=chatgpt.com))
* A **modular security model** where each route/app can choose its own verification setup through **Interchain Security Modules (ISMs)** 

Hyperlane is developed by **Abacus Works** and was founded by **Asa Oines**, **Nam Chu Hoai**, and **Jon Kol**.

***

### Why we use Hyperlane for xSPACE

Hyperlane fits xSPACE well because it is:

* **Modular**: Warp Routes are deployed per token/route, not as one monolithic bridge shared by everything.
* **Customizable in security**: routes can be configured with an ISM appropriate to the use case/risk appetite.
* **Designed for broad environments**: Hyperlane is intended to work across L1s, rollups, and appchains.
* **xERC20-compatible**: Hyperlane documents dedicated xERC20 route types (e.g., HypXERC20 / HypXERC20Lockbox) for issuer-controlled bridged tokens.

***

### Typical Hyperlane use cases

Hyperlane is commonly used for:

* **Token mobility** (ERC-20/NFT/native token transfers) via Warp Routes 
* **Interchain applications** that need cross-chain actions (e.g., execute on chain B after an action on chain A) 
* **Cross-chain governance and coordination**, where messages coordinate state changes across deployments (route/app-specific security is a key part of this) 

***

### What is supported for SPACE/xSPACE

* **Supported bridge layer:** Hyperlane (current) 
* **Connext routing:** deprecated