Search content
Sort by
Showing 14 of 14 results by Stalesamy
This wallet already appears to have been loaded into Bitcoin Core previously... in Mid-December 2020... and it has "refilled" the keypool with a bunch of new private keys/addresses. The 0014 privkeys and "3" addresses are the P2SH versions of the private keys.
What exactly has your "friend" done with this wallet.dat before they gave it to you?
How was it "recovered" to start with?
What exactly has your "friend" done with this wallet.dat before they gave it to you?
How was it "recovered" to start with? He emailed the wallet.dat to himself, I'm going to have him fw me the original email, as I'm assuming he did something with it before he sent it to me.
If you were able to load the wallet in Bitcoin Core and run dumpwallet then all you need are the privkeys starting with "5" or "L" or "K". You can import all of those into an Electrum wallet (https://electrum.org/#download - Read the HOWTO verify guide here: https://bitcointalk.org/index.php?topic=5240594.msg54223763#msg54223763)
As I said, it seems that you're having issues with PyWallet due to the updates... you'd either need to switch back to Python2.7 and my old version of PyWallet... or wait for JackJack to get a less "unstable" version of the new Python3 compatible Pywallet up and running.
But it's not necessary if the wallet.dat opens in Bitcoin Core... you'd just be dumping the same info... so I'd just forget about PyWallet for now.
Focus on importing those private keys into another wallet, and check to see if any transaction history is found (and hopefully a positive balance!
)
As I said, it seems that you're having issues with PyWallet due to the updates... you'd either need to switch back to Python2.7 and my old version of PyWallet... or wait for JackJack to get a less "unstable" version of the new Python3 compatible Pywallet up and running.
But it's not necessary if the wallet.dat opens in Bitcoin Core... you'd just be dumping the same info... so I'd just forget about PyWallet for now.
Focus on importing those private keys into another wallet, and check to see if any transaction history is found (and hopefully a positive balance!
)Thanks, if I get anything from this, you'll def get a piece....
Do you know what the keys that start with 0014 represent? The pub key for those start with 3's
So I was able to open the wallet.dat file in the latest version of Bitcoin Core, when I do dumpwallet "~/wallet.txt" the file has a bunch of pub/priv keys in it. For example it has a line that says extended "private masterkey: xprivxxxxxxxxxxxxxxxxxxxxx" followed by 2,000 priv keys that begin with '5' or 'L' and the public keys beginning with 'bc1'. After those 2,000 pub/priv key pairs there are another 2,000 pub/priv keys pairs, priv keys that begin with '00' and pub keys that begin with '3'.
Example: Kxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2020-12-17T16:32:01Z reserve=1 # addr=bcxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx hdkeypath=m/0'/0'/696'
00xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0 script=1 # addr=3xxxxxxxxxxxxxxxxxxxxxxxxxxx
any ideas?
Update on pywallet: Still couldn't get it to dumpwallet, stuck on this error:
Wallet data not recognized: Bdict({'__key__': b'\bunch of stuff like \x03\x11\xab ', '__value__': b'UNKNOWN_DATA', '__type__': b''})
Wallet data not recognized: Bdict({'__key__': b'\bunch of stuff like \x03\x11\xab', '__value__': b'UNKNOWN_DATA', '__type__': b''})
Wallet data not recognized: Bdict({'__key__': b'\'bunch of stuff like \x03\x11\xab, '__value__': b'UNKNOWN_DATA', '__type__': b''})
Traceback (most recent call last):
File "pywallet.py", line 2316, in parse_wallet
item_callback(type, d)
File "pywallet.py", line 2716, in item_callback
json_db[type] = 'unsupported'
File "pywallet.py", line 111, in __setitem__
return super(Bdict, self).__setitem__(bytes_to_str(k), v)
File "pywallet.py", line 90, in bytes_to_str
return k.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa1 in position 0: invalid start byte
ERROR parsing wallet.dat, type b'\xa1'
key data: b' bunch of stuff like \x03\x11\xab'
key data in hex: b'long string'
value data in hex: b'short string'
Example: Kxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2020-12-17T16:32:01Z reserve=1 # addr=bcxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx hdkeypath=m/0'/0'/696'
00xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0 script=1 # addr=3xxxxxxxxxxxxxxxxxxxxxxxxxxx
any ideas?
Update on pywallet: Still couldn't get it to dumpwallet, stuck on this error:
Wallet data not recognized: Bdict({'__key__': b'\bunch of stuff like \x03\x11\xab ', '__value__': b'UNKNOWN_DATA', '__type__': b''})
Wallet data not recognized: Bdict({'__key__': b'\bunch of stuff like \x03\x11\xab', '__value__': b'UNKNOWN_DATA', '__type__': b''})
Wallet data not recognized: Bdict({'__key__': b'\'bunch of stuff like \x03\x11\xab, '__value__': b'UNKNOWN_DATA', '__type__': b''})
Traceback (most recent call last):
File "pywallet.py", line 2316, in parse_wallet
item_callback(type, d)
File "pywallet.py", line 2716, in item_callback
json_db[type] = 'unsupported'
File "pywallet.py", line 111, in __setitem__
return super(Bdict, self).__setitem__(bytes_to_str(k), v)
File "pywallet.py", line 90, in bytes_to_str
return k.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa1 in position 0: invalid start byte
ERROR parsing wallet.dat, type b'\xa1'
key data: b' bunch of stuff like \x03\x11\xab'
key data in hex: b'long string'
value data in hex: b'short string'
I'm not sure what you mean by "you are using an experimental build of pywallet and cloned the Github repo while jackjack was updating stuff."
Basically the pywallet is on alpha/beta version.
I tried moving the wallet.dat folder into ./bitcoin wallet folder and when I open bitcoin-qt -rescan it says:
"Warning: error reading wallet.dat! All keys read correctly, but transaction data or address book entries might be missing or incorrect."
"Warning: error reading wallet.dat! All keys read correctly, but transaction data or address book entries might be missing or incorrect."
That means the wallet.dat file is corrupted, but the most important part (the keys) of wallet is intact. You can try,
1. Export the keys to another wallet (such as Electrum) with dumpwallet command
2. Fully sync Bitcoin-qt, where you need to download and verify 350GB+ of blockchain. If you plan to do it, make sure to update Bitcoin-qt to newest Bitcoin Core version, which offer better performance.
Thanks for your response, I don't know any of the public addresses associated with this wallet.dat. From my understanding you need atleast 1 to dumpwallet. If I download full node, will the addresses show up? How can I recover something off of this wallet.dat file?
Have you tried to import this wallet.dat to a newer version of Bitcoin core?
If not yet I suggest you try it first but make sure make a backup copy of that file first before you open it with the latest version of Bitcoin core.
Or try to open it with a notepad since you said it was not encrypted and you might see the private key when you open it with notepad.
If not, try this one below which is created in 2011 when the wallet.dat is not encrypted yet.
- https://bitcointalk.org/index.php?topic=25091.0
If not yet I suggest you try it first but make sure make a backup copy of that file first before you open it with the latest version of Bitcoin core.
Or try to open it with a notepad since you said it was not encrypted and you might see the private key when you open it with notepad.
If not, try this one below which is created in 2011 when the wallet.dat is not encrypted yet.
- https://bitcointalk.org/index.php?topic=25091.0
I tried moving the wallet.dat folder into ./bitcoin wallet folder and when I open bitcoin-qt -rescan it says:
"Warning: error reading wallet.dat! All keys read correctly, but transaction data or address book entries might be missing or incorrect."
You must be using Python 2 because it's default behavior for the decode() method is to use the "ascii" codec which can't handle any bytes greater than 0x7f , while Python 3 switched to the "utf8" codec which does handle all kinds of bytes.
Running Pywallet using Python 3 is going to remove this error, but I notice your stack trace also has json_db[type] = 'unsupported'. Which points to one of two possibilities:
- either your friend gave you a weird wallet.dat that has an unsupported field in the database, or:
- you are using an experimental build of pywallet and cloned the Github repo while jackjack was updating stuff.
I'm inclined to think it is the second possibility so can you try rolling back to an older commit by running "git checkout COMMIT_ID_You_get_from_github"?
Running Pywallet using Python 3 is going to remove this error, but I notice your stack trace also has json_db[type] = 'unsupported'. Which points to one of two possibilities:
- either your friend gave you a weird wallet.dat that has an unsupported field in the database, or:
- you are using an experimental build of pywallet and cloned the Github repo while jackjack was updating stuff.
I'm inclined to think it is the second possibility so can you try rolling back to an older commit by running "git checkout COMMIT_ID_You_get_from_github"?
So he emailed me the wallet.dat file, I put it into the pywallet directory, ran python3 pywallet.py --dumpwallet --wallet=wallet.dat
and I get :
Wallet data not recognized: Bdict({'__key__': b'\bunch of stuff like \x03\x11\xab ', '__value__': b'UNKNOWN_DATA', '__type__': b''})
Wallet data not recognized: Bdict({'__key__': b'\bunch of stuff like \x03\x11\xab', '__value__': b'UNKNOWN_DATA', '__type__': b''})
Wallet data not recognized: Bdict({'__key__': b'\'bunch of stuff like \x03\x11\xab, '__value__': b'UNKNOWN_DATA', '__type__': b''})
Traceback (most recent call last):
File "pywallet.py", line 2316, in parse_wallet
item_callback(type, d)
File "pywallet.py", line 2716, in item_callback
json_db[type] = 'unsupported'
File "pywallet.py", line 111, in __setitem__
return super(Bdict, self).__setitem__(bytes_to_str(k), v)
File "pywallet.py", line 90, in bytes_to_str
return k.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa1 in position 0: invalid start byte
ERROR parsing wallet.dat, type b'\xa1'
key data: b' bunch of stuff like \x03\x11\xab'
key data in hex: b'long string'
value data in hex: b'short string'
To download pywallet on my machine, I ran: git clone https://github.com/jackjack-jj/pywallet.git
I'm not sure what you mean by "you are using an experimental build of pywallet and cloned the Github repo while jackjack was updating stuff."
Could you walk me through?
-Thanks for your help
Hello, I was given a wallet.dat file from a friend to try and recover anything on it. I am using pywallet. I have no idea what any of the public addresses are associated with this wallet. This wallet was also supposedly made before wallet encryption was mandatory.
When I run python pywallet.py --dumpwallet --wallet=wallet.dat > ~/wallet.dat.json
I get:
Traceback (most recent call last):
File "pywallet.py", line 2316, in parse_wallet
item_callback(type, d)
File "pywallet.py", line 2716, in item_callback
json_db[type] = 'unsupported'
File "pywallet.py", line 111, in __setitem__
return super(Bdict, self).__setitem__(bytes_to_str(k), v)
File "pywallet.py", line 90, in bytes_to_str
return k.decode()
UnicodeDecodeError: 'ascii' codec can't decode byte 0xa1 in position 0: ordinal not in range(128)
any ideas?
When I run python pywallet.py --dumpwallet --wallet=wallet.dat > ~/wallet.dat.json
I get:
Traceback (most recent call last):
File "pywallet.py", line 2316, in parse_wallet
item_callback(type, d)
File "pywallet.py", line 2716, in item_callback
json_db[type] = 'unsupported'
File "pywallet.py", line 111, in __setitem__
return super(Bdict, self).__setitem__(bytes_to_str(k), v)
File "pywallet.py", line 90, in bytes_to_str
return k.decode()
UnicodeDecodeError: 'ascii' codec can't decode byte 0xa1 in position 0: ordinal not in range(128)
any ideas?
Hello I have an old wallet.dat file from 2011.
When I run python pywallet.py --dumpwallet --wallet=wallet.dat > ~/wallet.dat.json
I get:
Traceback (most recent call last):
File "pywallet.py", line 2316, in parse_wallet
item_callback(type, d)
File "pywallet.py", line 2716, in item_callback
json_db[type] = 'unsupported'
File "pywallet.py", line 111, in __setitem__
return super(Bdict, self).__setitem__(bytes_to_str(k), v)
File "pywallet.py", line 90, in bytes_to_str
return k.decode()
UnicodeDecodeError: 'ascii' codec can't decode byte 0xa1 in position 0: ordinal not in range(128)
any ideas?
When I run python pywallet.py --dumpwallet --wallet=wallet.dat > ~/wallet.dat.json
I get:
Traceback (most recent call last):
File "pywallet.py", line 2316, in parse_wallet
item_callback(type, d)
File "pywallet.py", line 2716, in item_callback
json_db[type] = 'unsupported'
File "pywallet.py", line 111, in __setitem__
return super(Bdict, self).__setitem__(bytes_to_str(k), v)
File "pywallet.py", line 90, in bytes_to_str
return k.decode()
UnicodeDecodeError: 'ascii' codec can't decode byte 0xa1 in position 0: ordinal not in range(128)
any ideas?
Hello, I was given a wallet.dat file from a friend to try and recover anything on it. I am using pywallet. I have no idea what any of the public addresses are associated with this wallet. This wallet was also supposedly made before wallet encryption was mandatory.
When I run python pywallet.py --dumpwallet --wallet=wallet.dat > ~/wallet.dat.json
I get:
Traceback (most recent call last):
File "pywallet.py", line 2316, in parse_wallet
item_callback(type, d)
File "pywallet.py", line 2716, in item_callback
json_db[type] = 'unsupported'
File "pywallet.py", line 111, in __setitem__
return super(Bdict, self).__setitem__(bytes_to_str(k), v)
File "pywallet.py", line 90, in bytes_to_str
return k.decode()
UnicodeDecodeError: 'ascii' codec can't decode byte 0xa1 in position 0: ordinal not in range(128)
any ideas?
When I run python pywallet.py --dumpwallet --wallet=wallet.dat > ~/wallet.dat.json
I get:
Traceback (most recent call last):
File "pywallet.py", line 2316, in parse_wallet
item_callback(type, d)
File "pywallet.py", line 2716, in item_callback
json_db[type] = 'unsupported'
File "pywallet.py", line 111, in __setitem__
return super(Bdict, self).__setitem__(bytes_to_str(k), v)
File "pywallet.py", line 90, in bytes_to_str
return k.decode()
UnicodeDecodeError: 'ascii' codec can't decode byte 0xa1 in position 0: ordinal not in range(128)
any ideas?
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Has anyone tried using SimpleMining with the TB250-BTC board? I can't seem to get more than 3 cards working without getting PCIE bus errors and I've tried most troubleshooting changes in the bios.
I just want someone who is living proof that someone is using this board with simplemining OS, who is using this motherboard and can you list the bios settings any other settings you've changed in order to get 6 cards running ?
i've found that adding a linux command 'pci=nomsi' gets rid of the error messages but i'm unsure of how healthy / stable that is.
I just want someone who is living proof that someone is using this board with simplemining OS, who is using this motherboard and can you list the bios settings any other settings you've changed in order to get 6 cards running ?
i've found that adding a linux command 'pci=nomsi' gets rid of the error messages but i'm unsure of how healthy / stable that is.
does anyone have any idea what mobo bios settings to enable to get 6 cards up and running? At the moment I can only get 5 cards running without oc, when I oc them through simplemine, it says there are no OpenCl devices available. Please help
Hello, I'm having some trouble configuring the z270gt6 motherboard to run 6 rx480s on simplemining. Is anyone currently using this board to mine with? I get pcie bus errors and cannot run more than 5 cards stock oc, when I overclock them I get spammed with an error message and the hashrate gets really low, any help or anyone experienced with this board for mining can help?