How the QIE Bridge works

Overview

QIE Bridge is a native cross-chain bridge between QIE Chain (an EVM-compatible chain with id 1990) and Osmosis. There are no intermediary contracts, no multisig of human signers, and no custodian holding your assets. Both chains verify transfers independently and cryptographically.

When you send QIE to Osmosis, your assets are held by the protocol on QIE Chain while an equivalent balance becomes available on Osmosis. When you send back, the Osmosis balance is settled and your native QIE is released on QIE Chain. The amount you receive always equals the amount you sent.

How a transfer works

1. You approve a single transaction

On QIE → Osmosis with MetaMask, a single EVM transaction approval in your wallet kicks off the entire transfer. No extra steps, no typed-data signing — just one click.

On Osmosis → QIE (or QIE → Osmosis with Keplr/Leap), one Cosmos transaction approval from your wallet is all it takes.

2. The transfer is broadcast on-chain

Once your transaction lands in a block, it's permanently recorded on the source chain. A 10-minute timeout window is set — generous enough to handle any normal network delays. If the transfer can't complete in time, your assets are automatically returned.

3. The relayer routes it across chains

Our relayer network watches both chains continuously. As soon as your transaction is confirmed, the relayer picks it up and routes it to the destination chain — along with a cryptographic proof that the source transaction actually happened.

Relaying is permissionless and redundant — we run a primary relayer with backup operators, so there's no single point of failure.

4. The destination chain releases your assets

The destination chain independently verifies the proof from the source chain. If everything checks out, your QIE becomes available in your destination wallet — no manual claim, no extra steps.

Total time: typically 30–60 seconds end to end.

EVM addresses on the destination

QIE Chain supports both EVM and Cosmos address formats — they point to the exact same account. MetaMask shows your address as 0x… and Keplr shows it as qie1…, but both are controlled by the same private key.

Our bridge UI accepts either format in the destination field when sending to QIE. Pasting a 0x… address triggers an instant local conversion and shows you the equivalent qie1… address before you confirm. No backend round-trip, no extra steps.

Security model

QIE Bridge is designed with a trust-minimized architecture — no privileged admin keys, no upgrade mechanisms that could be exploited, and no human signers in the transfer path. Security comes from three independent layers:

Layer 1 — Independent consensus on both chains

Both QIE Chain and Osmosis operate with their own independent validator sets. Compromising a transfer would require simultaneously controlling a supermajority of validators on both networks — an economic and logistical barrier orders of magnitude beyond any realistic attack.

Layer 2 — Cryptographic proof verification

Every transfer carries a cryptographic proof that the source transaction actually occurred. The destination chain verifies this proof independently against the source chain's committed state. No valid proof, no transfer — it's that simple.

Layer 3 — Fixed channel binding

The channel connecting QIE and Osmosis was established with a verified 4-way handshake that locked in the exact counterparty on both sides. You can't trick either chain into accepting transfers from an impersonator.

Balance display on Osmosis

QIE uses 18 decimal places, which is more than most Cosmos tokens. When your QIE arrives on Osmosis, some UIs may display the balance as a very large number because they assume 6 decimal places when rendering unfamiliar assets.

This is a display quirk only — your assets are safe and the amount is correct. When you bridge back to QIE, you receive exactly what you sent. If you need to interact with your QIE balance on Osmosis, use a tool that lets you specify the decimal precision manually.

Troubleshooting

"Transfer is taking longer than expected"

Don't resubmit yet. This appears if the transfer hasn't confirmed within 5 minutes. Common causes:

• The relayer is catching up after a restart — usually resolves within 15 minutes.
• Network congestion on Osmosis — can happen during high-activity periods.
• The 10-minute timeout was reached — your assets will be automatically returned, no action needed.

Check the QIE Explorer with your transaction hash. If a transfer event was emitted, the transfer is in progress and will arrive shortly.

"MetaMask is on the wrong network"

Click "Switch to QIE" in the bridge UI — this triggers MetaMask's network-switch flow and adds QIE automatically if needed. If your wallet rejects the auto-add, you can configure it manually:

• Chain ID: 1990 (0x7C6)
• RPC: https://evm-rpc.qie.digital
• Symbol: QIE, decimals 18
• Explorer: https://mainnet.qie.digital

"Receipt unconfirmed — RPC was slow"

Your transaction was broadcast successfully, but our connection timed out before confirming it landed in a block. It almost certainly did — check the QIE Explorer before doing anything else. Do not resubmit without confirming the first transaction didn't complete — you risk sending twice.