WarcGarage

Core token swapping and bridging workflows are non-functional due to silent transaction failures.

Testing covered the Swap Hub interface across 12 scenarios evaluating token exchange execution, cross-chain bridge actions, wallet asset balance rendering, and form input validation. Four scenarios passed, five failed, and three were blocked due to underlying execution failures and missing interface elements.

The primary interactive features on the Swap Hub fail silently without executing transactions or presenting user feedback. The swap button does not trigger transactions or validate pay amounts against available balances. Additionally, the bridge tool cannot initiate outbound transfers from Arc Testnet and silently ignores actions initiated on unsupported source networks.

A finding that the Assets tab and balance card fail to render the connected wallet's USDC balance was withdrawn after two re-checks. The Swap Hub's own "Circle Wallet" status card and USDC balance track a separate, Circle-hosted wallet session, not the generic EVM wallet that does connect and shows its address in the top navigation. Nothing in the app offers a way to connect that Circle Wallet session with a generic Wallet Standard or EIP-1193 wallet, so the DeepQA test wallet was never going to be able to populate it. Environment limitation, not an app defect.

Testing could not evaluate slippage tolerance bounds, gas balance reservations, or persistent swap history because slippage controls are absent from the interface and transactions cannot be executed to generate history records.

Target: https://warcgarage.xyz · Testing level: deep_feature · Stack: unknown

Severity: high · Type: functional · Verdict: confirmed · Scenario: S2

I navigated to the Swap Hub at /swap-hub, selected ETH as the pay token, entered an amount of 5, and clicked the '⚡ SWAP TO USDC' button. Nothing happened when I clicked the button; no confirmation, receipt, or transaction feedback was displayed, confirming the reported issue. The page reported 2 console errors during the scenario.

Expected: The token swap initiates, showing a transaction confirmation, progress, or success receipt.

Actual: Clicking the '⚡ SWAP TO USDC' button does nothing; no confirmation, receipt, or transaction feedback is displayed.

Steps to reproduce:

1. Navigate to https://warcgarage.xyz/swap-hub
2. Select an asset (such as ETH or USDT) from the pay token dropdown
3. Enter a valid amount (e.g. 5) in the Pay Amount field
4. Click the '⚡ SWAP TO USDC' button

Evidence: screenshots/S2-2.png, screenshots/S2-5.png, screenshots/S2-13.png

Severity: high · Type: functional · Verdict: confirmed · Scenario: S4

The evidence confirms the application silently ignores the bridge action without prompting a network switch or displaying an error. The live replay was inconclusive: The replay ran out of tool calls before it reached the reported state. The page reported 2 console errors during the scenario.

Expected: The application should attempt network switch or display a clear error message indicating unsupported network/wallet rejection.

Actual: The application ignores the interaction silently without displaying any error, modal, or feedback to the user.

Steps to reproduce:

1. Navigate to https://warcgarage.xyz/swap-hub
2. Click the BRIDGE tab
3. Select a non-Arc source network (e.g., Polygon)
4. Enter an amount to bridge (e.g., 10)
5. Click 'BRIDGE TO ARC TESTNET'

Evidence: screenshots/S4-2.png, screenshots/S4-4.png, screenshots/S4-9.png, screenshots/S4-11.png

Severity: high · Type: functional · Verdict: confirmed · Scenario: S5

Navigated to the Swap Hub and clicked the BRIDGE tab. The Source Network dropdown only lists Ethereum, Polygon, Arbitrum, Base, and Solana, and does not include Arc Testnet. The Destination Network dropdown is fixed/disabled to Arc Testnet. Therefore, outbound bridging from Arc Testnet cannot be selected or initiated. The page reported 2 console errors during the scenario.

Expected: The user should be able to select Arc Testnet as the source network and another supported chain as the destination to initiate an outbound bridge transaction.

Actual: Source Network only provides external chains (Ethereum, Polygon, Arbitrum, Base, Solana) and Destination Network is fixed/disabled to Arc Testnet, completely preventing outbound bridging from Arc Testnet.

Steps to reproduce:

1. Navigate to https://warcgarage.xyz/swap-hub
2. Click the BRIDGE tab
3. Inspect the Source Network and Destination Network dropdowns

Evidence: screenshots/S5-4.png, screenshots/S5-8.png

Severity: medium · Type: functional · Verdict: confirmed · Scenario: S6

The evidence shows the application fails to validate the pay amount against the connected wallet's zero balance, leaving the submit button enabled. The page reported 2 console errors during the scenario.

Expected: The swap submission button should be disabled or an 'Insufficient Balance' message should be prominently displayed.

Actual: The '⚡ SWAP TO USDC' button remains active and clickable with no insufficient balance error or warning displayed.

Steps to reproduce:

1. Navigate to https://warcgarage.xyz/swap-hub.
2. Enter an amount (e.g., 5000) in the Pay Amount field that exceeds the connected wallet balance.
3. Observe the swap submission button and form state.

Evidence: screenshots/S6-2.png

These failures came from the test environment, not from the application: a credential the sandbox does not hold, a demo nobody may write to, a resource it cannot reach. They are not counted as issues. They record what this run could not exercise.

• Swap Hub Assets tab and balance card fail to render connected wallet USDC balance and token holdings (S8, high): Navigated to /swap-hub and clicked the ASSETS tab. I observed that despite a wallet being connected in the header (0x1815...2c27), the USDC BALANCE card showed '—'. Additionally, the ASSETS tab displayed static contract addresses instead of token holdings. The page reported 2 console errors during the scenario. Hand and targeted-replay re-check, 2026-09-27, twice (once by hand with no wallet, once via a targeted Docker replay with the Arc test wallet, --wallet qa-1): both confirm the generic wallet does connect, its address shows in the top nav chip, but the Swap Hub's own 'Circle Wallet' status card and USDC balance never depend on that generic connection. No 'Circle Wallet' connect trigger exists anywhere in the app's own interactive elements (checked the AppMap), the card appears to be a read-only status tied to Circle's own hosted wallet product, a separate flow our generic EIP-1193 test wallet cannot satisfy. Environment limitation: the app's wallet flow does not offer the DeepQA test wallet a path to the specific Circle Wallet session its balance UI depends on.

The Critic reviewed 5 findings and re-verified 5 of them live in the browser, replaying the reported steps on a fresh page.

• In S12, the tester interpreted the silent failure of the bridge button as successful validation of an empty field, contradicting S4 where the exact same silent behavior was correctly identified as a defect.
• The silent failures of the action buttons across multiple scenarios may be directly related to the 'Not connected' Circle Wallet state noted in S9 or the uncaught JavaScript errors present on load.
• A possible defect in S1 ("Console errors occur on Swap Hub page load") was not promoted: the live replay came back not-reproduced.
• Hand correction, 2026-09-27: F5 was re-classified as an environment limitation and withdrawn after two re-checks (a hand check with no wallet, and a targeted Docker replay with --wallet qa-1) both showed the generic wallet connects at the page level while the app's distinct 'Circle Wallet' status stays unconnected with no connect trigger of its own.

1. Resolve silent execution failures on the token swap button to trigger transactions and provide visible user feedback (F1).
2. Enable outbound transfer routing from Arc Testnet on the Swap Hub Bridge interface (F3).
3. Provide clear error messaging and user feedback when attempting to bridge from unsupported networks (F2).
4. Validate input amounts against available balances and disable the swap action when funds are insufficient (F4).

In scope: Swap Hub DEX token swaps; Swap Hub cross-chain bridging; Native gas token reservation constraints; Network switch refusal handling; Swap input validation and slippage bounds; Assets and History navigation tabs.

Not covered: NFT Minting (focusing solely on Swap Hub deep dive); 3D Race Arena (focusing solely on Swap Hub deep dive); Predictions Hub (focusing solely on Swap Hub deep dive); Web3 Vehicle Bridge (focusing solely on Swap Hub deep dive); Verify X Identity (focusing solely on Swap Hub deep dive); Holder Profile Search (focusing solely on Swap Hub deep dive).

• A MAX shortcut exists on or near the Pay Amount field as described in the intake.
• Wallet connection occurs automatically when Web3 transactions or network switches are requested.
• Sufficient testnet liquidity exists to process small USDC swaps successfully.
• The deep_feature test isolates the Swap Hub strictly to exhaust its form fields and latent network constraints.
• S3 could not be executed: The Swap Hub page only supports swapping other assets (USDT, ETH, MATIC, ARC) TO USDC, does not provide USDC as a selectable pay token, and does not have a MAX balance shortcut button..
• S9 could not be executed: Unable to execute token [redacted] on the Swap Hub because the Circle Wallet integration is disconnected and swapping does not trigger transaction execution..
• S11 could not be executed: The Slippage Tolerance field is not present on https://warcgarage.xyz/swap-hub or in any of its tabs..