Bridging and Cross-Chain Messaging

Last reviewed: 2026-08-01

Lithosphere status

MultX Bridge, Swap, Faucet, and related restricted features remain disabled on Lithosphere. No cross-chain representation of native LITHO or LEP100 assets is approved for exchange listing in the current release package.

Do not direct users to a Kamet or Makalu bridge as a Lithosphere bridge. Do not describe testnet wrapped assets as interchangeable with native Lithosphere assets.

MultX testnet documentation

MultX integration code and testnet documentation exist for the Kamet/Makalu ecosystem, including a bridge integration guide, the MultX protocol API reference, and the @litho/multx-sdk package. These resources do not constitute a production Lithosphere bridge launch.

Production publication gates

Before publishing a Mainnet bridging tutorial, all of the following must be approved and evidenced:

• external security audit and remediation status;
• exact source and destination chain IDs;
• canonical bridge and wrapped-token contract registries;
• validator or attestation security model;
• ownership, multisig, timelock, guardian, and pause controls;
• supported routes, fees, limits, and finality policy;
• incident, pause, recovery, and upgrade procedures;
• official user interface and API endpoints; and
• clear warning against unsupported routes and contract addresses.

Cross-chain messaging

No general-purpose Lithosphere cross-chain messaging service is approved for public developer use in the current package. A future page must distinguish asset bridging from arbitrary-message delivery and document the precise trust and verification model.