Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeepKey BTC accounts not detected and automatically for BTC segwit balances #8156

Open
purelycrickets opened this issue Nov 21, 2024 · 3 comments
Assignees
Labels
bug Something isn't working needs engineering Requires engineering input before bounty

Comments

@purelycrickets
Copy link

Overview

Currently in production, with a clear cache, when connecting a KeepKey with a Segwit balance only in Account 0, we do not detect the balance and require the user to manually add their BTC address.

References and additional details

I was able to get balances to load initially for a personal KeepKey with a higher BTC balance (Segwit Native) on initial load with a clear cache, but could not get the same results for my test KK that only has BTC in a segwit address.

Jam of no BTC account detection even though there is a BTC balance: https://jam.dev/c/f034e8b5-3ea1-48e9-b8d0-0e8baf1eec78

A user in this situation could think they have lost their BTC, panic, and not know how to toggle their accounts in manage account to reveal them.

Acceptance Criteria

KeepKey accounts with balances are detected for all supported chains without the need to manually add them.

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

@purelycrickets purelycrickets added bug Something isn't working needs engineering Requires engineering input before bounty labels Nov 21, 2024
@purelycrickets
Copy link
Author

Getting more reports from users about this issue blocking them from seeing their balances.

@purelycrickets
Copy link
Author

This is now appearing to also affect other UTXO chains like DOGE and LTC.

@0xean 0xean moved this from Backlog to Up next / groomed in ShapeShift Dashboard Nov 25, 2024
@NeOMakinG NeOMakinG self-assigned this Nov 28, 2024
@NeOMakinG NeOMakinG moved this from Up next / groomed to In progress in ShapeShift Dashboard Nov 28, 2024
@NeOMakinG
Copy link
Collaborator

I did try to reproduce multiple times using:

  • An already existing wallet
  • A fresh new wallet
  • With Segwit
  • With Segwit native
  • With wallet with another tx history already existing

I'm struggling to reproduce... If you have any other interesting informations to share, I feel stuck now :/

@NeOMakinG NeOMakinG moved this from In progress to Blocked in ShapeShift Dashboard Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs engineering Requires engineering input before bounty
Projects
Status: Blocked
Development

No branches or pull requests

2 participants