How to use Keystone as a Signing device in Bitcoin Keeper App ?

Short Answer: To use Keystone as a signing device in Bitcoin Keeper App, first set up and update your Keystone, then add it as a signing device in the Bitcoin Keeper App by scanning its XPUB QR code. Once integrated, you can create multi-sig vaults and sign transactions with the Keystone.

Long Answer:

1. Preparing your Keystone:

• Initial Setup: Initialize your Keystone Essential or Pro by following the dedicated setup guide.(https://support.keyst.one/getting-started/setting-up-keystone-new)
• Firmware Update: Ensure you’re running the latest Keystone firmware. If you’re using it for Bitcoin exclusively, select the Bitcoin-only version.(https://support.keyst.one/getting-started/firmware-upgrading)

2. Setting Up Bitcoin Keeper App:

• Installation: Download and initiate the Bitcoin Keeper app, establishing a new wallet in the process.
• Vault Configuration: At the Pleb tier, you can create a single sig vault. For m-of-n vaults, you should be on either the Hodler or Diamond Hands tier.

3. Pairing Keystone with Bitcoin Keeper:

• Keystone Activation: Power on your Keystone hardware wallet.
• Retrieve XPUB QR Code: Navigate to [Menu] > [Multi-sig Wallet] > click on the [•••] button (upper right) > select [Show/Export XPUB]. This action will generate a QR code containing your XPUB.
• Access Vault in Keeper: On the Bitcoin Keeper’s main interface, click on “Vault”.
• Initiate Device Addition: Opt for “Add 1st signing device”.
• Keystone Selection: From the list of available devices, select “Keystone”.
• Preparation: Review the guidelines, ensuring all requirements are met, then click on “Proceed”.
• XPUB QR Scan: Utilize the Bitcoin Keeper app to scan the XPUB QR code that’s displayed on your Keystone.
• Finalization: After a successful scan, your Keystone will be recognized as a signing device. For users on the Pleb tier, this concludes the single-sig vault configuration. For Hodler and Diamond Hands users, Keystone can now be used as one of the devices required to form multi-sig vaults.

4. Registering Bitcoin Keeper Vault with Keystone:

• Keystone Icon Access: In the Bitcoin Keeper’s Vault section, tap on the Keystone icon.
• Advanced Settings: Proceed by choosing “Advanced Options”.
• Generate Dynamic QR: Opt for “Manual registrations” to generate a responsive QR code.
• QR Scan & Confirmation on Keystone: On Keystone, go to [Menu] > [Multisig Wallet] > [Import Multisig Wallet]. Use its scan feature to capture the dynamic QR from Bitcoin Keeper, then hit “Confirm” to register the vault with Keystone.

5. Handling Bitcoin Transactions in the Vault:

Receiving:

• Initiate “Receive”: Offer the Bitcoin address or its QR code to the sender. You have the option to specify an exact amount.
• Transaction Monitoring: Post-reception, you can monitor the received Bitcoin based on the designated priority.

Sending from a multi-sig Vault:

• Commence Sending Process: Inside the vault, select “Send”.
• Recipient Selection: Choose a destination from your Bitcoin Keeper wallets or manually enter/scan a Bitcoin address.
• Determine Amount & Priority: Specify the sending amount and assign its priority.
• Select Signing Devices: You will be prompted to choose the devices needed to authenticate the transaction.
• Generate PSBT QR with Keystone: If Keystone is among the selected devices, it will generate a PSBT QR code.
• Keystone Transaction Approval: Within Keystone’s interface, go to [Multisig Wallet] > use the scan tool to read the PSBT QR from Bitcoin Keeper. After reviewing transaction details, select “Sign”, provide your authentication credentials, and hit “Confirm”.
• Signature Integration in Bitcoin Keeper: Navigate back to the signature screen in Bitcoin Keeper, click “Import signature”, and scan Keystone’s displayed QR code.
• Acquire Second Signature: Follow similar steps for the secondary signing device.
• Broadcast the Transaction: With signatures from both devices, click “Broadcast Transaction”. You can then verify the transaction using platforms like mempool.space.(https://mempool.space)