bandforband.fun docs
Chains & bridging

Bridging

How deposits and withdrawals move through Relay, what they cost and how new assets are added.

Deposits and withdrawals from another chain or asset go through Relay, a cross-chain payments network. bandforband.fun never holds your funds in between: Relay delivers USDC to your wallet on Solana, and it goes into your vault from there.

Deposits

  1. On Wallet → Deposit, pick the chain and asset you send from.
  2. You get a one-time deposit address from Relay. Send the asset there from any wallet or exchange.
  3. Relay converts it to USDC on Solana and delivers it to your embedded wallet.
  4. The USDC is moved into your vault, automatically if you turned on automatic deposits in Profile → Settings, or with one click on Move to vault.

Sending USDC on Solana straight to your embedded wallet skips Relay entirely. The minimum deposit is $5.00. Details in Deposit.

Withdrawals

  1. On Wallet → Withdraw, pick the destination chain, asset and address.
  2. You sign one Solana transaction. It takes the USDC out of your vault, and the program sends the withdrawal fee to the treasury in the same transaction.
  3. Relay converts the USDC and delivers the asset on the destination chain.

The minimum withdrawal is $5.00. Fees are listed in Withdrawals.

Status and history

Every deposit and withdrawal shows its steps, from Relay's first confirmation to delivery, with links to both chains' explorers, in Wallet → Transfers. The matching vault movements are also in Wallet → Transactions, with every other movement of your money.

If a bridge fails

When Relay cannot complete a route, it refunds it, and the transfer shows as refunded with the reason.

  • A failed withdrawal comes back as USDC to your embedded wallet on Solana and is moved back into your vault.
  • A failed deposit is refunded on the chain you sent from.

Relayed app trades

Fomo and pump.fun trades on Robinhood Chain are scored from Relay's order for that transaction (GET /requests/v2?hash=). The order has to be a success for that wallet and that exact token amount, with the app's referrer and a positive fee to the app's fee wallet. The USD amount is the order's cash side, and it has to sit within 0.5% of the USDG the router moved. A repeated look at the same transaction uses the per-hash cache: a matched order is kept, and a miss is looked up again after five minutes. That is the same chain read the scorer already does (eth_getTransactionByHash and the receipt) plus that one v2 call. The receipt check does not add an RPC call and does not change the score.

GET /requests/v2 retires on 24 Nov 2026. It cannot move to GET /requests/v3 or GET /intents/status/v3: v3 only returns this API key's requests and hides other integrators' referrers, and the status endpoint has no referrer. The Source tag in the router call is KyberSwap's client tag. It is present only when the solver routes through Kyber. About 28% of Fomo fills and about 70% of pump.fun fills are untagged. Those go through 0x AllowanceHolder or 0x603206d6 and look the same for every integrator. There is no per-fill on-chain fee. A sell cannot be proven from the receipt: EntryPoint and Multicall3 are permissionless, a tag can be attached to any executed call, and USDG paid into the router is not the user's proceeds.

Replacing the v2 call needs a feed from Relay, Fomo, or pump.fun. For each transaction hash that feed has to supply the referrer (fomo or elon123), that the order succeeded, the user and the recipient, the token's chain and exact amount, the cash amountUsd the user paid or received, and a positive app fee paid to that app's fee wallet.

How a deposit is tracked

Relay posts a signed webhook to the API. While valid signatures are arriving, the worker does not poll Relay for that transfer. The first safety-net read is about two minutes after the wallet send or the deposit-address quote. After that, an in-flight transfer is checked at most every five minutes, and a deposit-address quote at most every fifteen, until the transfer finishes or expires.

If no valid webhook arrives for ten minutes while a transfer is in flight, or a signature check fails and no valid signature follows, the worker logs a warning and returns to the fast schedule: every eight seconds for two minutes, then a backoff that tops out at five minutes. A delivered webhook updates the transfer immediately. A lost webhook, while the channel is otherwise healthy, is caught within five minutes.

The heartbeat is three settings rows, relay.webhook.ok, relay.webhook.fail, and relay.webhook.alert, so one writer cannot erase another's timestamp. A bad signature updates the fail row at most once a minute, and the webhook route accepts at most 120 requests a minute. There is no new environment variable and no migration.

Adding assets

The assets you can deposit and withdraw are listed on Chains & bridging. New ones are added when Relay supports them.

On this page