Redbelly DAO · Community Support Guide
Unstick Your RBNT
A Cross Chain Recovery Playbook
A community support guide for wrong network sends, stuck bridges, and thin liquidity swaps. Reflects live, independently verified data as of August 2026.
Liquidity, fees, and routing conditions change frequently. Confirm current quotes before acting on amounts that matter to you.
Full document, rendered inline
SECTION 01
Before You Bridge
Never send RBNT to a centralized exchange deposit address on the wrong network. A deposit address is only valid for the exact asset and network the exchange lists it for. Sending native RBNT to an address expecting a wrapped version, or sending on a chain the exchange does not credit, puts the funds outside normal crediting and into a manual recovery process that may fail.
Where RBNT trades
RBNT trades on four exchanges: Gate, MEXC, WhiteBIT, and BYDFi. Recovery processes are not equivalent between them, so the exchange you used determines your realistic options.
- Gate
- Self service recovery form available. You submit the request yourself without waiting for a support agent.
- MEXC
- Self service recovery form available. MEXC charges a processing fee for wrong deposit returns.
- BYDFi
- No self service form. Recovery is handled through support, and you must supply the transaction hash and your account ID.
- WhiteBIT
- Weakest documented process of the four. No dedicated recovery form, and WhiteBIT states that deposits made incorrectly may be irreversibly lost.
Correct deposit procedure
- Open the deposit page on the exchange and select RBNT explicitly. Do not reuse an address saved from a previous deposit of a different asset.
- Select the exact network the exchange lists for RBNT. If the network you hold funds on is not offered, stop, the exchange cannot credit it.
- Copy the freshly generated deposit address and any required memo or tag directly from that page, then paste it into your wallet without editing.
- Send a small test amount first, confirm it credits, and only then send the full balance.
If your funds are already sent to the wrong place, skip ahead to Section 6 and start collecting evidence now. Never resend funds to the same address hoping to trigger a credit, and never click Discord or direct message recovery links. No legitimate recovery process starts in your DMs.
SECTION 02
Reference Tables
Table A. Wrapped RBNT Contract Addresses
Checked against Redbelly's own announcements and documentation.
| Chain | Contract Address | Confidence |
|---|---|---|
| Ethereum | 0xb45ffb51984d626ee758b336c61cf20990c6bf13 | High (dedicated official announcement) |
| Solana | 2GBVt2ENvbHepuJMWYTPkkfpWUabAhsaXToYw8UphxS3 | High (dedicated official announcement) |
| Redbelly Network (native chain) | 0x6ed1F491e2d31536D6561f6bdB2AdC8F092a6076 | High (confirmed directly) |
| Base | 0x020940df9F5E77338a094D55b5B5914122a804A5 | Medium (listed on Redbelly's own docs) |
| BNB Chain | No official token exists | Confirmed absent, impersonator tokens found |
Table B. Current Swap Liquidity by Chain
Checked live, August 2026. Price impact figures are quotes at the time of checking and will move as pools change.
Ethereum
The WRBNT/WETH pool holds roughly $33,000. That is enough for modest swaps and punishing for large ones, so size matters more than routing here.
| Swap Size | Price Impact |
|---|---|
| 100,000 WRBNT | 1.5% to 2.9% |
| 1,000,000 WRBNT | 13% to 14% |
Solana
Solana liquidity is effectively unusable for meaningful swaps right now. A 10,000 WRBNT swap already returns an impact figure that makes execution irrational rather than merely expensive.
| Swap Size | Price Impact (Raydium) |
|---|---|
| 10,000 WRBNT | 86.77% |
Base
Base currently shows lower price impact than Ethereum at matched sizes, despite having no dedicated official liquidity announcement from Redbelly. Quotes also diverge noticeably between aggregators, so check more than one before executing.
| Swap Size | Price Impact | Source |
|---|---|---|
| 1,000,000 RBNT | 7.9% to 8.0% | Two aggregators |
| 100,000 RBNT | 13.4% | Separate widget |
SECTION 03
Failure Mode 1. Wrapped RBNT Zero Value or Swap Fail
Step 1
Confirm the contract address
Compare the token contract in your wallet against Table A in Section 2, character by character, including the leading characters. A wrapped token showing zero value is very often the wrong contract rather than a broken one. On BNB Chain there is no official token at all, so any RBNT looking asset there is an impersonator and has no recoverable value.
Step 2
Check pool depth before swapping
If the contract is correct, look at pool depth for your chain in Table B. A large price impact warning is the pool being honest with you, not a bug. On Solana, a 10,000 WRBNT swap quoting 86.77% impact means the pool cannot absorb your order, and forcing it through by raising slippage would hand most of the value away.
Reduce size, split the swap, or move to a chain with deeper liquidity instead of overriding the warning.
Step 3
Rule out ordinary transaction issues
If the contract is right and the pool is deep enough, the cause is usually mundane: insufficient native gas on the chain you are swapping on, a quote that expired while you were confirming, or a slippage tolerance set too tight for current conditions. Refresh the quote, confirm your gas balance, and retry once with a realistic slippage setting.
SECTION 04
Failure Mode 2. Quote Unavailable Bridging RBNT Back to Redbelly Network
Redbelly's own developer documentation names Lucid Labs Bridge as the official route for bridging RBNT back to Redbelly Network. It supports nine source chains. If your source chain is not one of them, no quote will appear, and that is the expected behaviour rather than a fault in your wallet.
Verified Bridge Routes
| Source Chain | Asset | Route | Fee | Time |
|---|---|---|---|---|
| Ethereum | RBNT | Stargate | 0.00016 ETH | About 109 min |
| Ethereum | WRBNT | Polymer | 0.000015 ETH plus 10 WRBNT | About 2 min |
| Base | RBNT | Stargate | 0.00016 ETH | About 1 min |
| Base | WRBNT | Polymer | 0.000015 ETH plus 10 WRBNT | About 10 sec |
| BSC | RBNT | Stargate | 0.0005 BNB | About 124 min |
| Arbitrum | RBNT | Stargate | 0.00017 ETH | About 172 min |
| Polygon | RBNT | Stargate | 4.43 POL | About 190 min |
| Avalanche | RBNT | Stargate | 0.05 AVAX | About 62 min |
| Sonic | RBNT | Stargate | 14.21 S | About 93 min |
| ⚠ Solana | RBNT | No route found | N/A | N/A |
Solana is the one confirmed unresolvable case. There is no supported route from Solana back to Redbelly Network through the official bridge at the time of checking. This will not resolve by retrying, by changing wallets, or by adjusting the amount.
What to do
- Do not repeatedly retry. Repeated attempts cost gas and produce the same result.
- Check Lucid Labs directly for current chain support, since supported chains can be added over time.
- Consider moving your funds to a working chain first, if a supported path exists from where you hold them.
- Never use an unofficial bridge to work around a missing route. An unsupported route is a limitation, an unofficial bridge is a risk of total loss.
SECTION 05
Failure Mode 3. Stablecoins Stranded on Ethereum Mainnet
reddex is Redbelly's official interface for this route. Use it rather than a third party front end, and treat any other interface offering the same transfer as unverified.
Route and Fee
| Asset | Route | Fee |
|---|---|---|
| USDT | Lucid Labs (Polymer) | 1% |
| USDC | Lucid Labs (Polymer) | 1% |
| WRBNT | Lucid Labs (Polymer) | 1% |
Step 1
Confirm the source transaction on Etherscan
Look up your transaction hash and confirm the transfer actually succeeded on Ethereum mainnet, with the correct token contract, amount, and destination. If the source transaction failed, nothing left your wallet and there is nothing to recover.
Step 2
Give it time
Polymer transfers normally complete in 10 seconds to a few minutes. Anything past 30 minutes is a genuine delay worth investigating, but the first few minutes are normal operation, not a stuck transfer.
Step 3
Check reddex directly for status
Open reddex and check the status of the transfer there rather than judging by your wallet balance alone. The interface is the authoritative view of whether the destination leg has been delivered.
Step 4
If still stuck, collect evidence and contact support
Gather the following before you open a ticket:
- Transaction hash
- Amount and asset
- Timestamp
- Destination address
Contact Redbelly or reddex support directly with that evidence. Never resend the funds, and never click Discord or direct message links offering to unstick the transfer for you.
SECTION 06
Failure Mode 4. Native RBNT Sent to a CEX Deposit Address by Mistake
Recovery is possible here, but it is never guaranteed on any of the four exchanges. Each one runs a manual process with its own rules, fees, and limits, and each reserves the right to decline. Act quickly and keep your evidence tidy, because a complete first message is the single biggest factor you control.
Evidence to collect first
- Transaction hash of the deposit
- The exact deposit address you sent to
- The exact asset and network used
- Amount and timestamp
- Your account identifier on the exchange (UID or registered email)
Gate
Self service "Deposit Not Received, Recovery Request" tool. You submit the request yourself with the transaction details.
MEXC
Dedicated "Wrong Deposit Return Application". A processing fee applies, and funds are returned to the original sending address, not credited to your MEXC balance.
BYDFi
No self service form. Contact Customer Support directly with the transaction ID and your UID.
WhiteBIT
Weakest documented process of the four. General support ticket only, with no dedicated recovery tool.
None of these processes guarantee recovery. Never send additional funds to the same address, and never click links claiming to expedite recovery in exchange for a fee or your wallet credentials.