> ## Documentation Index > Fetch the complete documentation index at: https://docs.pfbridge.xyz/llms.txt > Use this file to discover all available pages before exploring further. # Frequently asked questions about using ProofBridge > Answers to common questions about ProofBridge: supported wallets, transfer times, fees, stuck transfers, token support, privacy, and future chains. Find answers to the most common questions about using ProofBridge. If your question is not covered here, open an issue on [GitHub](https://github.com/Explore-Beyond-Innovations/ProofBridge) or check the community channels. Not yet. ProofBridge is currently deployed on **Ethereum Sepolia** and **Stellar Testnet** only. These are public testnets, so you can explore the full bridging experience without using real funds. Mainnet deployment is on the [roadmap](/reference/roadmap) and will follow a thorough security review process. No. ProofBridge has no accounts, sign-ups, or KYC requirements. You connect your wallet and interact with the smart contracts directly. Your wallet address is your identity on the protocol. ProofBridge supports any EVM-compatible wallet for Ethereum Sepolia interactions, including: * **MetaMask** — the most commonly tested wallet * **WalletConnect-compatible wallets** — any wallet that supports the WalletConnect protocol For Stellar Testnet interactions, ProofBridge supports common Stellar wallets including **Freighter**, **xBull**, and **Albedo**. Make sure your wallet is connected to the correct testnet network before creating orders or ads. Transfer time depends on two factors: block confirmation time on the source chain and relayer processing speed. In typical conditions on testnet: 1. You submit your order on the source chain and wait for it to be confirmed. 2. You notify the relayer via a callback, which triggers proof generation. 3. The relayer generates the ZK proof and submits it to both chains. 4. Both unlock transactions confirm on their respective chains. The ZK proof generation step takes the most time. On current testnets, expect end-to-end completion in the range of a few minutes, depending on network congestion. ProofBridge does not charge a fixed protocol fee. Instead, the Maker implicitly sets the exchange rate when creating a liquidity ad by specifying the source and destination token amounts. The difference between what the Bridger deposits and what the Maker provides represents the Maker's compensation for supplying liquidity. You will also pay standard gas fees on both the source and destination chains for your on-chain transactions. If your transfer does not complete, your funds remain safely locked in the smart contract. The relayer cannot move or access them — only a valid zero-knowledge proof submitted to the contract can release funds to the designated recipient. Common reasons a transfer may stall: * The relayer is temporarily offline or unresponsive * Proof generation encountered an error * Network congestion delayed one of the unlock transactions If your transfer is stuck, check the relayer status and open a support issue on [GitHub](https://github.com/Explore-Beyond-Innovations/ProofBridge) with your order hash and the source chain transaction ID. No. Only tokens on configured cross-chain routes are supported. Token routes are set by the contract administrator and must be established on both the source and destination chains before bridging is possible. Currently supported routes on testnet: | Route | Source | Destination | | ----------------- | ---------------------------------- | ---------------- | | ETH / WETH | Ethereum Sepolia | Stellar Testnet | | XLM / WXLM | Stellar Testnet | Ethereum Sepolia | | ProofBridge Token | Ethereum Sepolia ↔ Stellar Testnet | Both directions | Native tokens (ETH, XLM) are automatically wrapped to their equivalents (WETH on Sepolia, WXLM via a SEP-41-compatible contract) when deposited, and unwrapped when released. No. All on-chain data is public — deposit amounts, wallet addresses, order hashes, and MMR roots are visible on the block explorer for both chains. Zero-knowledge proofs in ProofBridge are used for **succinct cross-chain verification**: the destination chain confirms what happened on the source chain by checking a fixed-size proof, with no oracle or validator set in the trust path. See [Zero-knowledge proofs](/concepts/zero-knowledge-proofs) for the full treatment. As a Maker, you lock funds in AdManager when you accept an order. Your primary risks are: **Counterparty non-completion**: If the Bridger creates an order on the source chain but never triggers the relayer callback to initiate settlement, your locked liquidity stays reserved until the order expires or the situation is resolved. The Bridger's deposited funds are also locked in the meantime. **Relayer liveness**: In the current pre-authorization phase, the relayer coordinates settlement. If the relayer is offline, settlement may be delayed even after both parties have deposited. The BLS aggregation milestone removes this single-relayer dependency — see the [roadmap](/reference/roadmap). **Settlement guarantees**: Once a valid ZK proof is submitted and verified on-chain, funds are released to the correct recipients automatically — the contract enforces this unconditionally. A Maker who has locked funds against a valid order hash will receive the Bridger's deposited tokens as soon as the proof confirms. Slashing mechanisms and liquidity guarantees for cases of Maker misbehavior are planned for a future release. ProofBridge is designed for multi-chain extensibility. The roadmap includes: * **Currently**: Ethereum Sepolia (EVM) and Stellar Testnet (Soroban) * **Planned EVM**: Arbitrum, Base, Optimism, Polygon * **Planned non-EVM**: Starknet, Solana Adding a new chain requires deploying the four core contracts (`AdManager`, `OrderPortal`, `MerkleManager`, `Verifier`), configuring bidirectional chain links, and registering token routes. The protocol is chain-agnostic as long as the chain can verify UltraHonk proofs and execute the Poseidon2 hash function. See the [roadmap](/reference/roadmap) for timing and sequencing.