PancakeSwap Volume Trading - V2

Each wallet performs one buy and one sell per cycle with separate amount rules. Before starting, every wallet needs both input assets and Gas, and the fee wallet must cover the entire first cycle.

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
*

An independent wallet pays service fees for tasks prepared for submission in the current group, not only trades that ultimately succeed.

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
Estimated Fee Transaction Gas
0 BNB
Total BNB Fee Budget
0 BNB
Buy Input Amount
—
Sell Input Amount
—
Fees are based on tasks prepared for submission in each group. Failed trades may still incur service fees and Gas. Budgets are not actual spending.
The lowest service fee in the network, only per transaction
0.0008
0.001  BNB

Choose quote asset Q and target asset T: buying swaps Q→T and selling swaps T→Q. Each wallet plans one buy and one sell per cycle, with a fixed order or a buy-first probability; the second trade is prepared after the first succeeds. Before the first cycle, every wallet must already hold both input amounts and enough BNB for both Swaps and required approvals, while the fee wallet must cover the entire first cycle. First-cycle amounts are fixed from initial balances; later cycles use current balances. Import up to 20 wallets with concurrency capped at 5 and serial execution for each wallet.

How to Use

  1. Select quote asset Q and target asset T and confirm that a PancakeSwap V2 pair exists.
  2. Import up to 20 wallets and fund both initial input assets plus BNB Gas for both trades and any required approvals.
  3. Set separate amount rules, choose buy then sell, sell then buy or a random first direction, and independently configure wallet order, concurrency and group intervals.
  4. Set cycles per wallet or a price range, slippage, Gas and a separate fee wallet, then review the budget. Each cycle plans one buy and one sell per wallet.
  5. Start with a read-only check of every wallet’s initial balances, Gas and whole-first-cycle fees. Approvals and trades start only after all checks pass. First-cycle amounts are saved from initial balances; the second trade follows the first confirmed success, and later cycles use current balances.
  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 PancakeSwap Volume Trading - V2? contact us.

FAQ

How is the order configured for Volume Trading?
Each cycle is one buy and one sell per wallet. Choose buy then sell, sell then buy, or use the buy-first probability to select the first direction; the second trade is always the opposite. A probability of 0% or 100% still plans both trades. Buy and sell amounts follow their own rules; the sell amount is not automatically changed to the amount bought in that cycle.
Which amount rules are available?
Both sides support a fixed amount, random range, balance percentage, retained balance or all available funds. Before any transaction starts, every wallet’s initial balances must cover both first-cycle input amounts and Gas for both Swaps and required approvals, without relying on proceeds from the first trade. Both first-cycle amounts are resolved and saved from initial balances, and random amounts are sampled once. Any insufficient wallet or uncertain read blocks the whole start without sending approvals or fees. Later cycles resolve and validate amounts using current balances; BNB inputs reserve the applicable Gas budget first.
How do wallet order and concurrency work?
Wallet order is independent of buy/sell order. Import up to 20 wallets and choose round-robin, random or consecutive order. Random order shuffles wallet pairs without breaking the dependency between their two trades. Concurrency is capped at 5 and cannot exceed the wallet count. Approval, Swap and confirmation remain serial for each wallet, with the second trade prepared only after the first succeeds. Strict consecutive order requires concurrency 1 and a finite cycle count.
How is the service fee charged?
The page uses the current V2 market-making fee configuration. A separate fee wallet pays for tasks prepared and included in the current submission group. Before starting, its balance is checked against both tasks per wallet in the entire first cycle and the estimated fee transaction Gas; this check does not charge fees upfront. Fees are not limited to Swaps that ultimately succeed, future cycles are not charged upfront, and previously charged task IDs are not billed again on retry. Network Gas is separate.
What happens after a failed or pending transaction, or when execution stops?
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. A failed or pending first trade blocks the second, and Bundle acceptance is not on-chain success. After the initial check passes, retries validate current funds for remaining tasks without requiring spent initial two-sided balances again.
Are execution, price or returns guaranteed?
No. The initial check prevents starting with an already-insufficient opposite-side balance, but the two independent trades are not atomic. Execution still depends on quotes, slippage, balances, approvals, liquidity, Token rules and on-chain results. A wallet’s cycle is marked successful only when both trades succeed. The page does not guarantee trade counts, prices or returns.
How is Gas simulated and capped?
Before signing, estimate Gas for the complete Swap call with its actual sender, value and calldata, add a rounded-up 5% margin, and enforce the configured Gas Limit as the per-trade cap. A failed simulation or exceeded cap stops the group before its fee or Swap broadcasts; already confirmed approvals retain their real receipts. The budget is not actual expenditure and does not guarantee unchanged market conditions.
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, including entries from the separate fee wallet. 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.