Ambire

The wallet implements Wallet Connect through the browser and it requires user confirmation before processing each request to the following RPC endpoints: wallet_addEthereumChain, wallet_watchAsset, eth_decrypt, eth_getEncryptionPublicKey, eth_signTypedData*, personal_sign, eth_sendTransaction.

The wallet has an embedded browser and it requires user confirmation before processing each DApp request to the following RPC endpoints: wallet_addEthereumChain, wallet_watchAsset, eth_decrypt, eth_getEncryptionPublicKey, eth_signTypedData*, personal_sign, eth_sendTransaction.

The wallet in the embedded browser uses WalletConnect. When locked, it asks users to unlock before processing requests. It displays messages indicating pending approval requests. This was tested using the RUN AUTH function with a timer in the dApp to test a request after exiting the application.

The wallet does not allow signing an EIP-712 object when the chain ID does not match the currently active chain.

The eth_sign method appears to be disabled by default in the wallet.

The wallet does not warn users of a domain or scheme mismatch when signing an EIP-4361 (Sign in With Ethereum - SIWE) message.

Although it does not have the functionality to list dApps, it only allows one connection at a time.

The wallet lacks the functionality to display token approvals.

The wallet requires user confirmation before processing the wallet_switchEthereumChain RPC request from the dApp.

The wallet does not display all the incomes and outcomes of the transaction in either a swap or when adding liquidity to a pool in Uniswap.

The wallet provides the token, token, amount, effect and spender address within an approval transaction preview but not the address of an unknown token.

The wallet displays large messages in a personal sign request in full, without truncation, and it also shows the verifying contract field within an EIP-712 object.

The wallet does not parse EIP-712 objects and instead displays the raw, unparsed data.

The wallet refuses to process transactions when provided with addresses that have invalid checksums (EIP-55), either entered manually or through a dApp.

The wallet requires users to scroll through the entire content of a large message in a personal sign request before allowing them to sign it.

The wallet provides clickable links while querying the wallet history and also to a contract address within an approval transaction preview.

The wallet provides proprietary backup via encrypted JSON file. Standard backup and recovery methods not supported.

The wallet does not feature a manual lock button.

Wallet locks, by default, immediately after moving it to the background or exiting the app. It also locks when the device gets locked.

The wallet allows easy-to-guess six-digit passwords like 111111 and it does not rate-limit failed attempts. It supports biometrics.

The wallet provides proprietary backup via encrypted JSON file. Standard backup and recovery methods not supported.

The wallet provides proprietary backup via encrypted JSON file. Standard backup and recovery methods not supported.

The wallet alerts about connections to known phishing dApps.

The wallet does not prevent or alert users about interactions with known phishing or scam addresses, such as the Tornado Cash attacker.

The wallet connects directly without prompting any connection dialog and does not inform users when they are interacting with well-known, verified URLs.

The wallet warns users when they are not interacting with a previously known or trusted address.

The wallet connects directly without prompting any connection dialog. In the browser, the url of the site appears truncated.

The wallet hides scam or spam tokens and NFTs that are sent to the wallet.

The wallet connects directly without prompting any connection dialog.