QA report: external/oneliq.xyz at hosted
Wallet connection fails on the trade page where the network defaults to Arc Mainnet, leaving core swap and bridge transactions unverified.
Testing on oneliq.xyz evaluated twelve scenarios covering wallet connection, input validation, swap and bridge mechanics, theme switching, and rate limit handling. Six scenarios passed, confirming that basic swap input validation, theme toggling, and history views operate as expected.
A single high-severity functional issue was confirmed during wallet connection testing. The trade page defaults to Arc Mainnet rather than Arc Testnet, and selecting Connect Wallet does not trigger a functional connection interface.
Five scenarios could not be completed because the headless test environment lacked an injected Web3 wallet provider and encountered pointer-event actionability timeouts on the trade page controls. Core transaction workflows—including swap execution, network switch rejection, native gas reservation, and bridge recipient address handling—remain untested.
Run summary
| Metric | Count |
|---|
| Scenarios executed | 12 |
| Passed | 6 |
| Failed | 1 |
| Blocked | 5 |
| Findings raised | 1 |
| Issues after the audit | 1 |
| Withdrawn by the audit | 0 |
| Critical / high / medium / low | 0 / 1 / 0 / 0 |
Target: https://oneliq.xyz/ · Testing level: deep_feature · Stack: unknown
Issues
High severity
F1 · Trade page defaults to Arc Mainnet instead of Arc Testnet and Connect Wallet fails to connect
Severity: high · Type: functional · Verdict: confirmed · Scenario: S1
I navigated to /trade and observed that the network indicator defaults to 'Arc Mainnet ▾'. Clicking the 'Connect Wallet' buttons in the sidebar and main view failed to display any wallet connection interface or modal.
Expected: The wallet connects successfully and the UI reflects that the active network is Arc testnet.
Actual: The network indicator shows 'Arc Mainnet ▾' by default, and clicking 'Connect Wallet' does not connect or display a functioning connection interface.
Steps to reproduce:
- Navigate to https://oneliq.xyz/trade
- Observe the network indicator in the navigation sidebar
- Click on the 'Connect Wallet' button
Evidence: screenshots/S1-2.png, screenshots/S1-7.png
Scenario results
| Scenario | Priority | Result | Issues |
|---|
| S1 Connect wallet and verify default network | high | fail | F1 |
| S2 Execute a successful USDC swap | high | blocked (Pointer-event actionability timeouts on /trade controls and absence of an injected Web3 wallet provider in headless browser prevented connecting a wallet and executing on-chain swaps.) | none |
| S3 Verify swap transaction in history | high | pass | none |
| S4 Handle rejected network switch gracefully | medium | blocked (No injected web3 wallet provider was available in the headless browser environment to trigger and simulate a network switch rejection.) | none |
| S5 Validate empty swap amount | medium | pass | none |
| S6 Validate zero or negative swap amount | medium | pass | none |
| S7 Validate non-numeric swap amount | medium | pass | none |
| S8 Enforce native USDC gas reservation | medium | blocked (Unable to connect an active Web3 wallet to verify gas reservation behavior with total available balance.) | none |
| S9 Validate empty recipient for bridging | medium | blocked (Interactive buttons on the trade page could not receive click events within the execution turn budget.) | none |
| S10 Validate malformed bridge recipient address | medium | blocked (Execution could not submit the swap & bridge form without an active Web3 wallet connection provider.) | none |
| S11 Toggle and observe UI theme | low | pass | none |
| S12 Graceful degradation on rate limits | low | pass | none |
The audit
The Critic reviewed 1 finding and re-verified 2 of them live in the browser, replaying the reported steps on a fresh page.
- Nearly half the scenarios were blocked because the test harness lacked a Web3 wallet provider, representing a critical gap in testing the core swap functionality.
- A 429 Too Many Requests error repeatedly appeared in the console across multiple scenarios but was ignored.
- A possible defect in S5 ("Rate limit (429) error encountered on trade page") was not promoted: the live replay came back inconclusive.
What to fix first
- Fix F1 to ensure the trade page defaults to the correct network and reliably initiates the wallet connection interface.
Coverage and caveats
In scope: Trade (Swap & Bridge) primary execution flow; Form validation for Amount and Recipient fields; Network switching and wallet boundary constraints; Transaction receipt history reflection.
Not covered: Unified Balance and Batch Pay (outside chosen deep feature area); Oneliq AI Agent (outside chosen deep feature area); Portal daily check-in (outside chosen deep feature area).
- Test wallet holds sufficient test USDC on Arc testnet to perform swap and bridge actions.
- The 429 console error from the intake AppMap can be reproduced by rapid UI interactions.
- Dropdowns for token and chain selection follow standard HTML/UI interactive patterns.
- S2 could not be executed: Pointer-event actionability timeouts on /trade controls and absence of an injected Web3 wallet provider in headless browser prevented connecting a wallet and executing on-chain swaps..
- S4 could not be executed: No injected web3 wallet provider was available in the headless browser environment to trigger and simulate a network switch rejection..
- S8 could not be executed: Unable to connect an active Web3 wallet to verify gas reservation behavior with total available balance..
- S9 could not be executed: Interactive buttons on the trade page could not receive click events within the execution turn budget..
- S10 could not be executed: Execution could not submit the swap & bridge form without an active Web3 wallet connection provider..
By the numbers
| Metric | Value |
|---|
| Scenarios | 6 passed, 1 failed, 5 blocked of 12 (42 planned steps) |
| Browser actions | 252 (65 clicks, 30 inputs, 40 navigations, 117 snapshots) |
| Screenshots | 25 (4 explore, 20 scenario, 1 critic), 20 captioned |
| Coverage | 10 pages, 3 forms, 4 flows, 1 console errors |
| Audit | 1 findings, 2 re-verified live, 1 confirmed, 0 promoted, 0 withdrawn |
| Model calls | 222 |
| Tokens | 1,180,582 input, 11,210 output, 21,375 thinking |
| Time | 22 min |
| Wallet | 0 transactions, 0 signatures, 0 refusals on chain 5042002 |
| Stage | Calls | Input | Output | Thinking | Seconds |
|---|
| explore | 25 | 158,691 | 3,952 | 863 | 152 |
| plan | 1 | 3,996 | 2,095 | 4,074 | 47 |
| test | 180 | 960,078 | 4,388 | 12,358 | 995 |
| critique | 15 | 56,221 | 539 | 3,604 | 103 |
| report | 1 | 1,596 | 236 | 476 | 7 |
