AchSwap

Every scenario DeepQA drove in the browser, in plan order, with the 36 screenshots it captured along the way. A passing scenario is evidence too.

1. S1

   Execute a token swap

   5 steps, 3 screenshots

   high✓ pass

   

   

   

   • Entered 1 USDC to swap for 9.4030 ACHS with quote calculated and Swap button enabled.
   • Swap executed successfully with toast notification 'Swap successful! Swapped 1 USDC → 9.4030 ACHS via V3' and token [redacted] updated accordingly.
   • Successfully executed swap of 1 USDC to 9.4030 ACHS via V3 protocol.
   • Observed 'Swap successful!' notification and updated token [redacted] (USDC from 3 to 1.9972, ACHS from 0 to 9.403).
2. S2

   Add liquidity to a pool

   6 steps, 3 screenshots

   high✓ pass

   

   

   

   • Navigated to the Liquidity page where V2 is selected by default.
   • Selected the V3 protocol tab, showing Token A (USDC), Token B (ACHS), and fee tiers.
   • Entered 0.1 USDC, which auto-calculated 0.929149 ACHS according to the pool ratio.
   • Navigated to /add-liquidity and switched to the V3 protocol tab.
   • USDC and ACHS token [redacted] was selected with the 0.3% fee tier.
   • Entered 0.1 USDC, and the corresponding 0.929149 ACHS was automatically calculated based on the pool ratio.
   • Clicked 'Add V3 Liquidity', which initiated the liquidity provision flow displaying 'Adding Liquidity…' and 'Approving tokens…Please approve token [redacted]' toast notification without errors.
3. S3

   Remove liquidity from a position

   4 steps, 1 screenshot

   high⊘ blocked

   

   • Navigated to /remove-liquidity on AchSwap DEX.
   • Checked V2, V3, and V4 liquidity tabs on /remove-liquidity.
   • The connected test wallet has no active LP positions (no V2, V3, or V4 positions were found).
   • Without an existing LP position to select and withdraw from, the scenario's removal steps could not be executed.
4. S4

   Bridge network switch rejection handling

   4 steps, 3 screenshots

   high⊘ blocked

   

   

   

   • Navigated to /bridge where the bridge form is loaded with Arc as source and Sepolia as destination.
   • Selected Base Sepolia as the source chain for bridging.
   • Navigated to /bridge and opened the source chain selection modal.
   • Selected Base Sepolia as the non-Arc source chain.
   • Entered 1.0 in the USDC Bridge Amount field.
   • Observed that the bridge button became 'Insufficient USDC Balance' (disabled) because the connected wallet has 0.0000 USDC on Base Sepolia, preventing form submission to test wallet network switch rejection.
5. S5

   Swap configuration settings persistence

   5 steps, 4 screenshots

   medium✓ pass

   

   

   

   

   • Opened Swap Settings modal showing protocol routing, slippage tolerance, and transaction deadline.
   • Set custom slippage tolerance to 1.5% and transaction deadline to 10 minutes.
   • Closed the Swap Settings modal.
   • Navigated to the Swap page and opened the Swap Settings modal.
   • Selected Custom for slippage tolerance and entered 1.5%.
   • Configured the custom transaction deadline to 10 minutes.
   • Closed the Swap Settings modal and verified custom settings were retained.
6. S6

   Validation for insufficient swap balance

   3 steps, 4 screenshots

   medium✕ fail

   

   

   

   

   • Opened Swap page with initial balance of 1.9963 USDC and Swap button disabled.
   • Entered 100 USDC (balance is 1.9963 USDC), but the Swap button became active with text 'Swap' instead of being disabled with 'Insufficient balance'.
   • Clicking Swap initiated the transaction without balance validation, resulting in a 'Simulation Failed' error toast.
   • Navigated to the Swap page where the connected wallet USDC balance was 1.9963 USDC.
   • Entered 100 in the input token [redacted], exceeding available balance.
   • The Swap button was enabled and clickable instead of being disabled with an insufficient balance indicator.
   • Triggering the swap led to a transaction simulation failure.
7. S7

   Max balance populates input correctly

   3 steps, 2 screenshots

   medium✓ pass

   

   

   • Clicked USDC token [redacted], selected USDC, then clicked MAX balance button; the input spinbutton was populated with available balance (reserving gas buffer for native token).
   • Navigated to Swap page where wallet balance was shown as 1.9963 USDC.
   • Opened token [redacted] and selected USDC as input token.
   • Clicked the MAX button; the Input spinbutton populated with available balance (1.9566 USDC, accounting for gas reserve) and the output estimation calculated to 18.5377 ACHS.
8. S8

   Toggle auxiliary UI elements (Gasless and Chart)

   3 steps, 4 screenshots

   medium✓ pass

   

   

   

   

   • Clicked Show price chart: button updated to Hide price chart, TradingView chart and recent trades component rendered, and form inputs were preserved.
   • Clicked Gasless mode toggle: Gasless UI indicator/action ('Enable Permit2 for Gasless') appeared above the swap form without resetting input values.
   • The price chart toggle successfully toggled the chart component on and off.
   • The Gasless mode toggle successfully displayed the Permit2 gasless action/indicator and hid it on toggle off.
   • Neither toggle cleared or disrupted existing swap form inputs or quotes.
9. S9

   Add Liquidity missing input validation

   3 steps, 2 screenshots

   medium✓ pass

   

   

   • Navigated to /add-liquidity; the Add Liquidity button is initially disabled.
   • With Token A set to 0.5 USDC and Token B unselected, the Add Liquidity button is disabled.
   • Navigated to /add-liquidity on AchSwap.
   • Selected Token A (USDC) and entered an amount of 0.5.
   • Left Token B unselected / empty.
   • Observed that the 'Add Liquidity' button is disabled, correctly preventing form submission when required pair data is incomplete.
10. S10

    Navigation link integrity

    5 steps, 5 screenshots

    low✓ pass

    

    

    

    

    

    • Navigated to /add-liquidity via Liquidity link and verified the Add Liquidity form rendered correctly.
    • Navigated to /remove-liquidity via Remove link and verified the page rendered properly.
    • Navigated to /bridge via Bridge link and verified the Bridge form rendered with CCTP options.
    • Navigated back to / via Swap link and verified the swap interface rendered with active balances.
    • Navigated across all core links in the header navigation: Liquidity (/add-liquidity), Remove (/remove-liquidity), Bridge (/bridge), and Swap (/); all URLs updated correctly without full-page crashes or 404 errors.
    • Each route rendered its corresponding view and interactive forms correctly.
11. S11

    Swap zero input validation

    2 steps, 3 screenshots

    low✓ pass

    

    

    

    • Entered 0 into the From amount spinbutton; the Swap button remained disabled.
    • When 0 is entered, the Swap button is disabled, preventing zero-value swap execution.
    • Navigated to Swap page at / where the Swap button was initially disabled.
    • Entered 0 into the token [redacted] spinbutton; the Swap button remained disabled.
    • Verified that entering a valid amount (0.1) activates the Swap button, and returning the input to 0 disables it again.
12. S12

    Remove Liquidity disabled on 0%

    3 steps, 2 screenshots

    low⊘ blocked

    

    

    • Navigated to /remove-liquidity.
    • The page loaded with tabs for V2, V3, and V4 liquidity.
    • No LP positions were available for the connected test wallet across V2, V3, or V4, preventing step 2 (Select a valid LP Position) from being executed.

Findings that survived the Critic's audit. Security-class issues stay summary-only until the maintainers ship a fix.

highconfirmed ✓functionalF1 · S6

Swap submission button remains enabled when input amount exceeds wallet balance

When entering an input amount of 100 USDC which exceeds the current wallet balance of 1.9963 USDC, the 'Swap' button becomes active instead of indicating an insufficient balance or becoming disabled.

Expected

The Swap button should be disabled and display text indicating insufficient balance (e.g. 'Insufficient USDC balance'), preventing submission of an amount exceeding wallet balance.

Actual

The Swap button becomes active with the label 'Swap', allowing the user to click it and trigger a failing transaction that results in a 'Simulation Failed' error.

Repro · 4 steps

1. Navigate to Swap page (/)
2. Ensure USDC is selected as the input token (wallet balance ~1.9963 USDC)
3. Enter 100 in the input amount spinbutton
4. Observe the Swap button state and text

S6-4.pngS6-6.pngS6-8.png

mediumwithdrawnfunctionalF2 · S7

MAX button incorrectly deducts native gas reserve from ERC-20 balance

Surfaced by the audit of S7, which the Tester passed, and reproduced live: Clicked the 'MAX' button while USDC (an ERC-20 token) was selected as input. The input field was populated with 1.9566 instead of the full available balance of 1.9963, showing that a native gas reserve was incorrectly deducted from the ERC-20 token [redacted]

Expected

The MAX button should populate the input with the full available balance of the ERC-20 token (1.9963 USDC).

Actual

The MAX button populates a reduced amount (1.9566 USDC), incorrectly applying native token gas reservation logic to an ERC-20 token.

Repro · 3 steps

1. Navigate to the Swap page.
2. Select an ERC-20 token (USDC) as the input.
3. Click the MAX balance button.

critic-M1-1.png