Alternative question: I can’t find funds (i.e. STX, BTC) displayed in Ledger Live when I try to access it with the Ledger device in Leather, why is that?

If you're using a Ledger device and trying to view your Stacks (STX) funds in Leather wallet, you may encounter some compatibility challenges. This guide explains why these issues occur, how to resolve them, and provides important details about Bitcoin addresses and their differences.

Why Your Ledger Live Stacks Account Funds May Not Appear in Leather

Derivation Path Differences

Ledger Live and Leather Wallet use different derivation paths to generate Stacks addresses:

• Ledger Live:

  • Account 1: m/44'/5757'/0'/0/0

  • Account 2: m/44'/5757'/1'/0/0

  • Account 3: m/44'/5757'/2'/0/0

  • Additional addresses within an account: m/44'/5757'/0'/0/1, m/44'/5757'/0'/0/2, etc.

    
    

• Leather Wallet:

  • Account 1: m/44'/5757'/0'/0/0

  • Account 2: m/44'/5757'/0'/0/1

  • Account 3: m/44'/5757'/0'/0/2

This means that if you generate accounts or addresses using Ledger Live, they may not align with the paths used by Leather Wallet. As a result, you may not see these addresses in Leather.

Fresh Address Generation in Ledger Live

Ledger Live generates fresh addresses within an account as you use them. For example:

• The first Bitcoin address in Account 1 is always the same (m/44'/0'/0'/0/0), but subsequent addresses like m/44'/0'/0'/0/1, m/44'/0'/0'/0/2 are generated dynamically.

Leather Wallet, on the other hand, does not automatically generate new addresses beyond the initial ones. This difference affects both Bitcoin and Stacks accounts.

Resolving Compatibility Issues

Stacks (STX)

If your Stacks account is not appearing in Leather, here’s how to fix it:

1. Identify the Address in Ledger Live: Check the address in Ledger Live where your STX is stored.

2. Send Funds to Leather’s Address: In Leather, click "Receive" to display your Stacks address. Send your STX from the Ledger Live address to the address shown in Leather.

3. Monitor in Ledger Live: Once your STX balance appears in Leather, you can add this account to Ledger Live (via "Add Account") for monitoring purposes. Note that this only works if the address has a balance.

Bitcoin (BTC)

For Bitcoin, the process is similar, but there are additional considerations:

• Taproot Addresses: Taproot addresses (used for ordinal inscriptions or collectibles) require special handling. Sending or spending BTC tied to an ordinal inscription could inadvertently destroy the collectible.

• Separate Devices: If you manage collectibles or inscriptions, consider using separate Ledger devices for Ledger Live and Leather accounts. This minimizes risks of accidental spending.

Key Differences for Bitcoin Addresses

1. Fresh Address Generation:

   • Ledger Live generates a new address once a previously generated address has been used.

   • Leather Wallet currently does not generate new addresses automatically.

2. Ordinal Collectibles (Taproot):

   • Sending BTC tied to an ordinal inscription from Ledger Live could destroy the collectible.

   • Always double-check before sending BTC from a Taproot address.

Best Practices

• Use Leather for STX: Always generate Stacks addresses using Leather if you plan to use the funds there. Avoid generating Stacks addresses in Ledger Live.

• Monitor Balances with Ledger Live: After transferring STX to a Leather address, you can monitor the balance in Ledger Live.

• Be Cautious with Taproot Addresses: For users holding Bitcoin collectibles, avoid accessing these accounts in Ledger Live to prevent accidental spending.

• Separate Devices (Optional): Consider using one Ledger device for Leather accounts and another for Ledger Live to ensure clear account separation.

Conclusion

By understanding the differences in derivation paths and address generation between Ledger Live and Leather Wallet, you can manage your STX and BTC funds seamlessly. For Stacks, always use Leather to generate addresses, and for Bitcoin, exercise caution with Taproot addresses.

If you have further questions, feel free to reach out to our support team or consult our Derivation Path Explainer.