Latest posts of: ice2097

Show Posts
Pages: [1]

Economy / Services / Re: FREE ☘☘☘ Bitcoin Transaction Accelerator for Unconfirmed Transactions ☘☘☘

on: January 18, 2018, 12:46:17 PM

Can you please accelerate: 6f79d7b34c46e6ec2595d842d70335d95cb6f9aaa395830d78a40d308eb78067 Thanks!

Economy / Services / Re: ga

on: January 18, 2018, 12:36:59 PM

Can you please accelerate: 6f79d7b34c46e6ec2595d842d70335d95cb6f9aaa395830d78a40d308eb78067 Thanks!

Economy / Services / Re: [Fast] Bitcoin Transaction Accelerator| for unconfirmed transactions -Hooli1.com

on: January 18, 2018, 10:16:24 AM

Can you please accelerate: 6f79d7b34c46e6ec2595d842d70335d95cb6f9aaa395830d78a40d308eb78067 Thanks!

Bitcoin / Development & Technical Discussion / Re: Pywallet 2.2: manage your wallet [Update required]

on: June 26, 2017, 08:31:50 PM

Quote from: HCP on June 23, 2017, 03:54:41 AM Sorry for the delay... I suspect that either the wallet is badly corrupted or it is indeed encrypted and the password you are using is wrong, hence the script being unable to read it properly... Especially in light of the message you're getting from current Bitcoin Core saying that it is corrupted. I'm wondering if could be struggling with an old wallet format? What version of bitcoin-qt were you using originally with this wallet? Yeah, I think it probably is a very old version... I think the wallet was started around 2011 or 2012, but I'm not positive.

Bitcoin / Development & Technical Discussion / Re: Pywallet 2.2: manage your wallet [Update required]

on: June 20, 2017, 05:42:14 PM

Quote from: HCP on June 20, 2017, 01:30:37 AM Have you tried specifying the full path to the wallet file rather than just . ?? It's possible that the script is attempting to parse this as a full path and may not be locating the file correctly? I haven't looked at the actual code to see how the script is handling the --datadir argument, so I'm not 100% sure of the format required here. When I get home from work tonight I'll have a proper look and and a bit of a play around with it and see if I can replicate and/or figure out some more specific solutions for you. Yeah, unfortunately I've tried the full path as well, and get the same response. I don't think its an issue with the path, as if I put in an malformed path I get a different "`bsddb.db.DBNoSuchFileError: (2, 'No such file or directory -- /Users/user/notpywallet/__db.001: No such file or directory')`" error.

Bitcoin / Development & Technical Discussion / Re: Pywallet 2.2: manage your wallet [Update required]

on: June 18, 2017, 09:16:38 AM

Thanks for the fast replies! Quote from: madmartyk on June 17, 2017, 07:51:18 PM Have you tried to import the keys you have found? No, sorry, I don't really understand the format of the output: `{'\x00\x01\x03key': [`(Here there is a list of 142 comma-separated 5- and 6-digit numbers, in ascending value) `], '\t\x00\x01\x04mkey': [], 'PRFdevice': './wallet.dat', 'PRFsize': 139264, 'PRFdt': 0.02301478385125293, "'\x00\x01\x04ckey": []}` Is there something I can do with the list of 5/6 digit numbers? Quote from: HCP on June 18, 2017, 03:55:52 AM You likely need to use the following commandline options to get it to point to the wallet.dat you want to work on: Sorry I should have been more clear, I'm running this on a computer that doesn't have any bitcoin software installed, just the wallet.dat file from my old computer, and pywallet. For the wallet dump the command I ran was: `$ python pywallet.py --datadir=./ --wallet=wallet.dat --dumpwallet --dumpwithbalance > keys.txt ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.` I've tried changing the permissions of the wallet file with chmod, and running the command as sudo to make sure its not a permissions issue, but it still gives the same response... Quote Just as an FYI... Recover is used when you're effectively scanning a drive to try and find accidentally deleted wallet files and/or keys... it probably isn't what you want to be using... --recov_device needs to be set to a disk (ie. harddrive or maybe usb). The --recov_size is used to specify the size of the device in Gigabytes... Ah good to know. Thanks for the clarification!

Bitcoin / Development & Technical Discussion / Re: Pywallet 2.2: manage your wallet [Update required]

on: June 17, 2017, 03:15:54 PM

I'm trying to recover an old bitcoin wallet.dat from ~2011 or so. I tried loading it with the current bitcoin-qt, and just get a "wallet.dat corrupt, salvage failed" error. I didn't think I had a passphrase on my wallet, but I'm not positive. I'm trying to use pywallet to get something usable out of the file, but I'm having some trouble and would really appreciate any help anyone here can provide. I have the wallet.dat file in the same directory as pywallet.py If I try to dump the wallet, I get: `ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.` If I try to recover, I get: $ ./pywallet.py --recover --recov_size 30.1Gio --recov_device ./wallet.dat --recov_outputdir ./rec2/ Enter the passphrase for the wallet that will contain all the recovered keys: q Enter the possible passphrases used in your deleted wallets. Don't forget that more passphrases = more time to test the possibilities. Write one passphrase per line and end with an empty line. Possible passphrase: Starting recovery. Read 0.0 Go in 0.0 minutes Found 0 possible wallets Found 0 possible encrypted keys Found 141 possible unencrypted keys Segmentation fault: 11 at which point python crashes.... I'm not really clear on if these 141 keys should be useful or not... also I have no idea what the recov_size variable means, so this could be incorrect. I'm not really sure where to go from here... any suggestions would be highly appreciated!

Pages: [1]