Ambire

The wallet requires explicit user confirmation for all tested privileged RPC methods, as each request was rejected with code 4001 after the tester declined the prompt.

The wallet rejected eth_decrypt, eth_getEncryptionPublicKey, eth_signTypedData_v4, personal_sign, and eth_sendTransaction with code 4001, and eth_accounts returned an empty list, leaking no account information before connection approval.

The wallet correctly prompts for unlock for all tested RPC requests (wallet_addEthereumChain, wallet_watchAsset, eth_decrypt, eth_getEncryptionPublicKey, eth_signTypedData_v4, personal_sign, eth_sendTransaction) when locked, and none of the requests are processed; no data is returned while locked.

The wallet rejects the signing request because the EIP-712 chainId does not match the connected network.

The wallet rejects `eth_sign` requests by default, displaying an error that it does not support the method.

The wallet warns about the SIWE domain mismatch. The sign-in request shows the dApp origin as Localhost while the SIWE message domain is opensea.io, and a Deceptive app request warning states the app does not match the domain in the message and may be a phishing attempt.

The wallet's settings menu does not include token approval management, nor does it link to a third-party app or site for listing or revoking token approvals.

The wallet lists connected dApps in the Explore Connected view and the Manage app screen shows a Disconnect action for Localhost. After revoking the testing dApp, subsequent RPC probes show eth_accounts and wallet_getPermissions resolved with empty data, confirming access is revoked.

The wallet blocks switching to non-approved networks by returning an 'Unrecognized chain ID' error, requiring the chain to be added first; the switch is not performed without confirmation.

The wallet displays expected inputs and outputs before signing for both liquidity provision (e.g., -0.01 POL and Uniswap V3 Position NFT) and swap (e.g., -0.01 POL and +0.00089 USDC.E), satisfying the acceptance criteria.

The wallet clearly identifies the request as an ERC-20 Approve and shows the token symbol USDC.E, the spender address 0xE592427A0AEce92De3Edee1F18E0157C05861564 (visible in the parsed data), and the approved amount as unlimited (max uint256).

The wallet renders large personal_sign and EIP-712 signing requests with scrollable content and no truncation; the EIP-712 dialog shows the EIP712Domain including verifyingContract 0x0000000000000068F116a894984e2DB1123eB395 in Raw view.

The wallet renders structured, human-readable EIP-712 signing details, including spender, spending amount, and expiry, with an option to view raw JSON.

The wallet blocks transactions to the invalid-checksum address 0x6603E7c1F985D0E75C9C326e86E6C7E8a1898577 in both cases: manual send shows "Invalid checksum. Verify the address and try again." and the dApp request is rejected with "A call has invalid 'to' field".

The wallet's sign button was observed enabled and working after scrolling for both personal_sign and eth_signTypedData.

Addresses are not clickable links to a block explorer in the transaction preview screen. However, the transaction history screen provides an "Open explorer" button to view transaction details in a block explorer.

The wallet requires the extension password to be confirmed before revealing the recovery phrase.

The wallet includes a manual lock control. The Menu shows a 'Lock Wallet' option with a lock icon at the bottom of the menu.

The wallet auto-lock device setting is configured to Never, and the menu shows Auto lock: Never, so the wallet does not auto-lock within 20 minutes of inactivity.

The wallet allows trivial passwords to be set: 11111111, 12345678 and password are shown with ‘Passwords match’ and the Confirm button enabled, indicating acceptance of weak/trivial credentials.

The wallet reveals the recovery phrase without displaying a clear warning about the risks of sharing the secret; no risk warning is shown on the Manage recovery phrase / reveal screen.

The wallet allows the recovery phrase to be copied to the clipboard with a ‘Recovery phrase copied to clipboard!’ confirmation and no warning about clipboard risks, no time-limited exposure, and no evidence of clipboard clearing.

The wallet warns about the poisoned lookalike address 0x8730...Da54 when entered manually, but does not warn when the same address is supplied via a dApp, and does not warn or block for the known malicious address 0x5923...9de9 in either manual entry or via dApp.

The wallet warns the user about potential danger when attempting to connect to known phishing sites, displaying a 'Potential danger!' message and a 'Danger' badge.

The wallet visibly distinguishes verified dApps from unknown ones: Uniswap and SushiSwap show a 'Verified app' badge and 'Passed' security check, while the Netlify dApp shows a warning and requires 'Hold to continue anyway'.

The wallet shows “First time sending to this address.” for the fresh address 0x9eb91Fbc0291180088a7ff279FA7d35d26a42516 when sending directly through the wallet UI, but no unknown-address warning or indicator is displayed in the dApp transaction builder for the same address.

The wallet displays the full dApp origin URL 'flagship-web3-v1-336a757b5b637a684207a3.webflow.io' without truncation in the connection dialog.

Spam Tokens and NFTs are hidden by default in the wallet.

The connection dialog discloses that the app can see your addresses and propose transactions.