Create an Arbitrum Connector and fund your Vault
Configure an Arbitrum Connector, deploy a Vault through the owner wallet, and fund the Vault and bot wallet for their separate roles. Use Arbitrum One and verify addresses, tokens and balances before starting a Plan. The walkthrough uses simulated wallet prompts, addresses, balances and transfers; all example amounts are illustrative, not required minimums.
Create an Arbitrum Connector and fund your Vault — MP4 · SRT
Understand the Vault, bot and owner roles
The Arbitrum Vault holds trading capital. The separate bot wallet submits automated trades and pays gas. The owner wallet authorizes deployment and privileged management. Review the DEX-Arbitrum guide and Vault/bot flow diagram to understand these roles before funding any address.
Use Arbitrum One and separate budgets
Use Arbitrum One, chain ID 42161. Keep native ETH in the owner wallet for deployment gas, budget USDC for Vault trading capital, and reserve a small amount of native ETH for the bot. Optional bot USDC is a separate reserve for possible later gas replenishment.
Follow the wallet’s current fee quote. There is no universal fixed deployment cost, and the example budgets are not platform minimums.
Configure the Arbitrum Connector
On Connectors, choose DEX Arbitrum Vault. Enter a recognizable name and choose supported assets. Selecting assets does not place trades.
Leave the read-only Vault field unchanged. The wallet deployment flow supplies the Vault address.
Connect the owner wallet
Choose Generate new Vault and connect the intended owner account in a compatible wallet. Confirm that the network is Arbitrum One.
Share only the public address and approve only operations you understand. Never share the owner seed phrase or private key. The connection prompt in this walkthrough is simulated.
Review and approve deployment
Review the contract deployment and gas estimate in your wallet. The owner pays deployment gas in native ETH. Check the account and network before approving, then wait for confirmation and saving.
The approval in the demonstration is an illustration: no live deployment transaction is submitted and no contract is deployed.
Check the saved addresses
Open Edit on the saved Connector and review the Vault, owner and bot address fields. The Vault address receives trading USDC; the bot address receives the small fee reserve.
Copy only your own current addresses from the application. Do not use the demonstration addresses.
Fund the bot with native ETH
Before automated trading, send a small amount of native ETH on Arbitrum One to the bot wallet. The example budgets about ten dollars’ worth of ETH, not a fixed required quantity.
The bot needs native ETH even for a possible fee-replenishment swap. USDC alone cannot pay its first gas fee.
Send trading USDC to the Vault
Send your chosen trading capital to your own Vault using native USDC on Arbitrum One. Check the network, token and recipient before confirming. Do not send trading capital to the bot wallet.
The example uses 500 USDC, not a required investment. The demonstrated transfer is not signed or submitted.
Consider optional bot USDC
You may keep a little USDC on the bot wallet for later gas replenishment. The example uses 10 USDC.
CoinRobot can attempt to buy ETH when the bot’s native balance is low, provided funds and a suitable route are available. Replenishment is not guaranteed, so maintain native ETH headroom and watch fee warnings.
Verify Vault and bot balances
Open Dashboard and load the Connector under Open position balances by connector. Review the Vault trading assets and the separate bot fee section, including bot ETH and USDC.
Compare account amounts, robot allocations and differences. The demonstration balances are simulated. Only start a Plan after your real deposits are confirmed.
Exit while retaining control
Consult the DEX-Arbitrum guide for contract permissions and withdrawal instructions. Stop Plans before exiting, then follow the current withdrawal or Close Vault flow.
Removing a Connector record does not return on-chain funds. The owner can also manage the contract directly. No withdrawal, revocation, close or delete request is performed in this demonstration.