• Metamask doesn’t offer its first phrase to come from the QRcode/Shell (extension). It shows error on mobile - “Looks like you’re trying to scan a QR code, you need to unlock your wallet to be able to use it” - but no unlock possible at his stage.
• I have accidentally touched keycard during passphrase recovery phase and had to repeat the whole process again. Card doesn’t sit firmly in the Shell.
• Swap transaction QR code scan is a bit tricky, because the QR code fluctuates and Shell needs to be held firmly. Swap transaction data to confirm are not very human readable. Some transaction basic info is available. Would be nice to have tx data decoded for popular dapps.

https://sepolia.etherscan.io/tx/0x3cb77a3c446e5e3c8c395e0bf42e3de9b32b9d005faa92f27bd90e8c20808971

https://sepolia.etherscan.io/tx/0x0537b4b3c730a031bf59f8fdbf9532fb20c2cf08987c32f97df428eecd889916

https://sepolia.etherscan.io/tx/0x867cecea1e1e068f2b8585c916132c80d730dbb478bb23e886195ecd63efcc25

https://sepolia.etherscan.io/tx/0x0a47b17d5595aad22eeaeb47c6c9a63c76f9f211bac8c07e40b37e2e45ef4407

https://etherscan.io/tx/0xec1f45abbaeeb12dd33033d9346785ef05b76261c536f96f1bb81ef60ba9cf45 | | | | Metamask | Ethereum multisig (Gnosis Safe transaction) | Ethereum | Passed | - | - | - | - | Passed on CoW**/Ethereum** | Safe Address: https://app.safe.global/home?safe=sep:0x554A896DEc3BCbE53B03e829E1FAafe0bec04B0F

Safe (sepolia)Activate tx: https://sepolia.etherscan.io/tx/0x0b406468b59c23bc83621beabfab25aabf345c2335cf9271fbb0b8170886b519

Send final tx: https://sepolia.etherscan.io/tx/0x59dd19570ba7b8e061ece09c445865758374d7e8cbb1768e132253975d960e07

Safe (Ethereum ctivita tx) https://etherscan.io/tx/0xcba5bfbfd359b420cf2da4d39764c4a30583f4f6d1dc38955c306b08502ccef5

Safe Swap final tx: https://etherscan.io/tx/0x385c9ce374ab6b9914ebac36e95cc5a03c580b566eccf3000773ae653f3699ea | | | | Rabby | Sepolia | Ethereum | Passed | Passed | Passed | Passed | Passed | Passed on Uniswap/Ethereum | - Extension wallet connected as AIrGap Vault using QR code

• iOS wallet imported as Keystone wallet using QR code
• Rabby for desktop had a problem with focus on QR code. It took a while moving Shell around before HW wallet could be added. What is good here, the first address could be from the Shell.

https://sepolia.etherscan.io/tx/0xd6f462b42f02c96c3309e8f7c9074bfaf2f72adb580e835ef6b95d243f804c98

https://sepolia.etherscan.io/tx/0xbfe3ad51040421903efbc8f420631083b089853f177cef2c192b753dfe0fb480

https://sepolia.etherscan.io/tx/0x197493e372526a7a176ff8f3e8f60084dfec6b1a7a3c60bb6190b74d4e35940d

https://sepolia.etherscan.io/tx/0x85701b17ac078221c55439f5cea099cc088621c393b31e8ebe2516958cb3dc12

https://sepolia.etherscan.io/tx/0x54a88fd188fb175893957074049ffdd04384f308eb12129b6c9434d8d7371471

https://etherscan.io/tx/0x533556c4714f75adc6b2c837af0a70d28cd8dd0f6ee3ae5e80be48298b4fefa0 | | | | Blockwallet | Sepolia | Ethereum | Could not scan QR code | - | - | - | - | | They have outage on their own RPC provider: https://mainnet-node.blockwallet.io https://www.notion.so/Keycard-Shell-Test-Results-22b8f96fb65c80faa06fcc195373624b?source=copy_link#2308f96fb65c804a8a9cfe967366a4c8

• Outage resolved after several days. I cannot import Shell’s Keycard using QR code. Image is blurred and won’t get recognized. They have a message in the scan dialogues “blurred image should not affect the QR code recognition”. It looks the opposite is true. | | | | Bluewallet | BTC | Bitcoin | - | Passed* | Passed* | Passed* | Passed* | - | - Watch-only import possible.
• • User has to confirm two warning dialogues in order to send funds | | | | | BTC testnet | Bitcoin Testnet | - | Wallet shows mainnet addresses after import not tb1 testnet addresses | Wallet shows mainnet addresses after import not tb1 testnet addresses | Wallet shows mainnet addresses after import not tb1 testnet addresses | Wallet shows mainnet addresses after import not tb1 testnet addresses | - | - With https://testnet.aranguren.org:50002 and https://mempool.space/testnet | | | | | BTC multisig | Bitcoin Multisig | - | Cannot import the key with QR code | Cannot import the key with QR code | Cannot import the key with QR code | Cannot import the key with QR code | - | - Getting “invalid co-signer data” error during key import | | | | Sparrow | BTC | Bitcoin | - | - | - | - | Passed | - | | | | | | BTC testnet | Bitcoin Testnet | - | - | - | - | Passed | - | - Initially I was not able to get wallet usable after import as testnet wallet. I had to restart entire application in Testnet4.
• It is not possible to display BTC testnet addresses on Shell device.
• QR code to sign transaction cannot be scanned with Shell device when “Show BBQr is toggled” - default. | | | | | BTC multisig | Bitcoin Multisig | - | - | - | - | Passed | - | - No warning when device is signing transaction not intended for it. Sparrow’s UI is confusing enough to let user start multisig signing process without clear order of signers. When all signers use the same software wallet instance - I understand this is not usual scenario. | | | | Specter | BTC | Bitcoin | - | - | - | - | Passed | - | | | | | | BTC testnet | Bitcoin Testnet | - | - | - | - | | - | - Unable to connect to local Bitcoin core testnet installation so far | | | | | BTC multisig | Bitcoin Multisig | - | - | - | - | Passed | - | - I had problems with creating multisig with non hardware wallet. Tested accidentally with having one Shell/Keycard as two different signers, which let to locking Bitcoin in the wallet. Reached to Specter support. | | | | Nunchuk | BTC | Bitcoin | - | Passed | Passed | Passed | Passed | - | - Shell imported as Generic Airgap | | | | | BTC testnet | Bitcoin Testnet | - | Passed | Passed | Passed | Passed | - | - Intuitive and clean UX | | | | | BTC multisig | Bitcoin Multisig | - | Passed | Passed | Passed | Passed | - | | | | | Zeus | BTC | Bitcoin | - | Import failed with “Error: Value provided was not a valid Bitcoin address or Ligthning invoice” | Import failed with “Error: Value provided was not a valid Bitcoin address or Ligthning invoice” | Import failed with “Error: Value provided was not a valid Bitcoin address or Ligthning invoice” | Import failed with “Error: closed” | - | - Import external account is currently an experimental feature (v0.11.2). | | | | | BTC testnet | Bitcoin Testnet | - | Import failed with “Error: Value provided was not a valid Bitcoin address or Ligthning invoice” | Import failed with “Error: Value provided was not a valid Bitcoin address or Ligthning invoice” | Import failed with “Error: Value provided was not a valid Bitcoin address or Ligthning invoice” | Import failed with “Error: closed” | - | | | | | | BTC multisig | Bitcoin Multisig | - | Import failed with “Error: Value provided was not a valid Bitcoin address or Ligthning invoice” | Import failed with “Error: Value provided was not a valid Bitcoin address or Ligthning invoice” | Import failed with “Error: Value provided was not a valid Bitcoin address or Ligthning invoice” | Import failed with “Error: closed” | - | | | | | Bitcoin Safe | BTC | Bitcoin | - | - | - | - | Shell error: Malformed data or unsupported format. | - | - https://github.com/andreasgriffin/bitcoin-safe
• I was able to import keycard with QR code
• Error reported by Shell during Send tx signing using QR/UR code. Other variants of QR code didn’t work as well. https://github.com/keycard-tech/keycard-shell/issues/145 | | | | | BTC testnet | Bitcoin Testnet | - | - | - | - | Import failed | - | - Unknown error displayed in Bitcoin Safe during import to Testnet4. Error: “Expected Network Network.TESTNET, but got Mainnet” happened when I tried to import to Testnet. | | | | | (no multisig) | Bitcoin Multisig | - | - | - | - | Shell error: Malformed data or unsupported format. | - | | | | | Babylon | BTC | Bitcoin | - | - | - | - | - | Passed* | - Connected together with Kepler wallet
• Cannot get stakable balance > 0. Response from support “There is a 0.005 BTC needed as slashing guarantee which in turn will return to your wallet after staking, but the stake needs to be able to cover that at least”.
• • ideally to retest with larger sum >0.005 BTC | | | | Multichain Wallets | | | | | | | | | | | | | | | | | | | | | | | | | | Xverse | Multichain | Multichain | - | - | - | - | - | - | - No QR wallet import available. USB Keystone import available for browser extension, but not supported by Shell. | | | | ImToken | Ethereum | Ethereum | - | Passed | No QR import* | Passed | Passed | Passed on in-App Uniswap/Ethereum | - Shell not supported for Bitcoin
• “Keycard Shell” label recognized nicely by ImToken
• Shell is market “watch-only” yet Send transactions possible
• • ImToken app very slow in Android 14 emulator | | | | Okx | Multichain | Multichain | Import failed - cannot read QR code | Shell is unable to Sign BTC Send transaction* | No accounts shown during import on account select page. | No accounts shown during import on account select page. | Shell is unable to Sign BTC Send transaction* | - | - Service not available in EEA region. VPN set to Taiwan, Chrome browser settings set to GMT+8.
• transaction QR code is using dots instead of squares - these QR codes are non-compliant. | | | | Backpack | Ethereum | Ethereum | Import failed | Import failed | - | - | - | - | - Shell import as Keystone - failed. Blurred image. | | | | Backpack | Ethereum | Multichain | - | - | - | Import Failed on importing addresses (Pixel 9a, Android 15) | - | - | - * The Packpack app doesn’t run in Android 16 emulator | | | | Bitget | Multichain | Multichain | No import for HW wallets | Passed (Ethereum + Bitcoin) | Passed (Ethereum + Bitcoin)* | Passed (Ethereum + Bitcoin) | Bitget app is not asking for camera permissions | App message: “The hardware wallet does not support this feature.” | - Full multichain support with HW wallets
• Bitget app will report positive balance when one of the addresses holds Bitcoin value, but it won’t allow to send Bitcoin out if the address is not the same with the imported address - it only imports one of the many Keycard contains.
• • Bitget app very slow in Android 14 emulator | | | | former Bitkeep ⇒ Bitget | - | - | - | - | - | - | - | - | | | | | Core wallet | Avalanche | Multichain | Send transaction signing failed* | No option to import hardware wallet | No option to import hardware wallet | No option to import hardware wallet | No option to import hardware wallet | - | - * Send transaction failed with Core wallet response “Transaction failed” after reading QR code from Shell device | | | | Unisat | BTC | Bitcoin | Passed | Passed | Passed | Passed | - | Passed on https://detrading.com/ signed wallet connect request | | | | | Fewcha | Aptos | Multichain | Import failed* | - | - | - | - | - | - * Fewcha error: Failed to handle QR code | | | | Gnosis safe | - | - | - | - | - | - | - | - | - Tested already as “Ethereum multisig (Gnosis Safe transaction)” | | | | Keplr | | Multichain | Import failed* | QR import not supported | QR import not supported | QR import not supported | - | - | - Keplr extension frozen after QR reading had completed | | | | Keplr | Ethereum | Ethereum | Import failed | QR import not supported | QR import not supported | QR import not supported | - | - | - Keplr extension reported “invalid QR code” | | | | Keplr | Bitcoin | Bitcoin | Import failed | QR import not supported | QR import not supported | QR import not supported | - | - | - Keplr extension reported “invalid QR code” | | | | Nufi | Multichain | Multichain | QR import not supported | QR import not supported | QR import not supported | QR import not supported | - | - | | | | | Nightly | Multichain | Multichain | Only Ledger supported | Import failed. Phone is vibrating to hint error. | Import failed. Cannot use emulator’s camera. | Import failed. Cannot use emulator’s camera. | Import failed. | - | - I tried import options: Ethereum, Bitcoin, Multichain | | | | Suiet | Solana | Multichain | Import failed | - | - | - | - | - | - Nothing happened during QR code scan | | | | Petra | Aptos | Multichain | Import failed | - | - | - | - | - | - *Petra reported: “Unexpected QR code” | | | | Blockwallet | Ethereum | Multichain | Import failed: Could not scan QR code | - | - | - | - | - | - Same with previous testing for Ethereum QR import | | | | | | | | | | | | | | | |