RabbitX is a decentralized perpetual futures & derivatives exchange built on StarkNet, a Layer‑2 zero‑knowledge rollup of Ethereum. It aims to offer high‑speed, gas‑efficient (often zero gas fees for trades), non‑custodial trading with leverage (up to about 20×) and deep liquidity. :contentReference[oaicite:0]{index=0}
The protocol uses a hybrid architecture: off‑chain order matching for rapid execution and on‑chain settlement for transparency. Users keep custody of their assets via connected wallets, not via centralized custodians. :contentReference[oaicite:1]{index=1}
Another component is the native utility/governance token **RBX**, which is used for staking, rewards, and governance of the RabbitX ecosystem. RBX has a fixed maximum supply, with a substantial portion allocated to community rewards and staking programs. :contentReference[oaicite:2]{index=2}
Here are frequent problems RabbitX users report, and how to approach resolving them.
- Confirm your wallet is supported and properly connected (e.g., MetaMask, WalletConnect).
- Ensure you are on the correct network (StarkNet) and have bridged funds if necessary.
- Clear browser cache, disable conflicting extensions.
- Try switching devices or browsers. Sometimes mobile vs desktop issues occur.
- Check if RabbitX is in “invitation‑only” or restricted access phase; early mainnet launch had invitation‑only access. :contentReference[oaicite:10]{index=10}
- Wallet‑RPC mismatch or unsupported RPC endpoint may cause verification or connection errors.
- Ensure your wallet software is up to date.
- Check if there is an ongoing outage or downtime via RabbitX’s official docs or support channels.
- Try reconnecting or reauthorizing the wallet.
- If using API, verify that your credentials (private key / onboarding) are correctly configured. :contentReference[oaicite:11]{index=11}
- Insufficient collateral or leverage constraints can lead to transaction rejections.
- Slippage or limit order settings too strict.
- Gas or fee issues may arise if deposit/withdrawal networks are congested.
- Oracle / price feed lags or errors may cause trades to fail or get liquidated unexpectedly.
- For large withdrawals, processing time may be longer; withdraws go through “pending” → “claimable” → “success” states. :contentReference[oaicite:12]{index=12}
- Ensure deposit confirmations are complete (e.g. block confirmations required). :contentReference[oaicite:13]{index=13}
- For large withdrawals, require more confirmations or larger block delays; check the required processing times.
- Verify that the “Transfers” tab is showing correct status (“pending”, “claimable”, etc.).
- If claim step is needed, you must execute the claim.
- If delays persist, contact RabbitX support (Discord / official channels).
- As of known public info, RabbitX is non‑custodial, so standard 2FA (like TOTP) is not core for wallet logins.
- If a UI layer or third‑party overlay adds extra authentication (2FA, email login), follow that provider’s recovery flow.
- Always secure your wallet private key / recovery phrase; losing that often means loss of access.
- Use verified domain and official links to avoid phishing attempts.
RabbitX aims to bring together speed, efficiency, transparency, and user control to decentralized derivatives trading. By using StarkNet’s zero‑knowledge rollups, off‑chain order matching, and on‑chain settlements, it delivers many of the benefits of centralized exchanges while maintaining DeFi’s promise of user custody and decentralization. However, practical usage may face friction: problems like login/connectivity issues, transaction declines, withdrawal delays, or mis‑configured wallets can disrupt experience. Users should carefully follow proper setup: correct network, bridges, confirmed deposits, wallet setup, and keep up with official documentation and status updates. Maintaining good security practices (wallet backups, verifying domain names, avoiding phishing) will reduce risk. With the right precautions, RabbitX has strong potential in the DeFi derivatives landscape.