A Swiss-made hardware wallet known for its security and simplicity. It and features both SD-Card and USB interfaces for enhanced flexibility.
+ - Coldcard 
A popular choice for a secure and dedicated Bitcoin hardware wallet. Known for its advanced security features and ability to work with PSBT (Partially Signed Bitcoin Transactions).
+ - Cobo 
Designed for durability and security, Cobo is a multi-cryptocurrency hardware wallet with SD-Card support for backup and recovery.
+ - Passport 
This device emphasizes user-friendly design and privacy, offering air-gapped operation via QR codes and SD-Card backup.
+
+### QR Code Wallets
+
+- **Functionality:** QR code wallets operate differently, providing enhanced security through minimal direct connections with other devices. Learn how they work and why this matters.
+- **User background:** Bob, a frequent user of Bitcoin for transactions, often finds himself in public places like coffee shops or conferences. He is concerned about the security risks associated with connecting his wallet to public Wi-Fi or potentially compromised devices.
+- **Use Case:** Bob uses a QR Code wallet, which provides enhanced security through minimal direct connections. When making transactions, he simply scans the QR code displayed by his wallet. This method eliminates the need to connect to potentially insecure networks or devices, significantly reducing the risk of digital asset theft. The QR Code wallet’s ability to operate with minimal connectivity makes it an excellent choice for secure, hassle-free transactions in public settings.
+- **Supported Devices:**
+
+ - Jade 
A budget-friendly hardware wallet with QR code functionality for secure and offline transactions.
+ - SeedSigner 
An open-source project that focuses on creating a secure, offline transaction signing device using QR codes.
+
+### USB Wallets
+
+- **Characteristics:** USB wallets come with distinct features, including direct connectivity and user-friendly interfaces. Get a deeper understanding of what makes them stand out.
+- **Scenarios:** Find out when and where USB wallets are your best choice. We'll showcase their versatility and compatibility with a wide range of devices.
+- **User background:** Carol, a small business owner, accepts Bitcoin in her store. She needs a wallet that is both easy to use and compatible with various devices since she regularly deals with different types of transactions.
+- **Use Case:** Carol chooses a USB wallet for its user-friendly interface and direct connectivity. The USB wallet's plug-and-play nature makes it simple to connect to her store's point-of-sale system or her personal computer. Its compatibility with various devices allows her to efficiently manage transactions without the need for specialized hardware. The USB wallet's intuitive interface makes it easy for Carol to navigate, making it an ideal choice for her everyday business transactions.
+- **Supported Devices:**
+
+ - BitBox02 Swiss-made hardware wallet, offering a blend of security and simplicity. Bitcoin Only version available.
+ - KeepKey 
A user-friendly wallet with a large display, providing a secure environment for cryptocurrency storage and transactions.
+ - Ledger 
Known for its security and sleek design, Ledger wallets support a wide range of cryptocurrencies. Less security since it contains code for other shitcoins.
+ - Trezor 
One of the first hardware wallets in the market, renowned for its ease of use and robust security measures.
+ - Keystone 
Formerly known as Cobo Vault, Keystone wallets offer a high-security solution with air-gapped QR code signing.
+
+
+## Step-by-Step Guide for Device Creation in Specter
+
+### Add a new device
+Select signing device
+
+Upload public keys
+
+
+### Select how to connect to Bitcoin network
+
+Electrum server or...
+
+...via Bitcoin Core node.
+
+
+
+## Understanding Derivation Paths
+
+### Concept Explanation
+
+Understanding derivation paths is fundamental to managing the security of your digital assets. In this section, we'll provide you with an overview of what derivation paths are and why they matter. We'll also introduce key paths like BIP 44 (for multi-account hierarchy), BIP 49 (for SegWit compatibility), and BIP 84 (for native SegWit addresses). Each of these paths caters to different Bitcoin address types and plays a crucial role in organizing and securing your Bitcoin, especially within hardware wallets.
+
+By default, Specter Wallets are set up with:
+- BIP 44 for traditional multisig wallets.
+- BIP 49 or BIP 84 for SegWit singlesig wallets.
+
+These default settings cover the needs of most users, simplifying the wallet setup and usage process. However, understanding these paths can enhance your ability to tailor the wallet to your specific needs, especially if you have advanced security considerations.
+
+### Challenges and Best Practices
+
+1. **Complexity:**
+ - Derivation paths, especially when considering various Bitcoin address types like BIP 44, BIP 49, and BIP 84, can be intricate. The challenge lies in comprehending the nuances of each path and selecting the one that aligns with your specific use case. Best practice here is to educate yourself thoroughly and seek expert advice if needed.
+
+2. **Compatibility:**
+ - Using the wrong derivation path can lead to compatibility issues, making it challenging to access your funds. It's crucial to ensure that the path you choose is supported by your wallet software and the services you intend to use. Staying informed about updates and changes in the Bitcoin ecosystem is essential to avoid compatibility pitfalls.
+ - To assist with this, [common derivation paths for different wallets can be found at Wallets Recovery](https://walletsrecovery.org/). This resource can be useful for understanding the standard practices of various wallets and ensuring compatibility.
+ - Ensure that the path you choose is supported by your wallet software and the services you intend to use.
+
+3. **Security Risks:**
+ - Incorrectly managed derivation paths can introduce security risks. For instance, sharing your master public key (xpub) derived from an account with a third party may expose all the addresses generated from it. Best practice involves limiting the exposure of sensitive information and adopting a "need-to-know" approach when sharing keys or information related to derivation paths.
+ - Limit the exposure of sensitive information and adopt a "need-to-know" approach when sharing keys or information related to derivation paths.
+
+4. **Backup Strategies:**
+ - Derivation paths affect how you back up your wallet. Implementing a robust backup strategy that includes the derivation path information is essential. Best practice is to maintain secure backups and periodically test your recovery process to ensure you can regain access to your digital assets if the need arises.
+ - Implementing a robust backup strategy that includes the derivation path information is essential.
+
+### Example 1: BIP 84 (Hierarchical Deterministic Wallets)
+#### Scenario: Multiple Account Management
+
+##### Context
+Emily, a Bitcoin enthusiast, has diverse needs for managing her digital assets. She wants to separate her main funds from the stacking service provider she's using. For this, she needs a wallet structure that allows for clear separation while maintaining privacy and security.
+
+##### Use Case
+Emily opts to use the BIP 84 derivation path, which is designed for native SegWit addresses, providing her with an efficient and cost-effective way to manage her Bitcoin transactions. She uses two different paths within BIP 84 to separate her funds:
+- For her main wallet, where she keeps the majority of her funds, Emily uses the derivation path `m/84'/0'/0'`. This path is for her personal use, ensuring that her primary funds remain secure and private.
+- For the stacking service provider, which requires her to share her extended public key (xpub) for operational purposes, she uses the derivation path `m/84'/0'/1'`. This separation allows her to maintain privacy and security, as the service provider only has visibility over the funds in the dedicated stacking account.
+
+##### Advantage
+By using two distinct accounts under the BIP 84 standard, Emily efficiently manages her assets, keeping her main funds secure and private while still participating in stacking services.
+
+### Example 2: BIP 49 (SegWit Compatibility in P2SH)
+#### Scenario: Balancing Efficiency with Cost in Wallet Management
+
+##### Context
+John has been managing his Bitcoin assets using an older wallet setup. As the volume of his transactions increases, he's faced with the challenge of seeking more efficient transaction processing, both in terms of speed and reduced fees, without incurring significant costs in moving his funds.
+##### Use Case
+John's current wallet utilizes BIP 49, which enables SegWit compatibility through Pay to Script Hash (P2SH) addresses, identifiable by starting with '3'. His addresses follow the derivation path m/49'/0'/0'. Despite being aware of newer wallet technologies like those adhering to BIP 84, which offer even greater efficiencies by fully embracing native SegWit addresses (beginning with 'bc1'), John decides to stick with his current setup.
+##### Advantage
+John's decision is influenced by his desire to maintain his current UTXO set. He is cautious about the transaction fees that would be incurred in transferring his entire balance to a new wallet structure. By sticking with BIP 49, John still benefits from reduced transaction fees and improved speeds compared to legacy addresses, but he acknowledges that his setup is not as efficient as it could be with BIP 84. His choice represents a compromise between optimizing transaction efficiency and minimizing the costs associated with a complete migration to a new wallet system.
+
+### Example 3: BIP 84 (Native SegWit Bech32 Addresses)
+#### Scenario: Maximizing Efficiency and Exploring Testnets
+
+##### Context
+Lisa is a tech-savvy investor who keeps up with the latest developments in Bitcoin technology. She wants to use the most advanced and efficient method for managing her Bitcoin transactions. Additionally, Lisa is interested in exploring Bitcoin testnets for testing and educational purposes.
+
+##### Use Case
+Lisa opts for a wallet that implements BIP 84, which enables the creation of native SegWit addresses that start with 'bc1'. These are Bech32 addresses, which offer benefits such as more efficient block weight usage and better error detection. For her main Bitcoin transactions, her derivation path is: `m/84'/0'/0'`.
+
+Moreover, Lisa is also experimenting with Bitcoin testnet. Testnets are crucial for trying out transactions without using real Bitcoin, which is an ideal environment for testing and learning. For her testnet transactions, she uses the derivation path `m/84'/1'/0'`. This path is specifically designated for testnet in BIP 84, allowing her to differentiate between real and test transactions easily.
+
+##### Advantage
+Using BIP 84, Lisa experiences lower fees and faster transactions in her main wallet. With the addition of the testnet path, she can safely experiment and learn without risking her actual Bitcoin. This approach not only future-proofs her wallet as the industry moves towards broader adoption of SegWit but also enhances her understanding and proficiency in managing digital assets.
+
+### Conclusion
+In each of these scenarios, the use of different derivation paths (BIP 44, BIP 49, and BIP 84) reflects a specific need and functionality in managing Bitcoin transactions:
+- **BIP 44** is ideal for users like Emily, who require a structured organization for multiple types of transactions. It provides a clear hierarchical structure for different accounts under a single master seed.
+- **BIP 49** benefits users like John, who seek efficiency and reduced costs in their transactions. The SegWit compatibility in P2SH format helps in lowering transaction fees and improving confirmation speeds.
+- **BIP 84** is perfect for tech-savvy users like Lisa, who want to leverage the latest advancements in Bitcoin technology for optimal efficiency and future compatibility.
+
+For those seeking a deeper understanding of derivation paths, we recommend exploring "[Learn Me a Bitcoin". This website provides in-depth information](https://learnmeabitcoin.com/technical/derivation-paths) on the topic, and you can integrate this knowledge into our guide for a more comprehensive grasp of derivation paths.
+
+## Troubleshooting
+
+### Common Issues
+
+#### Check the USB Connection
+- **Step 1:** Unplug the wallet from the computer.
+- **Step 2:** Inspect the USB cable for any visible damage. If damaged, replace the cable.
+- **Step 3:** Reconnect the wallet to the computer using a different USB port. Sometimes ports can malfunction or have poor connectivity.
+
+#### Restart the Wallet and Computer
+- **Step 1:** Safely eject the hardware wallet from your computer.
+- **Step 2:** Restart the hardware wallet. If it has a power button, turn it off and then on again. If not, disconnect and reconnect it.
+- **Step 3:** Restart your computer. This can resolve issues caused by temporary software glitches.
+
+#### Update Wallet Firmware and Software
+- **Step 1:** Check if your hardware wallet firmware is up to date. Refer to the wallet’s official website for the latest firmware version.
+- **Step 2:** Update the wallet application on your computer. Ensure you're using the latest version.
+- **Step 3:** After updating, reconnect the wallet and check if it is recognized.
+
+#### Check Device Manager (Windows) or System Report (Mac)
+**For Windows:**
+- **Step 1:** Open 'Device Manager'.
+- **Step 2:** Look under ‘Universal Serial Bus controllers’. Check if the wallet is listed or if there are any devices with a yellow exclamation mark.
+- **Step 3:** If the wallet is listed with an error, right-click on it and select ‘Update driver’.
+
+**For Mac:**
+- **Step 1:** Click on the Apple logo and select ‘About This Mac’.
+- **Step 2:** Go to ‘System Report’ and select ‘USB’.
+- **Step 3:** Check if the wallet is listed under USB Device Tree.
+
+#### Try a Different Computer
+- **Step 1:** Connect the wallet to a different computer. This can help determine if the issue is with the original computer’s hardware or software.
+
+#### Contact Customer Support or our Telegram Group
+If none of the above steps work, the problem might be more complex or specific to the wallet. In this case, contact the customer support of the hardware wallet for further assistance.
+
+### Preventive Measures
+- Regularly update the wallet's firmware and the computer’s software to avoid compatibility issues.
+- Use high-quality USB cables and ports to ensure a stable connection.
+- Avoid exposing the hardware wallet to physical damage or extreme temperatures.
+
+By the end of this guide, you'll be well-equipped to create and manage hardware wallets within the Specter environment and understand derivation paths. Let's get started on your journey to safeguarding your bitcoin journey.
diff --git a/docs/WalletCreationGuide.md b/docs/WalletCreationGuide.md
new file mode 100644
index 0000000000..9267bf74a3
--- /dev/null
+++ b/docs/WalletCreationGuide.md
@@ -0,0 +1,69 @@
+# Wallet Creation Guide
+
+## Introduction
+
+Specter wallets are designed to provide a user-friendly interface around Bitcoin Core, focusing on multisignature setups with airgapped signing devices, though they also support single-signature wallets. It's developed to make the interaction with Bitcoin Core more convenient for the users.
+
+## Types of Wallets
+
+### Single-Sig Wallets
+- These involve one signing device or hardware wallet generating one seed.
+- They are simpler and require only one secure location for seed backup.
+- However, they are less secure against phishing attacks as one compromised seed can lead to lost Bitcoin.
+
+### Multi-Sig Wallets
+- More secure than single-sig, multisig wallets require two or more signing devices to authorize transactions.
+- A key feature is the quorum requirement, which specifies the number of signatures needed out of the total number of devices. For example, a common scenario is requiring 2 signatures from a total of 3 devices (2/3 quorum). This setup enhances security as it requires multiple parties or devices to agree on a transaction.
+- Multisig wallets are particularly effective against phishing and theft as compromising one seed or device is not enough to access the funds.
+- They offer better security, as one compromised seed doesn't result in immediate loss of funds.
+- However, they are more complex to set up and require multiple secure locations for seed backups.
+
+#### Single-Sig Wallets Examples:
+
+- A user with a **Ledger Nano S** hardware wallet creating a single-signature Specter wallet for added convenience in managing their Bitcoin holdings.
+- Someone who wants a simple wallet setup opting for a single-signature wallet with their **Electrum** software wallet, as they trust their computer's security.
+
+#### Multi-Sig Wallets Examples:
+
+- A group of friends setting up a multi-signature Specter wallet for a shared investment fund, where multiple devices are required to authorize transactions, enhancing security. For more detailed guidance on setting up such a wallet, [refer to our Multi-Sig Wallet Guide](multisig-guide.md).
+- A Bitcoin exchange using a multi-signature setup with several hardware wallets to protect customer funds against a single point of failure. [Our Multi-Sig Wallet Guide offers](multisig-guide.md) comprehensive steps and best practices for implementing such a secure system.
+
+
+## Step-by-Step Guide for Single-Sig Wallets
+
+1. **Setup and Installation**
+ - Download and install the Specter Desktop app from the official GitHub release page. You can [find the installation guide here](install_guide.md).
+ - Ensure your system meets the necessary requirements (like Python version, Bitcoin Core version).
+
+2. **Running the App**
+ - Start the Specter Desktop app.
+ - It should automatically detect Bitcoin Core if it's using a default data folder.
+ - If not, set rpcuser and rpcpassword in the Bitcoin Core's bitcoin.conf file and directly in the Specter app settings. You can [find the Node Connecting Guide here](connect-your-node.md).
+
+3. **Creating a Wallet**
+ - In Specter, navigate to the wallet creation section.
+ - **Important:** Before proceeding, ensure you have imported your hardware wallet device (e.g., Ledger, BitBox, Trezor) into Specter Desktop. Specter is specifically designed to enhance security by working with hardware wallets, providing an extra layer of protection compared to hot wallets. For detailed instructions on connecting your hardware wallet, [refer to the Device Creation Guide](DeviceCreationGuide.md).
+ - Choose the option for a single-signature wallet if you are setting up a wallet with one device. For enhanced security, consider setting up a multi-signature wallet.
+ - When creating a single-signature wallet, Specter will interface with your hardware wallet. **Note:** If your hardware wallet is already initialized (which is the common scenario), Specter will use the existing seed from your device to manage the wallet. There is no need to generate a new seed within Specter. It is crucial to keep your seed secure and never enter it on the computer or share it with anyone.
+ - **For New Hardware Wallet Users:**
+ If your hardware wallet is new and not yet initialized, you will need to generate a new seed as part of the hardware wallet's setup process. This is typically done directly on the hardware wallet to ensure maximum security. Follow your hardware wallet's instructions for this step. Once your hardware wallet is initialized with a new seed, you can proceed to connect it with Specter Desktop.
+
+4. **Backing Up the Wallet**
+ - After creating the wallet, it's crucial to back up the seed securely.
+ - For single-signature wallets, where the loss of the seed equates to the loss of funds, Specter strongly recommends storing seeds on steel. This method provides long-term durability against elements like fire and water, ensuring your backup remains intact in various scenarios.
+ - While still advisable for multi-signature setups, steel backups in multisig configurations are slightly less critical since the loss of a single seed doesn’t necessarily mean loss of funds, provided other signatures are available. However, it is still a best practice to secure each seed with the utmost care.
+
+5. **Testing the Wallet**
+ - It's advisable to test the wallet by sending a small amount of Bitcoin to it and then trying to access these funds using the wallet.
+
+## Backup PDFs
+
+- Specter provides backup PDFs that contain crucial information like (master) public keys and fingerprints.
+- These backups do not include the seed itself.
+- Keep a copy of the backup PDFs with every seed backup, but ensure they are kept private as they allow anyone to recreate the wallet and see the balance.
+
+## Notes
+
+- Always ensure the safety of your seed phrases and backup information.
+- Regularly update the Specter software and your Bitcoin Core node for security and functionality improvements.
+- For multisig wallet creation, a separate, more detailed guide is recommended due to its complexity.
diff --git a/docs/api/README.md b/docs/api/README.md
index 5562157e53..f0c95731dc 100644
--- a/docs/api/README.md
+++ b/docs/api/README.md
@@ -10,11 +10,13 @@ In order to make reasonable assumptions about how stable a specific endpoint is,
The Specter API is using JWT tokens for Authentication. In order to use the API, you need to obtain such a token. Currently, obtaining a token is not possible via the UI but only via a special endpoint, which accepts BasicAuth (as the only endpoint).
+NB: The default user and password key-value pair for Specter Desktop is `admin:admin`.
+
## Curl:
Create the token like this:
```bash
-curl -u admin:password --location --request POST 'http://127.0.0.1:25441/api/v1alpha/token' \
+curl -u user:password --location --request POST 'http://127.0.0.1:25441/api/v1alpha/token' \
--header 'Content-Type: application/json' \
-d '{
"jwt_token_description": "A free description here to know for what the token is used",
@@ -35,7 +37,7 @@ As a result, you get a json like this:
The token will only be shown once. However, apart from the token itself, you can still get the details of a specific token like this:
```bash
-curl -s -u admin:secret --location --request GET 'http://127.0.0.1:25441/api/v1alpha/token/4969e9fb-2097-41e7-af53-5e2082a3e4d3' | jq .
+curl -s -u user:password --location --request GET 'http://127.0.0.1:25441/api/v1alpha/token/4969e9fb-2097-41e7-af53-5e2082a3e4d3' | jq .
```
```json
@@ -81,7 +83,7 @@ Here is an example of using the API with python. We don't assume that you use Ba
```python
import requests
-response = requests.get('http://127.0.0.1:25441/api/v1alpha/token/