FAQ

No. XGR→Base locks native XGR and mints wXGR; Base→XGR burns wXGR and unlocks native XGR.

XGR Interchain validators use XGR validator BLS identities. The active destination registry defines the Interchain set and an unweighted two-thirds quorum authorizes attestations and membership transitions.

No. The bridge is a non-custodial interface. XGR.Network GmbH does not collect or store your private keys, seed phrase or wallet signing credentials and cannot sign transactions from your wallet on your behalf. You initiate and sign transactions with your own wallet. XGR and wXGR involved in a bridge transfer are locked, minted, burned or unlocked on-chain according to the deployed smart contracts and protocol rules. The relayer transports messages and proofs; it does not possess your wallet keys.

The relayer can delay or withhold delivery, but it cannot manufacture a valid XGR BLS quorum attestation.

There is no fixed time guarantee. Completion depends on source confirmations, the next validator-attested checkpoint, relayer submission and destination-chain confirmation.

The transfer continues on-chain. The bridge stores recent message IDs locally in your browser so status tracking can resume when you return.

Deployment and public availability are separate. Router gates, PausableISM where applicable, validator attestation health and relayer runtime are checked independently.

It is the synthetic XGR supply issued on an external chain such as Base. In the lock/mint model, it should be backed by native XGR locked on XGRChain.

Yes, if that route is configured. Membership is scoped to the XGR destination registry while each source route keeps its own checkpoint context and attestation stream.