Getting started

Before your first swap#

Use an account and wallet supported by the deployed application. Keep enough native ETH for applicable network costs. Robinhood Chain uses ETH for gas; network configuration should come from the official network documentation and the application's verified release configuration.^[1]

A demo preview must not submit wallet transactions. A test environment uses test assets. Neither screen is evidence that QuiverDex supports real-value trading.

1. Connect your wallet#

Choose Connect wallet and review the connection request. Connecting an account is different from granting a token spending approval or signing a swap. A mismatch between the wallet network and the application's configured network must be resolved before a transaction is prepared.

2. Choose assets and enter an amount#

Choose the asset you want to pay and the asset you want to receive. Confirm the contract identity, not just the symbol or icon. The supported asset list must come from the application's registry. Missing or restricted assets should not be presented as routable by default.

Enter an amount you intend to exchange. The Max control must leave an appropriate reserve for applicable network costs when the input is the native gas asset. Read Supported assets for asset-status details.

3. Review the quote and permissions#

Review the expected net output, minimum received, price impact, platform fee, pool fees where known, and estimated network cost. A quote is an estimate with a validity period, not a guaranteed future price.

An ERC-20 asset may require a spending approval before the swap. Check the requested token, spender, amount, and any expiry. An approval transaction is not a completed swap.^[2] Read Safety before accepting an unfamiliar request.

4. Confirm the swap#

After any required approval, obtain and review a fresh quote. Confirm the final request in your wallet only when the recipient, amount, network, and minimum output match your intention.

The intended router may combine swap legs into one swap transaction. This does not promise that every trade will require exactly one wallet request. Required approvals, wallet type, and the deployed implementation affect the steps you see.

Follow the transaction#

Once a transaction hash is available, use the transaction detail panel to inspect its status. A successful receipt, network finality, and points processing are separate milestones. Robinhood Chain documents staged transaction finality; the interface must not label a soft confirmation as full finality.^[3]

Closing the panel does not cancel a transaction already sent to the network. If status is unknown, check the existing hash before submitting another transaction.

When something goes wrong#

No route: there may be no supported path for the asset pair or amount.
Quote expired: refresh and review the new output.
Insufficient ETH: leave enough balance for network costs.
Request declined: a wallet request was rejected; inspect whether any earlier step was already submitted.
Transaction failed on chain: review the receipt; network costs may still apply.^[4]

See FAQ for more troubleshooting guidance.