QA report: external/loomonarc.xyz at hosted
No confirmed defects were identified during testing, with all navigation and informational routes functioning as expected.
Testing covered primary navigation flows across the site, including the bridge entry point via hero call-to-action, the Launchpads directory, network guides for Solana and Ethereum to Arc, security model documentation, and general page resilience under console errors.
A single finding regarding silent failure during wallet network switch rejection was raised during testing, but the audit withdrew this finding because the automated test environment lacked an injected Web3 provider rather than encountering an application defect. Consequently, zero confirmed issues remain from the run.
The application successfully delivers its core informational and navigation journeys. Full end-to-end evaluation of wallet connectivity and bridge execution will require testing in an environment equipped with an active Web3 wallet provider.
Run summary
| Metric | Count |
|---|
| Scenarios executed | 7 |
| Passed | 6 |
| Failed | 1 |
| Blocked | 0 |
| Findings raised | 1 |
| Issues after the audit | 0 |
| Withdrawn by the audit | 1 |
| Critical / high / medium / low | 0 / 0 / 0 / 0 |
Target: https://loomonarc.xyz/ · Testing level: deep_feature · Stack: unknown
Issues
No issues survived the audit.
Withdrawn findings
The Critic re-examined these claims and found the evidence did not support them. They are kept here rather than deleted.
- Bridge UI fails silently without user feedback upon wallet network switch rejection (S1, medium): The tester claims the UI fails silently after a 'wallet connection / network switch to Base is rejected', but there is no evidence the harness actually initiated or rejected a wallet connection. Clicking 'Connect wallet' without an injected wallet often fails silently, which is an environment limitation rather than a graceful handling defect. The page reported 2 console errors during the scenario.
Scenario results
| Scenario | Priority | Result | Issues |
|---|
| S1 Graceful handling of network switch rejection | high | fail | none |
| S2 Primary navigation to Bridge via hero CTA | medium | pass | none |
| S3 Navigation to Launchpads directory | medium | pass | none |
| S4 Navigation to Solana to Arc guide | medium | pass | none |
| S5 Navigation to Ethereum to Arc guide | medium | pass | none |
| S6 Navigation to Security model documentation | medium | pass | none |
| S7 Page load resilience with console errors | low | pass | none |
The audit
The Critic reviewed 1 finding and re-verified 1 of them live in the browser, replaying the reported steps on a fresh page.
- The tester assumed a wallet network switch was explicitly rejected in S1, but the harness likely just clicked a button that does nothing without an injected Web3 provider.
- A pervasive JavaScript TypeError occurs across almost all scenarios and routes, which the tester consistently observed but ignored.
- A possible defect in S3 ("Uncaught TypeError on page load") was not promoted: the live replay came back inconclusive.
Coverage and caveats
In scope: Wallet connection and network switch failure handling on the bridge page; Navigation to all informational guides and directories; Application resilience in the presence of known console errors.
Not covered: End-to-end USDC bridge transaction: The test wallet strictly enforces the Arc testnet and refuses the required network switch to Base, preventing the transaction from being initiated.; Form validation for bridge amounts: The transfer form and input fields require a successful wallet connection on Base to render, which is blocked by the test wallet..
- The test wallet connects automatically but rejects the network switch to Base, allowing us to test only the error handling or 'wrong network' state of the bridge feature.
- The 'Cannot read properties of null (reading 'addEventListener')' and 403 console errors do not completely break client-side routing.
By the numbers
| Metric | Value |
|---|
| Scenarios | 6 passed, 1 failed, 0 blocked of 7 (15 planned steps) |
| Browser actions | 65 (12 clicks, 0 inputs, 20 navigations, 33 snapshots) |
| Screenshots | 20 (4 explore, 15 scenario, 1 critic), 15 captioned |
| Coverage | 6 pages, 1 forms, 4 flows, 2 console errors |
| Audit | 1 findings, 1 re-verified live, 0 confirmed, 0 promoted, 1 withdrawn |
| Model calls | 73 |
| Tokens | 352,903 input, 5,362 output, 13,807 thinking |
| Time | 6 min |
| Wallet | 0 transactions, 0 signatures, 0 refusals on chain 5042002 |
| Stage | Calls | Input | Output | Thinking | Seconds |
|---|
| explore | 17 | 98,058 | 1,871 | 1,477 | 70 |
| plan | 1 | 3,693 | 1,177 | 3,101 | 35 |
| test | 45 | 190,703 | 1,615 | 2,376 | 173 |
| critique | 9 | 59,184 | 510 | 6,436 | 83 |
| report | 1 | 1,265 | 189 | 417 | 6 |
