BSC Alpha Volume Trading

Set separate buy and sell rules, with one of each per wallet per cycle. Every wallet must hold both initial assets, two embedded service fees and Gas before starting.

Buy Settings
Fixed Amount
Sell Settings
Balance Percentage
%
Execution Settings
Random First Direction
%

Sell First Probability (%): 50.0% · The probability selects which direction runs first in each cycle; the second trade runs in the opposite direction. Each wallet has one buy and one sell per cycle. Retries retain the original order and resolved amounts.

Round Robin

Default 1, maximum 5. Wallet pairs are scheduled together; both trades for the same wallet always run serially. Consecutive order requires concurrency 1 and a finite cycle count; price-based stopping is unavailable.

s
s
Cycles

Each cycle is one buy and one sell per wallet. One cycle plans two Swaps per wallet.

%
Gwei

Each trading wallet pays its service fee inside each trade. No separate fee wallet is used. Approvals need additional Gas, and the budget is not actual expenditure.

Trading Wallets · 0 / 20
ID
Address
BNB
Payment Asset Balance
Target Asset Balance
status
Actions
No data available
Planned Fee Budget
Service Fee
0 BNB
Estimated Swap Gas
0 BNB
Estimated Approval Gas
0 BNB
Total BNB Fee Budget
0 BNB
Buy Input Amount
—
Sell Input Amount
—
Each trading wallet pays its service fee inside each trade. No separate fee wallet is used. Approvals need additional Gas, and the budget is not actual expenditure.
The lowest service fee in the network, only per transaction
0.008
0.01  BNB

Select quote asset Q and target asset T: buying swaps Q→T and selling swaps T→Q. Import up to 20 wallets with concurrency up to 5; each wallet executes its two legs serially. Fetch a new aggregated route per trade, using exact decimal amounts and passing slippage to the quote API. Finite-cycle mode does not require a reference-price quote. Price-stop mode freezes the largest actual first-cycle sell amount after initial checks and reuses that quantity for reference quotes, avoiding an arbitrary one-token quote. This reference is not each trade’s execution price. The trading wallet pays the service fee with the business-contract call; there is no separate fee wallet, and a timeout does not cancel a transaction.

How to Use

  1. Select both assets and validate the protocol market.
  2. Import up to 20 unique wallets and fund both initial assets, Gas and fees.
  3. Set both amount rules, trade order, wallet order, concurrency and intervals.
  4. Set cycles or price conditions, slippage and Gas, then review the budget.
  5. Start with the read-only all-wallet check, then execute both legs serially per wallet.
  6. Review receipts and query original pending hashes; verify the actual hash after a speed-up, cancellation or replacement before explicitly retrying generated incomplete tasks.

Need support for BSC Alpha Volume Trading? contact us.

FAQ

How many trades does Volume Trading plan per cycle?
Each wallet plans one buy and one sell. Choose their order or a probability for the first direction; 0% and 100% still plan both legs. The second is prepared only after the first confirms successfully.
Which initial balances are required?
Every wallet must already hold both first-cycle input assets, Gas for both Swaps and required approvals, and the complete first-cycle fees. Proceeds from the first trade cannot fund the initial check. Any failed check prevents all broadcasts. Initial amounts are saved; later cycles use current balances.
Which amount rules are supported?
Each side supports fixed amounts, random ranges, balance percentages, retained balances and all available funds. Native inputs reserve Gas and fees first. Random amounts are sampled once and determined amounts are retained on retry.
Which protocol restrictions apply?
Fetch a new aggregated route per trade, using exact decimal amounts and passing slippage to the quote API. Finite-cycle mode does not require a reference-price quote. Price-stop mode freezes the largest actual first-cycle sell amount after initial checks and reuses that quantity for reference quotes, avoiding an arbitrary one-token quote. This reference is not each trade’s execution price. The trading wallet pays the service fee with the business-contract call; there is no separate fee wallet, and a timeout does not cancel a transaction.
How are fees paid?
Each trading wallet includes its service fee in each business call; approvals need additional Gas. No separate fee transaction is sent. Actual costs follow contract execution and receipts.
How do stopping and retrying work?
The two independent on-chain trades are not atomic. A price boundary stops only new, unstarted pairs; a pair whose first trade has confirmed successfully continues preparing and executing its second trade, subject to balance, quote and protocol checks. Manual stopping, failed or pending transactions, and hard failures such as protocol migration can still interrupt a pair. Already broadcast transactions are not cancelled. An explicit retry checks price admission again and only retries generated incomplete tasks, preserving their directions and resolved amounts without replaying successful trades or creating later cycles. Recovery records stay in the current page and are not guaranteed to survive a browser refresh.
How is Gas simulated and capped?
Fetch a fresh aggregated route and estimate the actual business-contract transaction for each trade. Before signing and broadcasting, enforce the configured per-Swap Gas cap while separately reserving approval and later-trade Gas. A failed simulation or exceeded cap prevents that Swap from being sent. Wallets run independently in parallel, so the group is not an atomic zero-approval or zero-broadcast operation. Service fees execute with the business call and depend on its on-chain result.
How are sped-up, cancelled or replaced transactions verified?
Query the original transaction hash first. If it was replaced, enter the actual replacement hash for the pending entry. Verification establishes the chain, sender and nonce against a canonical confirmed block and receipt, then compares the destination, calldata and value. Only a successful same-call replacement with changed Gas can complete the original task. A cancellation or different call fails the original task while advancing the consumed nonce. A consumed nonce alone never proves success; insufficient evidence keeps the entry pending without automatic resubmission.