How to use UniHexa for cross-chain exchange? (BRC-20 & Runes)

Understanding UniHexa’s Cross-Chain Architecture

1. UniHexa operates as a non-custodial cross-chain bridge specifically engineered to handle BRC-20 tokens and Runes assets originating from Bitcoin’s Layer 1.

2. It leverages a hybrid verification model combining SPV proofs and decentralized relayer networks to validate state transitions across heterogeneous chains.

3. The protocol does not rely on wrapped assets or synthetic representations—instead, it facilitates atomic swaps through coordinated timelock-enforced UTXO management.

4. Each transaction is anchored by a Merkle inclusion proof derived from Bitcoin block headers, ensuring cryptographic fidelity during asset migration.

5. UniHexa’s architecture isolates Bitcoin-native primitives such as ordinal inscriptions and rune allocations within discrete execution contexts to preserve semantic integrity.

Initiating a BRC-20 to EVM Chain Transfer

1. Users connect a Bitcoin-compatible wallet supporting BRC-20 inscription signing, such as Unisat or OKX Wallet, to the UniHexa dApp interface.

2. They select the target chain—Ethereum, Arbitrum, or Base—and specify the destination address compatible with that chain’s address format.

3. The interface displays real-time liquidity depth for the selected BRC-20 token pair and calculates slippage-adjusted output amounts using on-chain oracle feeds.

4. A two-phase commitment is triggered: first, a Bitcoin transaction locks the BRC-20 UTXO in a multisig script; second, an Ethereum-based deposit event is emitted upon confirmation of six Bitcoin blocks.

5. Final settlement occurs when the receiving chain mints equivalent ERC-20 tokens backed by on-chain attestations verified by UniHexa’s validator set.

Executing Runes Asset Migration

1. Runes assets are identified via their unique rune ID encoded in the OP_RETURN field of a Bitcoin transaction, and UniHexa parses this metadata directly from raw block data.

2. Users input the rune ID and desired quantity, then approve a Bitcoin transaction that commits the runes to a designated burn address monitored by UniHexa’s indexer.

3. Once confirmed, UniHexa’s coordinator triggers issuance of fungible tokens on the destination chain using a deterministic mapping derived from the rune’s genesis inscription.

4. The minted tokens retain the original rune’s name, symbol, and divisibility parameters, preserving composability with existing DeFi protocols.

5. All rune transfers enforce strict adherence to the Rune Protocol’s supply rules, including etching validation and satpoint verification before cross-chain propagation.

Security Considerations and On-Chain Verification

1. UniHexa validators run full Bitcoin and Ethereum nodes to independently verify transaction inclusion, eliminating reliance on centralized block explorers.

2. Each cross-chain event includes embedded cryptographic commitments signed by at least five independent validator keys, with threshold signature aggregation enforced on-chain.

3. Users can manually inspect the validity of any bridged asset by querying UniHexa’s public verification dashboard using the original Bitcoin transaction ID.

4. Reentrancy protections are embedded in the Ethereum-side minting contracts, preventing recursive calls during transfer finalization.

5. UniHexa’s relayer layer undergoes continuous audit cycles conducted by third-party firms specializing in Bitcoin-layer security analysis.

Frequently Asked Questions

Q: Does UniHexa support direct BRC-20 to Runes swaps?UniHexa does not perform native BRC-20 ↔ Runes swaps. It supports independent migration paths for each asset type to external chains but does not mediate conversions between them.

Q: Can I retrieve my assets if a cross-chain transaction stalls?Yes. If finalization fails beyond the configured timeout window, users may trigger a manual refund by submitting valid SPV proofs and validator-signed attestations via UniHexa’s recovery portal.

Q: Are Runes transferred via UniHexa subject to the same scarcity guarantees as on Bitcoin?Yes. UniHexa enforces immutable rune supply constraints by validating etching transactions against the canonical Bitcoin blockchain before allowing issuance on destination chains.

Q: Which wallets display Runes balances after migration to EVM chains?Wallets supporting custom ERC-20 token imports—such as MetaMask or Rabby—can display Runes-derived tokens once the contract address and ABI are manually added. UniHexa provides verified contract addresses for all migrated assets.