Create a Solana Connector and fund your Vault
Create a DEX Solana Vault Connector, authorize setup with your owner wallet, fund the correct trading and fee accounts, and verify balances before starting a Plan. All amounts and addresses in the demonstration are examples, and the wallet operations and displayed balances are simulated. Never send funds to example addresses.
Create a Solana Connector and fund your Vault — MP4 · SRT
Understand the owner wallet, Vault and bot
The owner wallet authorizes setup and controls owner-only management actions. The Vault holds trading assets in program-controlled token accounts. A separate bot wallet submits automated trades through Jupiter and pays SOL network fees.
These are three different roles. Keep Vault trading capital separate from the bot’s fee reserves, and always use your own current addresses from the application.
Prepare your wallet and separate budgets
Use a Solana-compatible wallet such as Phantom. Keep SOL in the owner wallet for setup network fees and account rent. Network fees are spent; rent is a SOL deposit normally recoverable when eligible empty accounts are closed.
The example budgets 0.1 SOL in the owner wallet, 500 USDC for Vault trading capital, about 10 US dollars worth of native SOL for bot fees, and optionally 10 USDC for future fee replenishment. These are examples, not platform minimums, recommendations or a fee quote. Follow the live setup estimate, current SOL price and application fee warnings.
Choose the interface and supported assets
Open Connectors, open the interface selector and choose DEX Solana Vault. This Connector uses a Solana wallet and Vault rather than exchange API credentials. Open interface guide links to https://x.coinrobot.ai/docs/dex-solana.
Enter a recognizable Connector name, such as Solana tutorial, and select the supported symbols your Plans may use. The example selects the current complete 21-symbol list; USDC is included automatically during setup.
More selected assets can require more token accounts, rent and setup approvals. Selecting symbols does not buy those assets or start trading. Vault address is read-only and is generated through the wallet setup.
Connect the owner wallet and approve setup
Click Generate new Vault (wallet) and connect the intended owner account in Phantom. The connection shares a public owner address; requested operations require your approval. No owner seed phrase or private key is requested, recorded or needed. Never enter either into the site. Phantom prompts can vary by version.
The fresh, full-list example requests 11 setup transactions to initialize the Vault and selected token accounts. These are not eleven trades or purchases. The actual approval count can vary with selected assets, existing accounts and how instructions fit into transactions.
Review the operations and costs in Phantom before approving. The owner wallet pays network fees and account rent. Keep the page open until setup, confirmations and automatic saving finish. The demonstration’s wallet approvals and confirmations are simulations.
Review the saved Connector and deposit addresses
After setup is confirmed, find the Connector under Existing connectors and open Edit to review the generated read-only Vault account and address information. A saved Connector is not an active trading Plan; trading begins only after you create and start a Plan.
Do not send trading USDC to the Vault account or program-state address. Use Vault USDC deposit token account — trading capital for trading USDC, SOL fee address — bot-wallet for the bot’s native SOL, and USDC fee token account — bot-wallet ATA only for the optional fee-replenishment reserve.
Distinguish these addresses from the owner address. The documentation also shows integration addresses for a signed-in user with a saved Connector. Copy your own current addresses from the application, never the demonstration’s example addresses.
Fund the bot with native SOL
First send a small native SOL reserve on Solana to SOL fee address — bot-wallet. The example uses about 10 US dollars worth of SOL; the SOL quantity depends on the current price.
This is a network-fee budget, not trading capital or a guarantee of indefinite operation. A new bot cannot pay for its first transaction with USDC alone. Even a USDC-to-SOL fee-replenishment swap requires native SOL for execution. Leave headroom and top up when the application warns that fees are low.
Fund the Vault with trading USDC
Choose USDC on Solana mainnet in your wallet and send the capital you intend to trade to Vault USDC deposit token account — trading capital. Verify the network, token and recipient before confirming.
The example uses 500 USDC, not a required investment or platform minimum. Token-account setup rent is separate from trading capital. Do not send trading USDC to the Vault program-state account, a bot fee account or a different chain.
Optionally add a fee-replenishment reserve
USDC fee token account — bot-wallet ATA can hold an optional USDC reserve for fee replenishment. The example uses 10 USDC, separate from the trading USDC in the Vault.
When native SOL becomes low, CoinRobot may attempt a USDC-to-SOL swap from this dedicated bot account. This requires available USDC, enough native SOL to pay for execution and an available route. Success is not guaranteed, so keep native SOL available as well.
Test the Connector and verify account balances
After your real transfers are confirmed, use Test on the saved Connector. Then open Dashboard and expand Open position balances by connector. Select your Connector, such as Solana tutorial, and click Show full account balance.
Check the selected Connector and update timestamp. Verify the Vault USDC deposit address and the trading-balance table, then inspect the separate bot-wallet fee table. Vault USDC is trading capital; bot native SOL pays network fees; bot USDC is an optional fee-replenishment reserve.
The simulated balance example shows 500 Vault USDC, 0.08 bot SOL and 10 bot USDC. These are illustrative balances, not evidence of a live funded account, transfer or trade.
Read balance allocations before creating a Plan
Account amount, robot open amount and DIFF compare reported holdings with robot allocations. Before the first Plan, there may be no tracked allocation. In the example, no Plan is running, the robot-open quantity is a dash and the allocated-value total is zero.
A dash means unavailable data, not a measured zero. DIFF represents the reported holding in this example, not profit; a positive DIFF is not a profit figure.
Refresh after confirmed transfers and investigate missing funds before starting. Once trading USDC and native SOL are confirmed in the correct accounts, use New Plan to configure your strategy and risk settings. Creating the Connector alone does not place trades.
Use the detailed guide for security and exit procedures
Keep https://x.coinrobot.ai/docs/dex-solana nearby. Review Your Solana integration addresses and Operational security checklist, along with the permission model and public Verified Build/source links. This setup overview does not replace the detailed guide.
If a confirmation is delayed, check its status and follow the UI retry guidance rather than blindly signing duplicate operations.
Stop Plans before withdrawing or closing the Vault. Withdrawals return assets to the saved owner. Withdraw ALL and Close Vault have different purposes; follow the current UI instructions for exiting and closing the Vault.