TokenPocket

The wallet requires user confirmation to access the RPC endpoints.

The wallet rejects all privileged RPC requests before connection: eth_accounts returns an empty array with code 403, eth_decrypt and eth_getEncryptionPublicKey error with code -32603, and eth_signTypedData_v4, personal_sign, and eth_sendTransaction are rejected with code 4001, with no information leaked.

It requires users to unlock the wallet to process requests from dApp to all the RPC endpoints.

The wallet did not reject the signing request or display a warning about the chainId mismatch. The transaction was signed successfully.

The wallet rejected the `eth_sign` request, returning the error "Error: Not supported eth_sign!"

The wallet does not explicitly warn the user about the domain mismatch between the dApp origin and the SIWE domain. There is only a generic warning about signing.

The wallet provides a way to list existing token approvals and revoke them. The user can access the "Approvals" section, view approval details, and revoke authorizations.

The wallet lists connected dApps, and revoking access prevents further RPC requests from the disconnected dApp.

Chain was changed successfully with no confirmation prompt, without allowing the user to pre-approve networks within the connection dialog.

The wallet does not show expected inputs and outputs for the transaction before signing; it only displays the contract interaction and transaction fee, and in one case shows an estimation failure.

The wallet clearly identifies the approval requests for USDC and WSRT, displaying each token symbol, the spender address (0xE592...), and the approved amount (Unlimited) in the confirmation dialog.

The signing data is visible and scrollable for both personal_sign and eth_signTypedData. However, the verifyingContract is not present in the EIP712Domain.

The wallet renders raw JSON instead of structured, human-readable details for the EIP-712 signature request.

The wallet correctly blocks manual transactions with invalid EIP-55 checksums by showing an 'Invalid address' error. However, for dApp-initiated transactions with an invalid checksum, the wallet proceeds to the confirmation screen without any warning or blocking, allowing the transaction to be signed.

The confirm button is enabled without scrolling to the end of the payload.

Addresses and contract addresses are shown in transaction history and transaction confirmation screens, but they are not clickable links to a block explorer.

Authentication is required before proceeding to display the seed phrase or private key.

The screenshot shows a 'Lock' button in the wallet UI, fulfilling the requirement for a manual lock control.

The auto-lock settings are set to "Never" by default, which does not meet the acceptance criteria for auto-locking within 20 minutes of inactivity.

The password accepted is '11111111'. It is an 8-character trivial password, so it fails the check.

The wallet displays a warning to the user before revealing the secrets, which includes the risks of losing or sharing the seed phrase/private key.

The wallet warns about the risks of copying the recovery phrase to the clipboard and taking screenshots, satisfying the acceptance criteria.

The wallet did not surface any warnings, flags, or blocks when sending to the known malicious address (0x592340957eBC9e4Afb0E9Af221d06fDDFF789de9) or the lookalike poisoned address (0x8730aeb8FE951cfa6e17f82341ECD95C921FDa54), both via dApp and manual UI entry.

The wallet does not block or warn the user against known phishing sites.

The wallet does not feature a verified domain indicator for well-known dApps.

The wallet displays no warning or indicator when sending to an unknown address, both when the address is provided by a dApp and when entered directly in the wallet UI.

The origin URL 'https://flagship-web3-v1-336a757b5b637a684207a3.webflow.io' is displayed in full without any truncation in the connection dialog.

Spam NFTs are displayed by default.

The connection dialog only mentions access to view the user's address. It does not include the ability to view balance and activity or request transaction approvals.