HIP-102: Omnichain Bridge Integration. Status Draft. Hanzo's own standard — read this before implementing against it.
This proposal specifies how Hanzo AI integrates with the Lux Teleport omnichain bridge to enable cross-chain AI inference payments and model deployment across 270 supported chains. HIP-0101 defines the bilateral Hanzo-Lux bridge. This proposal extends that foundation to arbitrary destination chains by leveraging Lux Teleport as the routing layer.
The protocol defines three capabilities: omnichain inference payments (pay for AI compute from any chain), cross-chain model deployment (deploy trained models to execution environments on remote chains), and yield-bearing bridge tokens (compute deposits that earn yield while awaiting inference). MPC threshold signatures secure all cross-chain operations: FROST for Ed25519 chains and CGGMP21 for ECDSA chains.
The omnichain bridge extends HIP-0101 by adding Lux Teleport as a routing layer between Hanzo and external chains.
External Chain (1 of 270) Lux Teleport Hanzo-Lux Bridge Hanzo L1 (36963)
┌───────────────────┐ ┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ │ Lock │ │ │ │ │ │
│ Source Vault │──────>│ Teleport Router │──>│ HIP-0101 Bridge │──>│ Inference Engine │
│ (chain-native) │ │ (MPC relay) │ │ (lock-and-mint) │ │ (GPU validators) │
│ │<──────│ │<──│ │<──│ │
│ │ Unlock│ │ │ │ │ │
└───────────────────┘ └──────────────────┘ └──────────────────┘ └──────────────────┘
│
┌─────────┴─────────┐
│ MPC Signers │
│ FROST (Ed25519) │
│ CGGMP21 (ECDSA) │
└───────────────────┘
User External Chain Lux Teleport HIP-0101 Bridge Hanzo L1
│ │ │ │ │
│── pay(USDC, 100) ─────>│ │ │ │
│ │── Lock event ─>│ │ │
│ │ │── route ──────>│ │
│ │ │ │── mint wAI ───>│
│ │ │ │ │── queue inference
│<─── inference result ──│ │ │ │
│ │ │ │ │
│ Latency: 15-30s (source finality + Teleport routing + HIP-0101 bridge) │
Lux Teleport secures cross-chain messages using MPC threshold signatures. The signing scheme adapts to the destination chain's native cryptography.
For chains using Ed25519 (Solana, Near, Aptos, Sui, and others), the bridge uses FROST (Flexible Round-Optimized Schnorr Threshold signatures) as specified in RFC 9591.
without any single party learning the full signing key
commitment. Round 2: each signer produces a signature share using the aggregated nonce. The coordinator aggregates shares into a valid Ed25519 signature.
special precompile required.
For chains using ECDSA (Ethereum, BSC, Polygon, Arbitrum, Optimism, and others), the bridge uses CGGMP21 (Canetti-Gennaro-Goldfeder-Makriyannis-Peled 2021) threshold ECDSA.
Online signing requires one round using a presignature triple and the message hash. This achieves sub-second signing latency.
ecrecover on the destination chain.The MPC signer set consists of validators drawn from both Hanzo and Lux networks. Each signer runs a threshold signing daemon alongside their validator node. Signer rotation follows the same schedule as HIP-0101 validator rotation: epochs of 24 hours with a 1-hour overlap period for key resharing.
Lux Teleport maintains relay infrastructure across 270 chains organized by signature scheme:
| Scheme | Chain Count | Examples | |--------|-------------|----------| | ECDSA (secp256k1) | 180+ | Ethereum, BSC, Polygon, Arbitrum, Optimism, Base, all EVM L2s | | Ed25519 | 40+ | Solana, Near, Aptos, Sui, Cosmos chains | | Sr25519 | 20+ | Polkadot, Kusama, Substrate chains | | Other | 30+ | Bitcoin (Schnorr), Tron, Ripple, Stellar |
For chains using Sr25519 or non-standard schemes, the bridge uses chain-specific MPC protocols derived from the FROST framework with curve adaptation.
Users who bridge assets for AI compute may not consume inference immediately. Idle deposits represent capital inefficiency. Yield-bearing bridge tokens solve this by routing deposited assets into Lux DeFi pools while maintaining instant redeemability.
(lending pool or liquidity provision).
token.
(principal + accrued yield) to pay for compute.
USDC plus earned yield, routed back through Teleport to the source chain.
| Token | Underlying | Yield Source | APY Range | |-------|-----------|--------------|-----------| | ybUSDC | USDC | Lux lending pool | 3-8% | | ybUSDT | USDT | Lux lending pool | 3-8% | | ybAI | $AI | AI compute staking (HIP-0096) | 5-15% | | ybLUX | LUX | Lux network staking | 4-10% |
The inference payment protocol coordinates payment on a source chain with execution on Hanzo and settlement on Lux.
struct OmnichainInferenceRequest {
uint256 nonce; // Unique request ID
uint32 sourceChainId; // Origin chain (any of 270)
address payer; // Payer address on source chain
bytes model; // Model identifier (IPFS CID or Hanzo model ID)
bytes input; // Inference input (encrypted with model's TEE key)
uint256 maxFee; // Maximum fee in source chain's native unit
address feeToken; // Payment token on source chain
uint64 deadline; // Request expiration (source chain block timestamp)
bytes callback; // Optional: callback address + function selector
}
(HIP-0008) liquidity pools.
maxFee, the remainder routes back to thesource chain through Teleport. If a callback is specified, the inference result is relayed to the callback address on the source chain.
Trained models on Hanzo can be deployed to execution environments on remote chains where inference demand exists. The bridge carries model certificate NFTs (ERC-721) and deployment manifests.
execution environment.
model weights from the decentralized storage layer (referenced in the certificate metadata), and initializes the inference endpoint.
model owner on Hanzo.
in plaintext.
compromised shares.
(post-quantum).
USDC/USDT, $50M/day for $AI.
bridge pauses for that chain pending governance review.
Copyright and related rights waived via CC0.