How to sell ACTUALLY with Bitget Wallet
- Download and open the Bitget Wallet app, and ensure your account holds sol ACTUALLY tokens.
- Swap sol ACTUALLY tokens for USDT or USDC on Ethereum, Solana, BNB Chain, Base, or the TRON network.
- Select the token to sell: Open the [Trade] page, navigate to the [Cross-Chain Swap] section, select the token you wish to sell along with its network (e.g., ACTUALLY on the sol chain), and enter the amount.
- Select the token to buy: Choosing a token on the same chain (e.g., USDT or USDC on Ethereum, Solana, BNB Chain, Base, or Tron) constitutes a same-chain trade, whereas choosing a token on a different chain constitutes a cross-chain trade. Gas fees for cross-chain trades are typically higher than those for same-chain trades.
- Review trade details: The system will display the amount of the target token you can receive based on real-time prices. You can view the current slippage and price impact (factors that affect the final amount of tokens received) and check or modify the destination address (defaulting to your current wallet address).
- Set appropriate slippage: When the price of a token is very volatile or the pool has low liquidity, setting a low slippage tolerance may cause the transaction to fail. We recommend using Bitget Wallet's Smart slippage to ensure smooth transactions.
- Confirm Gas fees: Click [Confirm] to view the estimated Gas fee for the transaction. If your balance is insufficient, follow the on-screen instructions to deposit the necessary native network coin to cover the fee.
- Confirm the transaction: Click "Confirm" again on the transaction details page and wait for the transaction to be confirmed on the chain. Remember that once you click "Confirm", the transaction cannot be canceled. Even if the transaction fails, you will still be charged a gas fee.
What are common reasons for a failed transaction?
1. Gas fee is insufficient or set too low, so validators don't process it. 2. Insufficient wallet balance. 3. Network congestion, causing long processing delays.
What should I do when a transaction fails?
Insufficient gas: Top up native tokens, increase the gas fee, or use Bitget Wallet's GetGas service. Insufficient balance: Add funds and resend. Network congestion: Increase the gas fee for higher priority, or wait and try again. For more issues, contact customer support and provide the transaction hash (viewable on a block explorer).
Frequently Asked Questions
Yes. Bitget Wallet allows you to swap ACTUALLY for USDT on supported networks, including Ethereum, Solana, BNB Chain, Base, and TRON. If you choose USDT on the same blockchain, the transaction is considered a same-chain swap.
Yes. Because ACTUALLY is on the sol network, you'll need a small amount of the network's native token to pay Gas fees. Without enough Gas, the transaction cannot be processed.
Yes. You can swap ACTUALLY directly within Bitget Wallet using the Cross-Chain Swap feature without first depositing your assets into a centralized exchange.
The minimum amount depends on available liquidity, network requirements, and the trading route selected by the swap aggregator.
The easiest method is to use Bitget Wallet's Cross-Chain Swap feature. It lets you exchange ACTUALLY directly into supported cryptocurrencies without transferring assets to a centralized exchange.
A swap may fail due to insufficient Gas fees, low liquidity, rapid price changes, network congestion, or a slippage tolerance that is set too low.
Gas fees vary depending on network activity. During periods of heavy blockchain usage, transaction costs are generally higher.
No. Once an on-chain transaction has been signed and submitted, it cannot be canceled. Always verify the transaction details before confirming.
Yes. Bitget Wallet supports cross-chain swaps, allowing you to exchange ACTUALLY for assets on other supported blockchain networks.
The final amount can be affected by the current market price of ACTUALLY, liquidity, price impact, slippage, and applicable network or swap fees. The estimated amount may also change before the transaction is confirmed.

