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.

Sign up for GitHub

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

Jump to bottom

Old address inaccessible after internal wash #22

Closed
shihanqu opened this issue Dec 17, 2013 · 1 comment
Closed

Old address inaccessible after internal wash #22

shihanqu opened this issue Dec 17, 2013 · 1 comment

Comments

@shihanqu
Copy link

Back in Mid August, there was some sort of internal wash of bitcoin, and the balance of the old address was moved to a new address.

However, I just found out people have been sending payments to one of the old addresses. Since then, I've gotten a new phone, and restored keys that were backed up. It seems I no longer have access to the original address, which now has .85BTC collected on it.

Here is the blockchain.info link of the transaction: https://blockchain.info/tx/8cbb9ea385426c9a0e7fef56cb09067aa0945d7fb2cde926de4ee87344d1de78

The old address that has a non-zero amount of bitcoin is:
https://blockchain.info/address/1LV8iTmtGXfWkmuSzmLvaC6XWMZ7db3bqD

What can I do?
@schildbach
Copy link
Collaborator

Backups from after the August security incident do not contain the old, unsecure keys. Because you would mix them back into your wallet which would make it unsecure again.

What you should do is sweep the old keys. If you don't have a second mobile device, I suggest restoring your old (pre-August) backups to a new wallet in MultiBit. When the coins are restored, move them to a secure address, remove the (now empty) wallet and never use the keys again.

oliveraemmer pushed a commit to HW-Backed-Bitcoin-Wallet/bitcoin-wallet that referenced this issue Apr 9, 2024
@oliveraemmer
# This is a combination of 24 commits.
92ae3d2 
# This is the 1st commit message:

added new strings for upcoming keystore support

# This is the commit message #2:

moved from spending pin menu to wallet protection menu

# This is the commit message #3:

added prototype for supporting keystore and spending pin in a dialog fragment

# This is the commit message #4:

KeyStoreKeyCrypter with biometric authentication (#9)

* implemented new KeyStoreKeyCrypter and biometric authentication, untested

* added KeyStore features

# This is the commit message #5:

added a working version that supports both keycrypters without user biometric authentication

# This is the commit message #6:

small change*

# This is the commit message #7:

wip

# This is the commit message #8:

working version for encrypt but decrypt only works if its in the timout period. if decrypt needs to authenticate the user the app freezes i.e. the UI thread doesn't responde

# This is the commit message #9:

wip

# This is the commit message #10:

rebase2

# This is the commit message #11:

upgrade build successful, not tested

# This is the commit message #12:

rebase

# This is the commit message #13:

fixed tx declaration

# This is the commit message #14:

rebase

# This is the commit message #15:

rebase

# This is the commit message #16:

wip, implemented KeyCrypterFactory

# This is the commit message #17:

backup with keystorekeycrypter


# This is the commit message #18:

small changes for 0.17 upgrade + context propagation in cryptactivity

# This is the commit message #19:

sending funds when keystore encrypted fix

# This is the commit message #20:

removed button from CryptActivity, fixed backup export and import

# This is the commit message bitcoin-wallet#21:

added strings

# This is the commit message bitcoin-wallet#22:

fixed backup with keystore

# This is the commit message bitcoin-wallet#23:

added string resources and new EncryptionType

# This is the commit message bitcoin-wallet#24:

removed scrypt params from KeyStoreKeyCrypter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@schildbach @shihanqu