it should have downloaded the wallet.aes.json into the same directory as the download-blockchain-wallet.py script. You can either copy it somewhere else, or not... as long as you know where it is. Then you just download, extract and run the wallet decryption tool from here: https://github.com/blockchain/my-wallet-backup-decryption-tool/releasesClick the "Choose File" button and navigate to where you saved the wallet.aes.json file... enter your wallet password (and 2nd password if you have one)... and then click the "decrypt" button. It'll load and decrypt the wallet. You will likely need to click on the "View JSON" link to see something useful:  You should then be able to see the "raw" contents of your wallet... including seeds, xprvs/xpubs... and (hopefully) the relevant details for your address that holds the 3 BTC:  If you don't see any private key relating to that address, then I'm afraid that your chances of recovery are going to be pretty much nil... unless blockchain.com support can offer some insight (which it doesn't sound like they can). |
|
|
|
Oh... that is likely to be a Python 2.x vs Python 3.x issue. As per the btcrecover install guide, you need to have Python 2.7 downloaded and installed and NOT Python 3. What do you get if you enter the following command? If it doesn't say something like "Python 2.7.x", then that is most likely the reason you're getting that "SyntaxError". NOTE: The latest version of 2.7 (2.7.17) can be downloaded here: https://www.python.org/downloads/release/python-2717/ |
|
|
|
where should i put eg vps_wallet.dat file? in bitcoin core program files or in my bitcoin core files wallet folder?
You should put it in the bitcoin core files wallet folder (where the other wallet.dat file is on your Windows machine) can i send bitcoins via ubuntu linux rpc VPS directly to any bitcoin address? what should i put in my bitcoin conf in my vps rpc to be able to send bitcoins directly there if it's possible?
I don't see why you can't just send the bitcoins directly from the VPS, if all you want is to just move them. I don't think you need to put anything into the bitcoin.conf file on the vps... you just use one of the various methods for creating/sending transactions... like the sendtoaddress rpc command. refer: https://bitcoincore.org/en/doc/0.18.0/rpc/wallet/sendtoaddress/ |
|
|
|
Can you post the errors here? Either copy/paste or take a screenshot and put it on imgur.com (or another image hosting service) and then post the link to it. That way, myself or someone else reading, may be able to assist with getting it running. I know the script still works, as I've just used it to successfully download a blockchain.com wallet.aes.json... and then decrypted it using the blockchain offline decrypter tool I linked above. |
|
|
|
no im having a hard time getting the wallet.aes.json i downloaded everything just not sure if i'm doing something wrong. Yea blockchain support keeps giving me the run around its annoying
Are you getting errors when attempting to use btcrecover? Or is it some other problem... like it does nothing when you run the script etc?  |
|
|
|
It's the fact that the specific rule was stated in the giveaways channel prior to the giveaway roll taking place and it's really as simple as that. If we did not make a clear announcement of the giveaway rule before the draw, then I would understand further to the point to give proper compensation to sed individual, but the rule was posted before the draw. And that's the problem... I can't see any evidence, either way... ¯\_(ツ)_/¯ Messages have been edited (or possibly deleted?)... So, I don't see any evidence of any rules being posted in the channel except for the "anyone can enter" rule that was posted back in November. So where was it stated that new accounts were not eligible? Was it in the Giveaway announcement post that was made on Dec 15th (and later edited on Dec 25th?) Or are you saying that the comment you made just prior to draw was the rule being posted? If so, that's pretty much "bait and switch"... "hey come join our giveaway and check out our site etc!" *** 11 days later *** "oh, btw, new accounts are not actually eligible... ok the winner is XXX" That's not a great look tbh... But, just so we're clear, I don't believe there is solid evidence (unless someone has a screenshot of these "rules posted above") that proves nor disproves the OPs claim... |
|
|
|
How to use that? @HCP Pls. PM, would like to have that thanks, but I think its designed for Mods, am I right?
All the instructions are posted in the thread/posts that I linked... It isn't just for Mods (I'm not a mod)... basically, the buttons appear in EVERY post... If you see a "shitpost", you simply click the appropriate button... In the background, it will open a new tab (basically opens the "Report to moderator" link), it then fills in the "Enter comment" textbox automatically based on the button you clicked and then, after a brief timeout (to enable you to cancel if you click the wrong button by mistake), it will submit it. It is very useful if you find yourself reporting a lot of posts for the same reason... you can simply add in another button with the "reason" and then a single click will report the post for you. |
|
|
|
The rule was stated before you had won your giveaway, you can check the time stamps in our discord channel "codes": https://discord.gg/M2kq6xThe "codes" channel has nothing in there relating to this... it's just a bunch of promocodes being posted... how does that relate to this claim? In the #giveaway channel it is hard to see what the original rules were because the original post has been edited... and/or it looks like posts have been deleted. There is mention of "rules posted above apply"... but there aren't any rules posted there that I can see??!?  In fact... the only thing I could find "above" that looked like "rules" was a post on November the 1st... stating that "anyone could enter":  What I can see is that you've now added a #giveaway-rules channel... TODAY:  |
|
|
|
I compiled a Windows version a long time ago... but I never compared hashes as I think it may have been before the builds were considered "reproducible"... or, more likely, I was just lazy and didn't bother checking!  |
|
|
|
|
Using Bitcoin Core v0.19 on your Windows 10 machine, it should be as simple as:
1. Copy wallet.dat from VPS to Windows 10 Bitcoin Core datadir, but name it to something other than "wallet.dat"... eg. rename the copy to vps_wallet.dat
2. Run Bitcoin Core on your Windows 10 machine and let it fully sync.
3. Once fully synced, use "File -> Open Wallet -> vps_wallet.dat"
Bitcoin Core will then open and rescan the new wallet automatically. NOTE: it might take a looooong time for the rescan to finish.
Once finished, you should be able to see all the transactions/balance of vps_wallet.dat and be able to spend them (assuming that the vps_wallet.dat actually contains private keys)
|
|
|
|
If the file isn't encrypted... (ie. no wallet password), then there was a method that you could use to scan the wallet.dat file for "names" (it would be the actual addresses in string format, as opposed to public key/hex etc) and you could use the address prefix to work out what sort of coin you were dealing with. ie. 1 = Bitcoin, L = Litecoin, D = Dogecoin etc. This stackexchange link has a couple of options to do it using either pywallet or the gist script mentioned in one of the answers: https://bitcoin.stackexchange.com/questions/19589/how-to-determine-what-type-of-coins-a-wallet-dat-containsIf the wallet is encrypted, it might be a bit more difficult... although pywallet might still work. |
|
|
|
Could always try installing Windows 10... and then setup the Windows Subsystem for Linux (WSL) and then once it is setup, you can try and install Ubuntu (you can basically just goto the Microsoft Store and click "install") and then try running Bitcoin Core using that.  |
|
|
|
Do you guys look at any other fee estimator websites?
I usually go to the jochen-hoenicke site and check the graphs there: https://jochen-hoenicke.de/queue/#0,24hYou get a pretty decent overview of what the network is doing... plus by hovering over the very right hand side of the graphs, you can see the numbers of transaction at each fee level... and on the bottom chart, the actual "size" of transactions at each fee level... and then I adjust my fee as necessary to suit my needs. Generally, I'm never in much of a hurry, so just go with "1 sat/byte" stuff (with RBF enabled) and just wait I've had one or two occasions where I needed something transferred in a hurry and wanted to get nextblock confirmation... so I set the fee to end up within the top 1meg of transactions and it worked. But if the network is very busy/volatile, even that isn't a guarantee if 10,000+ transactions popup before the nextblock!  For instance... if I saw this:  And needed nextblock or close to it... I'd probably aim for that ~0.5meg region... so I'd got 12 sats/byte |
|
|
|
user@user~/Downloads$ gpg --verify eps-v0.2.0.tar.gz.asc electrum-personal-server-windows-release-v0.2.0.zip.asc
You're not verifying what you think you're verifying... You're trying to verify one .asc file, using another .asc file!!?! You need to verify the matching binary file that goes with the .asc (ie. the ".tar.gz" or the ".zip")... Try: gpg --verify eps-v0.2.0.tar.gz.asc electrum-personal-server-eps-v0.2.0.tar.gz
or gpg --verify electrum-personal-server-windows-release-v0.2.0.zip.asc electrum-personal-server-windows-release-v0.2.0.zip
Theoretically, you could just use "gpg --verify the_binary_filename .asc"... but ONLY if the .asc file has exactly the same name as the .zip file... so, it'd work with the windows_release .zip... "electrum-personal-server-windows-release-v0.2.0.zip.asc" == "electrum-personal-server-windows-release-v0.2.0.zip" + .asc So, this works: gpg --verify electrum-personal-server-windows-release-v0.2.0.zip.asc
user@user~/Downloads$ gpg --verify electrum-personal-server-windows-release-v0.2.0.zip.asc gpg: assuming signed data in 'electrum-personal-server-windows-release-v0.2.0.zip' gpg: Signature made Thu Dec 5 23:57:57 2019 NZDT gpg: using RSA key EF734EA677F31129 gpg: Good signature from "Chris Belcher < false@email.com>" [unknown] But, it won't work with the .tar.gz as it has a different name to the .asc "eps-v0.2.0.tar.gz.asc" =/= "electrum-personal-server-eps-v0.2.0.tar.gz" +.asc  user@user~/Downloads$ gpg --verify eps-v0.2.0.tar.gz.asc
gpg: no signed data
gpg: can't hash datafile: No data
You could also just rename the "tar.gz.asc" from "eps-v0.2.0.tar.gz.asc" to "electrum-personal-server-eps-v0.2.0.tar.gz.asc" and then the command would work: user@user~/Downloads$ gpg --verify electrum-personal-server-eps-v0.2.0.tar.gz.asc gpg: assuming signed data in 'electrum-personal-server-eps-v0.2.0.tar.gz' gpg: Signature made Thu Dec 5 22:51:58 2019 NZDT gpg: using RSA key EF734EA677F31129 gpg: Good signature from "Chris Belcher < false@email.com>" [unknown] |
|
|
|
My Bitcoin Address: 3DGjbDjNhtfHze6Rq6N9gVoa3pB119hee1 MY PGP: -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: Keybase OpenPGP v2.1.3
Comment: https://keybase.io/crypto
xsFNBF4BGpsBEADLddc1JIz9QWEZ8y+dhP9jgirY/GybhLzX8+nvXGKOsDnoUC7u
mXc9sqpd4wUbmal4Ijr8zT7qrrYHyTdYwbeaO6Lh/q1Nzr/frjhCwoKEIu1OHQ6g
ssq/7NHCK0ucGGjZN8mYB+elboSpqrc3kxCE2BzBqcCv7xUyU29p3L5fZvIrSmPi
9ROOEJ5Egm549dgp9SBhma3kWuZwhXR1wAoaoTP8Y1ZL6uDmfGDJLzm9dbMZ1HWW
7SjWXthIWqivvvnXY0BreFPGDDynL4rYILscuMFnGxzmgADyfZsd5gJj5Opu6QUQ
Z9D6XnKB87PqHJg9PBG1lj9OeL+V4Q30acl1AiXbPe9hEHh3oXFVX3j9Mj0zF7JF
r0fF1Ky3RBjexVBJovFMjrxYgvVu9QDOHAYblnerhjiKK8tSGJ/zcgsN9ppX57xQ
0uufMQIlKnTwKh5dosmwBO8cV9VF0Yv+h291tTdAFhaHLW2huSIAYnxxsEQMfr4h
Chf+8BMdHJ2gh+EsfPAKJazF1QrT8JNTDI/RbIyp21cw2ZdWbiF2eucMGfvs6Gs8
HMChYBImS5qCdwPZqBs+08tJ7pMGafD6g+XZgDvA80QL6MtRIROMG1kqWsH8UPTt
3eFPQy1y5KJptlQMCe8axfo9IcGq83s95sHtbR/cGKgEUQJ/PdKXM1fiUwARAQAB
zRdBZ2VudEYgPEFnZW50RkBmYmkuY29tPsLBdAQTAQoAHgUCXgEamwIbAwMLCQcD
FQoIAh4BAheAAxYCAQIZAQAKCRDb9vYA730ny0MDD/wIsg6uB1n8OML/ht7deJSK
6+CVp6mX+cfG/ZpVFFoDUw4QYz919gRiuMysQsHeXGigtOdcoAxYKxBPvDWRPOfp
qz76Wo31FWnLNyiFZ/R63ja8hCJoIqfcBTEyqFuGiVhFPLmPcxC54wntY4D26uUI
1MTFWVIwECjV/cMzbvdxswAAALT2X/uFdvB25ktlrWdsb74wwxf7nCHQaNjkqFtu
7vXdtGD0mCGxYXVPqv8gqC91LTm1Ih4+uoMDlwGRnrMvaJWoYGRopFN4k1oekU/Y
EK7EpkuVZXMuswqzZJYOaNqOsKbcv8yuXR6XRf6tcDcsCtdEWeD7j4md0+qdP+Wv
N0LiwEV0RCvxqgwFK2V+yHzGnzJiY9Od7Gpqq/y/aCWvzycqDSOMabstfRsKXRTf
P6SfU9z6ErKfKidEOpWE7Yv9HQU9A/82IZWOkTryJICw6vlwpztBgb3/DLBetEkf
Qiuciu+7hINGqHCuHC0xOC6xlWT54Rja5E5DCe0ToIKVswr8U9hdrjGu2UBMdY3l
VEpHC0L+Thi00wRtYB4/sXZfIrQNyF7nAvKknbVys9vylkdcpultBtktSAt12egK
4KUcJcRUEgtbRFKHx5VdOkjLHkrHEWD22ChtsiIbfJVcmo65pWqYHgkpeC6A76kx
BOl5JJOcUWwUdEONb0EiN87ATQReARqbAQgAtgaGPLeppUmNS7WuvdxR2jPef+zP
exgZTFiRE2A4vb1Pc4r5fsrjvHlIXJqPjAJbowsK2SH3XaFFFoFdR+qAMzjcSaTE
TAeIEPYSjG3rt60PqA+dPkOoe5p/55AtRGIUE7ANvCM5DCAzeeOGGMqOIvfw6OLE
t0bavnWWqt+ctGZk+AbyvDbS7Jl5Cj+7tcPPSQ7JNLDvXM+ZnRi0nvHc1V0hCDyz
8LrzLPIve71C7xjFOiqFcRv2Htaj9kWtJ3fJv64a8DOBItoMYhCK3/yKDGsdTBqv
2sGhb0wWOO+gmxyseZ4H1z0FKywKb2dDDprUYGEFThQb6cVXUGw29VwORQARAQAB
wsKEBBgBCgAPBQJeARqbBQkPCZwAAhsMASkJENv29gDvfSfLwF0gBBkBCgAGBQJe
ARqbAAoJEOrlisV/jl/GAQsH/iNZybpRDPeQbxOvIxGcoAJ4+UoWr6/f+bfJ6lWa
QMClGjMyPkwnnQq/ZrlyRf/0miy7A6FtfNG33D2Dl8ETgjh3H+9bwEP+t0aHBoeE
U4bR7QOzshDducyxFiiOjoUl5nMJFdWxqjfFAIn2TS7kDuY8hz2XEDv7tTS4pSJG
3RoI9JCVYXCoPchs7cy6rhCI2vq9A1tovTWeFqG8maocE8oF3Z4CGtZbOPHSI6uV
ycRoOS+8Krv5G7ivyYLH7nbWMHhnOITScOngm8cojM6VmCoh3ES/M3HTTAKua9+w
EqyF45pwElLFNdFgRsEiZ7YQg7/fw8EKdCAkUsWdR9tM/SuE+xAAu+KxnT/w62lv
4bCeD4ZbL8PJi8na4tl0/y4yEN46lA3SwmGMAt5evDGeFx24FXLLWGpDp+Wg6HNk
rCPVyxZCSi3Xsh4TL7nlN6cgoYSk2Pj8cCX8g2um7F5ULFrbf5RwG31n6ybTjPBh
0kmz6fso3Ohd98dVPyVFxNranjIbN8mlPhkGbnEveC2Y50iXs2LB9jzvdEQl6OV3
96z77LD4rgBY3P/qnxuuBKtgPYb3q/Mlcqf1BADwaLgNQ/lBdGAgAoIBbam6qvUc
RtHpJ3BPz4gLZ50lIzMBTzCC9ZVA3756tqDZ+/9HlkOn09i54aPpsULGw6q7pkF5
KHaKv1PW92j+zvrjsBMbnFrkhWGXs4zBZ1L5bhaC53ldPjaVVi7GoiFJnF8d62f+
azpSIXxfrK8O6R3TRTeTkPhmlCLkSBr7Kg1ENQ4zj0wO9y6x+vpiB3C2fbKq00P5
tyA4lfyxi3f0Qy4U/2vsTFHL/XZrPrEG7diG7bMVV4t4CHL1PQsaY2USrDFxKWrc
f0q9w8KKVhTuZo8PYyGd77uZBanlpjAjuS+nIkkK/fNsvrjKSyPWb2OwCiXyyHGv
q1pRjYynTfkrEZdNQZEJScwXrQnOxRsGw3F3FIj1xvJPqUKuQVSiB19XkMEfNCIO
AQOIXB0VAPNsUkxSi/J0qsW5vW0+8mPOwE0EXgEamwEIALszt4PZFrCJ31TpnIkP
Dz+AcEZq5Lmp9hdf4E4pm7MiG9wjC2LoRHQ3VUw0ScWDg6WQiraNbfj1u2d+kZmO
J8KKWfo7wn7tcVX0QWyC4wyOj6BOY4GNMChIp3XZ1MxU26aoasH+4nWW7YgyyQWR
qweOhA79kOfg7aHgraVexDcrIn5C6uE+Efzg77BaozYlUxAGF22CKr8ecr50jb2i
nLASXDJTeS1fAfJUFms8SxEYkLl9/lnKWZ2Sag1LCtNcE6dESM+DX9Pgl8qKTJ7q
fdPGBqq+f+ETSqjqhNwyOMzFIXvQ00xAWjrMLq6+Fy8C8H+ag/2DlGq4hVqn+xXI
yc8AEQEAAcLChAQYAQoADwUCXgEamwUJDwmcAAIbIgEpCRDb9vYA730ny8BdIAQZ
AQoABgUCXgEamwAKCRD9LqCyjX85h5jYB/kBzpc3NRL+HzVH8a9bB9fIr5eXz7p1
xxQxyGq2kw+lcBtzJMBSp6MUGoL0JP/VDqLZFN8H4YpA0TSOZ++p9Xa6AkOuSgkF
rYMVeSemuqtld0xPueZeHrxhyPuvR4GNwRkJ3evrwEFvuN/gV8v9Prt+/vDAwOXw
YbdmlR0tK986a+rBNCkRNqFUqXCBG9liBVd0JMpvT4c+LG7sr1VcU3ZaJ0lvl350
mmqFFKkYs5l7+/CJnpADhZPbDOzDqt/S2PZPjND7PS2SSlw39aAuv941FTktWxWy
8TbwmVo1li32I91b9VwqgfPmawW8KUJsZehe3EXeT4aKHpCQQ6mhGiBHC10P/0hf
bCuY2R6fRFwgXk09OWoYKamPYTjCoR07g1NCGtYfXsXC6oRQqZnPZHQVdO7jxhE3
+QNqyzhk6HosRBGPSfXtLyuU4k53x3Y1aim/TwLRKaG3xXc5vZXwDV9NMr8j8gNn
GZzbjs+Xjt/NdnuDDdG70j21SUDziEwnCRxkVFyCkV0gREl642fLCvcPUzpvPefz
fSO4LL1ZuUM0wMUfgpeI1CIuChDezyJy1N4CsUsn/uXpxnDvs0k5DwmTENH89N2T
O6PKXWLj+tFtqB7hj3drPXzWIBRS4QiS3lGXr5JLGlX4UNQfNBARcvBeewLGmF30
ztFjWHMtCPaOmZy6FhAjVecY4DOSRv8N9DxElWILh96dy6/MU5XVj8CwqCfPfYWT
xgPJAchWKlJngF0UGFyqyqbsQ2ATozXjKiamxm8XRtSkBU9l1+3x9+wPl/2+C1lA
SNjDQLCufw+dtkFtlL7M1PAKW7foPrjIVzcS9ECZoVFL6I0B/ELuNgxKsupLaHzB
3FCQiR180bWY9tlqSjjZAJRTU5zuWIuperIiKEi0+ooeLygH5UQPGIOtB5tN6d55
lkpqIav9OFDMQjPUtaBmPtkxkMWB0yQ4nZy1YlKn8tLllSZjig169Tn7zyRy+VCM
H0ZoB8nvtvVtg47CwNOkjd8e6IUnLVZg8rutmPE7
=N1Yu
-----END PGP PUBLIC KEY BLOCK----- Quoted, but you might want to sign a message from your Bitcoin address as well... and/or provide a PGP signed message so they can be verified. |
|
|
|
They might get a slightly bad rap these days due to the takeover and integration with ShapeShift... but FREE is a pretty good price! krogothmanhattan is running a free raffle for a KeepKey: https://bitcointalk.org/index.php?topic=5211648.0I advise to also check the last couple of posts to see the most up to date list of free slots and also what slots have been taken since... at the time of posting this, there are around 15 slots left. |
|
|
|
|
It seems like that would be a "permissions" issue of some description.
You'll need to double check what user/group the app/process is running as, and what permissions the various directories have. It's quite possible that your user/group doesn't have read/execute permissions for anything higher than the "common" directory. That could explain why the app is unable to browse those directories.
|
|
|
|
|
Show Posts
