Suiet Wallet Kit example

No confirmed application defects. Wallet connection could not be exercised in this sandbox.

Testing exercised the core wallet connection workflows, status persistence, permission handling, and extension error flows across five scenarios. Three scenarios passed and two failed.

Connection attempts consistently failed to update the wallet status from disconnected or populate account public keys and wallet details. The page's own console error names the exact cause: "[SUIET_WALLET]: You need to install Suiet Extension from Chrome Store firstly!" This reference app is wired to the real Suiet browser extension global rather than to generic Wallet Standard discovery, so our Node-signed injected test wallet, which holds no browser extension, was never going to connect here regardless of chain or wallet naming. All three related findings were withdrawn as one environment limitation after this hand review.

Basic error handling and static fallback behavior functioned correctly without crashing when the wallet extension was absent. This app's wallet-dependent flows remain untested rather than confirmed broken, since they require an extension this sandbox does not and should not install.

Target: https://wallet-adapter-example.suiet.app/ · Testing level: deep_feature · Stack: unknown

No issues survived the audit.

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.

• Wallet status remains disconnected after clicking connect, sandbox has no Suiet browser extension (S1, high): I selected 'Suiet' from the dropdown and clicked the 'connect' button. The 'current wallet' changed to 'Suiet', but the 'wallet status' remained 'disconnected', and 'wallet accounts' remained empty. The page's own console error names the cause directly: "[SUIET_WALLET]: You need to install Suiet Extension from Chrome Store firstly!". This example app is wired to the real Suiet browser extension global, not to generic Wallet Standard discovery, so our Node-signed injected wallet (no browser extension) was never going to connect here. wallet-log.json for this run shows 0 reads and no signing. This is a sandbox environment limitation, not an app defect.
• Wallet connection fails to update status and populate account fields on connect, sandbox has no Suiet browser extension (S2, high): I clicked the 'connect' button twice and the wallet status remained 'disconnected', wallet accounts remained empty '[]', and the account public key remained blank. Same root cause as F1: the page's console error names the missing Suiet browser extension directly, this example app does not use generic Wallet Standard discovery. This is a sandbox environment limitation, not an app defect.
• Application requires specific Chrome extension not available in test sandbox (S3, high): Surfaced by the audit of S3, which the Tester passed, and reproduced live: I verified on https://wallet-adapter-example.suiet.app/ that clicking the 'connect' or 'Request Permissions' buttons while the Suiet wallet is selected does not initiate a connection. The wallet status remains 'disconnected' and no UI changes occur, confirming the application requires the real Suiet browser extension rather than accepting a generic Wallet Standard wallet. The page reported 2 console errors during the scenario. This is the same environment limitation as F1 and F2, not an independent defect.

The Critic reviewed 2 findings and ran 3 live replays in the browser, each on a fresh page.

• F1 and F2 are duplicate findings of a connection failure entirely due to the sandbox not having the specific Suiet browser extension installed.
• Scenarios S3 and S5 masked the same underlying environment limitation by passing the app for simply not crashing when the wallet extension was absent.
• Hand correction, 2026-09-26: F1, F2 and F3 were all re-classified as one environment limitation and withdrawn. The page's own console error names the missing Suiet browser extension directly ("[SUIET_WALLET]: You need to install Suiet Extension from Chrome Store firstly!"), this reference app requires that real extension rather than using generic Wallet Standard discovery, so the injected test wallet was never going to connect here regardless of naming or chain.

No confirmed issue to fix. Every finding from this run traces to one environment limitation, the sandbox does not hold the real Suiet browser extension this specific example app requires, not to a defect in the application.

In scope: Wallet connection flow using the provided test wallet; Rendering of wallet state fields upon connection; Wallet permission requests via the UI; Application resilience to uninstalled wallet selections.

Not covered: Transactions or message signing (not mapped in the available UI); Creating new wallet accounts (external to the application); Testing specific third-party wallet extensions besides the injected test wallet.

• The injected test wallet automatically approves connection and permission requests when prompted by the application.
• The test wallet is available as an option in the wallet selection dropdown or acts as the default when 'connect' is clicked.
• There is no explicit disconnect button mapped; state reset relies on page reload or test isolation.