Flap Volume Trading

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

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. Use the Portal for two-way trading of existing tokens, validating their curve or DEX state and actual quote asset. Curve trading supports non-tax versions 0/1/2/7, symmetric-tax versions 4/5 and asymmetric-tax version 6; unknown versions, invalid tax rates and unverifiable extensions are rejected. Group migration checks use that token’s real r/h/k, reserve, migration threshold, protocol fee and buy tax, rather than token-creation defaults. Currently enabled standard and RWA quote assets are supported; migration or protocol changes pause execution.

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 Flap 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?
Use the Portal for two-way trading of existing tokens, validating their curve or DEX state and actual quote asset. Curve trading supports non-tax versions 0/1/2/7, symmetric-tax versions 4/5 and asymmetric-tax version 6; unknown versions, invalid tax rates and unverifiable extensions are rejected. Group migration checks use that token’s real r/h/k, reserve, migration threshold, protocol fee and buy tax, rather than token-creation defaults. Currently enabled standard and RWA quote assets are supported; migration or protocol changes pause execution.
How are fees paid?
A separate fee wallet pays for Swap tasks prepared and included in the submission group. Approvals are not Swap tasks, covered tasks are not charged again on retry, and the budget is not actual expenditure.
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?
Estimate the actual Portal swapExactInput call with its sender and native value, add a rounded-up 5% margin, and enforce the configured per-trade Gas Limit. A failed simulation or exceeded budget prevents that Swap from being sent; completed approvals retain their real results. Migration checks use the token’s own curve and actual protocol fees and taxes, rather than default raise budgets from token creation.
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.