WALLET PRODUCT · BRIDGE

Move assets without hiding the trust boundary.

Bridge belongs in the Wallet experience because the user previews and signs here. Its contracts and relayer remain separate security entities.

PHASE 2 · NOT ACTIVE
No bridge transaction can be submitted yet.BridgeLock, BridgeMint, the idempotent relayer, and the locked-equals-minted reconciliation check must all exist before this control is enabled.

1 · User wallet

Previews and signs the source-chain transaction. The user key never leaves the browser wallet.

2 · BridgeLock

Escrows JYVE on the source deployment and emits a unique transfer ID.

3 · Relayer

Waits for confirmations and submits the destination leg with its own dedicated key.

4 · BridgeMint

Mints or burns the mirrored JYVE and rejects any transfer ID already processed.

5 · Reconciliation

Checks that source escrow and destination mirrored supply remain equal.

Why the Bridge is not part of Exchange

Exchange discovers a JYVE/USDC price and executes swaps. Bridge transports JYVE between deployments. They share the JYVE economic unit, but they have different user intent, failure modes, and privileged actors.

Open WalletOpen Exchange ↗

The first study bridge will distinguish Local and Sepolia by deployment and RPC, not by chain ID. A Sepolia fork can report the same chain ID as real Sepolia.