How to Easily Recover Old wallet.dat Private Keys With ...

Recovered private key with Pywallet can't import into wallet. /r/Bitcoin

Recovered private key with Pywallet can't import into wallet. /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

This obviously isn't reaching anyone

This obviously isn't reaching anyone submitted by themusicgod1 to Bitcoin [link] [comments]

Can any one tell me how to i can transfer my multibit offline wallet to an online blockchain wallet...

submitted by amitahuja1995 to Bitcoin [link] [comments]

My first experience with bitcoin was NOT positive :( + Questions

After seeing an interesting comment on /funny in which bitcoin currency is used to make tips across reddit I started to investigate and learn about the Bitcoin. I had heard about it before but I didn't know how it worked or what I had to do in order to use it.
A dozen Bitcoin Wiki entries later I download bitcoin-qt and create my first wallet. The system seemed very easy and straightforward and I had already started to apply for "free starter bitcoins" when I met "synchronization".
Now synchronization is not necessarily a deal breaker but it was annoying as hell. I'm using an old computer and it seemed as if it would take at least a day if not more to complete the whole process... and during that time my computer was getting slow as hell.
Now I'm quite a tech savy person and I know why in this P2P based system this is important, but for anyone else this would be unacceptable. Imagine elder people or not so tech savy persons trying out the system for the first time and noticing that they can't use it without occupying 2+ GiB of their HardDrive and having to wait a lot.
I did not complete the sync and tried to use the multibit instead. But since I had already applied to the Free starter bitcoins on some websites I wanted to keep my old wallet. I try to look for an import/export button but it seems that Bitcoin-qt doesn't support exportation and I needed to use a third party application called pywallet (command line!) to export my wallet and convert it into another plaintext format since the format used by bitcoin-qt was not supported by multibit.
And one would assume that the first thing you do when creating such a currency is to define a standard for the wallet and the applications. Again, I know how to use the command line but anyone who doesn't and who just wants to try out the system for the first time would be inmediately turned off by this limitation.
These are all issues that need to be fixed and addressed. Also, at the current situation it is much more comfortable and easier to set up an e-wallet than using standalone software on my computer. And if you ask me, it beats the purpose of creating a decentralized currency when in the end the most popular e-wallet services are going to hold most bitcoins and suppose a great security risk.
So I ask you: do you know any solutions to the above mentioned problems? Is there any way to reduce the impact by those hindrances?
And now to the questions:
Since I'm a very inquisitive mind and I'm still very much interested in bitcoins I would like to ask some questions I couldn't find properly answered in the wiki about the nature of the bitcoin system and how exactly it works.
I'd be very grateful if you could answer any of the following questions:
1. What exactly is a bitcoin? A string of text? A hash? A file with a string of text?
2. If I'm not mistaken, a bitcoin wallet is made of a public key and a private key. If I want to transfer my wallet from one program to another or a piece of paper... would I need to export or print out the strings of text that form the bitcoins itself or do I just need those two keys?
3. How does the bitcoin system know how much balance is inside an wallet/account. Does it typically ONLY check it against the chainblock or does it also make use of any bitcoin strings stored inside the wallet?
4. Cryptographically speaking... what happens when I transfer bitcoins?
Thank you!
*Please don't downvote me just because my first experience was negative. I'm still very interested and would like to learn a lot more. *
Edit: Thank you very much for all your answers! I can't reply to all of you (mainly because it's very late over here) but I feel that I understand the concept much better and also feel much more comfortable knowing that the only thing I ever need is my private and public key. It makes me care much less about software and files, knowing that I can have everything I need written on piece of paper or saved in an encrypted file of my own. Then, when I need to spend bitcoins or check my balance I can use whatever software I deem best at the moment.
Thank you!
submitted by DanielTaylor to Bitcoin [link] [comments]

Wagerr mainnet wallet password not working but it is the RIGHT password.

I can't unlock my wallet.dat anymore. I'm sure it is the correct password. To test if it is the correct pass I used I extracted the hash with and got some hash in the style like this $bitcoin$96$d011a1b6a8d6................. as hash
Then I used hashcat with the 11300 type and a wordlist with only my password to see if it was able to crack it. I let it run and it gave immediately the status "Cracked". Tried it with another password and it didn't work.
So It has to be the correct password right? What else could be wrong here ? The wagerr client keeps telling me it's the wrong password. Is something wrong with the wallet.dat ?
Any help is welcome.
UPDATE : we managed to get de private key by adjusting code. Only a part could not be decrypted. I guess it somehow messed up closing the program. So the wallet.dat was corrupt altough it loaded fine. UPDATE 2 : we managed to create the WIP private key and import it into a new wallet so funds saved ! We will provide the pivx team the corrupt wallet so they can investigate it / debug it together with our procedure how we extracted the keys. As Wagerr forks from pivx we contacted them. If wagerr team wants the corrupt wallet.dat please let us know.
submitted by lordraider to Wagerr [link] [comments]

Recovering unencrypted wallet from 2013

EDIT: I've been able to export my details from Bitcoin Core into a format I recognise, with addresses marked with dates corresponding to the last time I was doing transactions. Now to see which ones have any money in them!
Hi all,
So after seeing the price of Bitcoin I immediately thought back to my wallets. I backed them up years ago. But they will not import into any modern wallet software (some just hard crash.) The software I last used with these wallets was Bitcoin QT.
I was able to extract a .json file from this backed up wallet.dat using pywallet, but I have no idea what to do with the resulting data. I read about Electrum having a "Sweep private keys" function, and about using Bitcoin QT to dump private key information. But since no receive addresses are showing up in these old versions, I have no idea what to dump. I tried my best at importing the private keys from this data after matching one private key to some Bitcoin QT output, and put all my private keys into the sweep. However, it says nothing was found and my balance remains at nothing.
I cannot find what my old BTC address was, so I'm unable to check if the funds are still there in the wallet.
Is anyone able to give me some steps on how to get this loaded into a modern wallet? Nothing I've tried so far works.
submitted by DaedalusRaistlin to Bitcoin [link] [comments]

What is the most efficient way of checking the balance of 10k+ addresses without having a full copy local? Or can I rent out a full node?

I am currently running a pywallet --recover on the entirety of my mac hd that was used since 2013. i previously scanned stuff like the windows VM i used most of the time and a timemachine image from late 2013 and was able to check the balance by tediously grepping solely the addresses into a newline seperated file with only addr's and used the unix split function to create 8 different 1k lists.
I would then import these as watch only into electrum but even with only 1000 electrum takes a really long time to sync (and as far as i can tell theres no log file to allow me to indicate progress. my network monitor often shows no data transfer leading me to believe that electrum is quitting querying)
I would like a solution that is both stable and efficient. You could query online api's but they rate limit real fast and even utilizing multiple ones, you're bound to hit the limit fast on 80% of them pretty quickly.
Also keep in mind that every bitcoin private key has both a compressed and uncompressed address so while pywallet may say 100 keys, its 200 addresses to check.
I also would like to be able to check this every once in a while to see if any of the addresses have seen new activity. Maybe every month or so, so i'm willing to wait an hour to do it but I would like to have some notion of progress and no ambiguous malfunctions like i experienced with electrum.
What I have used so far (and some might find useful for smaller amounts)
Does anyone have any solution? Is there a way to download the current state of the entire network address balances? Don't need to be cryptographically sound like building up a db or something because i can check it via third party. Having a list of all addresses with balances would allow for a grep that I could run overnight. While it probably would take a while, at least theres always going to be progress and one can tell where they are at on their list.
Side question: is there a way to convert hex keys en masse (or wif if it takes the extra step of converting back to hex ) to litecoin? I'm going to assume that some of the keys recovered by pywallet are litecoin keys. I would then need the same process for the ltc network which I imagine would be even tougher.
If I find some cash (which I am optimistic about) I will send you 50$ for linking to a solution that fits my needs to all above. At minimum I will pay 25$ even if theres no cash on my end.
submitted by winlifeat to Bitcoin [link] [comments]

Recovery of possibly corrupted Bitcoin Wallet

I have a very old wallet, which I am unable to open. It is password protected, but I know what the password is. Bitcoin Core says Salvage failed.
Booted LiveUSB Ubuntu and installed pywallet.
[email protected]:~/Desktop/pywallet$ sudo ./ --recover --recov_device /dev/sdc1 --recov_size 1Gio --recov_outputdir /home/ubuntu/Desktop/recove Enter the passphrase for the wallet that will contain all the recovered keys: 123456
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: xxxxxxxx Possible passphrase:
Starting recovery. 0.10 Go read 0.20 Go read 0.30 Go read 0.40 Go read 0.50 Go read 0.60 Go read 0.70 Go read 0.80 Go read 0.90 Go read 1.00 Go read
Read 1.1 Go in 0.7 minutes
Found 1 possible wallets Found 221 possible encrypted keys Found 0 possible unencrypted keys
Possible wallet #1 with passphrase #1
Private keys not decrypted: 221 Trying all the remaining possibilities (221) might take up to 0 minutes. Do you want to test them? (y/n): y
Private keys not decrypted: 221 Try another password, check the size of your partition or seek help The wallet is encrypted and the passphrase is correct
The new wallet /home/ubuntu/Desktop/recove/recovered_wallet_1513352751.dat contains the 0 recovered key [email protected]:~/Desktop/pywallet$
So it recognizes the password as correct, but it doesn't decrypt the keys.
Please help.
submitted by CYPER_BG to Bitcoin [link] [comments]

Trying to export my wallet.dat from Bitcoin-Qt, but one of the receiving addresses (and its private key) seems to have disappeared. What to do?

I'm trying to move from Bitcoin-Qt to MultiBit. After upgrading Bitcoin-Qt to 0.8.1 from 0.7.x (supposedly mandatory upgrade/fix because of Bitcoin protocol issues), it always tells me that the block chain is corrupt and I need to rebuild it. Tried a bunch of things, it still does it whenever I start. This easily takes over a day and I want something more lightweight on my laptop anyway, so I switch to MultiBit.
Got pretty much all my BTC out of my old wallet, but I still want to import the existing private keys and (if possible) transaction records. As I understand, I need to get the keys from wallet.dat in json format, and import them into MultiBit. Should be easy enough, no?
First, I tried taking the output of pywallet and importing it into MultiBit. I choose the file, click the button to import, and it does nothing. (The wallet is several megabytes with lots of txns, so it might not have been prepared to handle that big of a file.) Of course I later learn that I'm supposed to just import the private keys, but pywallet doesn't appear to have an option for that?
So I go to, and (hesitantly) created a wallet there with my wallet.dat. It works, but the balance is short of what it should be. Since then I sent nearly all of my balance via Bitcoin-Qt with no problem, but my balance right now is 0.0004 in Blockchain and ~0.002 in Bitcoin-Qt. I export my private keys to JSON, but when I try importing them to MultiBit, I get error: "There were missing dates. Have to go back to genesis block." It refuses to let me import it at all.
Nonetheless, it turns out that my Blockchain wallet is missing one of my receiving addresses (and its corresponding private key). This address is over a year old and has been used numerous it's not unused/new and I would really like to keep control of it.
I figure my wallet.dat is corrupted somehow...the Bitcoin/Bitcoin-Qt app itself has always seemed rather flaky for me. (Sometimes it'd spontaneously quit after I sent BTC...doesn't really inspire confidence.) Maybe this is what caused the block chain problems to begin with. But I want to figure out how to recover all the private keys, not just the ones that Blockchain recognizes.
Any ideas or suggestions would be greatly appreciated. Thanks.
submitted by MultiUseAccount to Bitcoin [link] [comments]

How do I move private keys from Bitcoin-QT to another wallet without having the blockchain downloaded?

I currently access my bitcoins on Bitcoin-QT and have used a pretty good passphrase to encrypt the wallet.dat file. I would like to eventually move my coins to a paper wallet for offline storage, but currently want to get my coins over to (I set it up the account on a thumb-drive linux system with 2FA and a great password). I've read instances of people decrypting their wallet, then finding some unknown malware on their computer immediately emptying their wallets. I don't want to rely on the computer I currently have my wallet.dat file on just in case this happens to me. I'm trying to get my private keys into something like electrum or multibit using pywallet to decrypt my wallet.dat on a fresh linux system (thumb-drive again). However, the format from pywallet doesn't seem to be right to get it on electrum nor multibit.
Is there a special way to extract the private keys from wallet.dat to import them into multibit or electrum? I don't think using Bitcoin-QT on my thumb drive is an option since the blockchain is so huge and I think the blockchain is needed to do anything with Bitcoin-QT.
I didn't find too much help via google or the security guide on the right side of this page.
submitted by dyrich20 to BitcoinBeginners [link] [comments]

Question about securing your bitcoins from theft or file corruption

I recently upgraded to Mavericks on my Mac and my Bitcoin Client refuses to start up. I'm in a position where I'm not sure what steps to take in order to recover my Bitcoins. Here are my options that I'm aware of:
  1. Remove all files from the ~/Library/Application Support/Bitcoin folder and place them safely on the desktop. Then open up Bitcoin-QT and start a new wallet.dat file. Finally, open up on my browser and import my wallet.dat file and transfer the bitcoins back into the new Bitcoin-QT client. Encrypt and backup
  2. Use pywallet to retrieve private keys and then I have no clue what I'm suppose to do next
As you can see, I'm a bit lost. Will my first option work?
submitted by Shadylane318 to Bitcoin [link] [comments]

State of the Redd-Nation :: May 23, 2016

Reddcoin Weekly Development Update

Welcome again Reddheads to another weekly update of Reddcoin Development.
This past week has achieved quite a few updates.

New v2.0 Wallet and testing progress

During this last week, I have been performing testing on the switch-over logic from v3 to v4 blocks on testnet using both the version 1.4.1 wallet and version wallet. Results have been better than expected and I am very happy with the progress so far.

Network Testing with Super-Majority

The recent testing with testnet was performed by setting the super-majority to 510/1000 blocks (51%). That is, when there have been 510 v4 blocks created in the last 1000 blocks, the rules for v4 blocks are enabled (Enforce DER Signatures). v3 blocks will then be rejected by the network.
On mainnet, the setting will be updated to be a Super-Majority 85%

Staking with different versions

Wallet Staking Block Ver Accepted by v1.4.1 Accepted by v2.0.0 Rejected by v2.0.0
Ver 1.4.1 YES v3 YES NO YES
Ver 2.0.0 YES v4 YES YES NO
SOME NOTES: After the switch of Super-Majority completes, version 1.4.1 nodes will continue to stake however, the network will reject those blocks. This is expected behaviour.

Transferring between versions

v1.4.1 v2.0.0
v1.4.1 YES YES
v2.0.0 YES YES
SOME NOTES Current testing of transferring coins between different wallet versions has been successful. Current indications are that if you are not staking, you will be able to continue to use v1.4.1 wallets. More testing to be done.
If you have any questions, or would like to know more on this, please let me know.


Translations continue to be updated which is great to see. Thank you to all those who are contributing their time and effort.
@Serkan34 continues to dominate on the European languages.
This is the running list of desired languages, and if you like you can also check the overall running list on transiflex here.

Wallet Recovery

As mentioned last week, wallet recover is no easy task. There are a few tools around on the net that can help, but it is no way guaranteed to provide 100% recovery.
So, it is important that you get in the habit of routinely backing up your wallet.dat file
For the second time in as many weeks, I have used the utility called pywallet that in my case has done a reasonable job to recover broken wallets. It is a python based tool that allows some low level manipulation of wallet files.
In this second case, it involved recovering the private keys from a testnet wallet (100K keys in total). The wallet.dat would load into Reddcoin-Qt, but then the application would sit spinning its wheels, without error, and no way to dump. Running the QT application with -salvage wallet would truncate the number of addresses that should have been available ion the wallet.
So, using the pywallet, I was able to load up read the available privatekeys in the wallet and dump the keys to a text file. This essentially was the same as last week. 100% of the privkeys were salvageable
I still have some problems importing those directly into a new wallet using the pywallet tool, and with such a large number of private keys, manual input was not an option.
I wrote a little script to pull the private keys from a text file and send a importprivatekey RPC command to the wallet. A little slower, but none the less it was effective and successful.
After starting the wallet with -rescan, it brought everything upto date with those associated addresses and their tx's into the wallet.

Large number of Micro Transactions on mainnet

Over the course of several weeks, there have been a number of instances where a large number of small transactions were broadcast onto the network.
It was brought up in a couple of forum messages on reddit and reddcointalk, so I thought it might be worthwhile just to touch on it again here.
Firstly, I would like to say, this is similar to reports that occurred on Bitcoin network where small transactions were sent to fill blocks. So I was interested to monitor just how such behaviours would occur on Reddcoins Mainnet and what the effects might be.
Reddcoin mainnet has in effect a 10x larger capacity that Bitcoin. The blocksize for Reddcoin is 1M, and the block generation time is targeted every minute (Bitcoin is 1M blocks every 10 minutes).
In the 'worst' case the maximum capacity that these transactions took on the network, was to occupy less than 25% of each block (about 230K in total)
With the number of transactions that were occurring, there were at times excesses of transactions that spilled over into subsequent blocks (again, only filling each of those to 25% capacity). When this occurred,e there were runs of up to 10-12 blocks that were filled.
In the current state of the network, where volume of transactions generally is low, it has been a good exercise to monitor the behaviour of sudden peak demand. I didnt hear of nay cases where normal transactions or staking were affected.
Thats is not to say, we are immune, If the normal operating capacity of a block was 50% or more, this would be more a concern and there could be an impact to the time of confirmation of a transaction.
Suffice to say, the current side effect is, a number of you may have a lot of small transactions sitting in your addresses. I would not be too concerned at this point, and would suggest to let the PoSV staking take care of those in due course (it will take a while to get selected due to the size), or in your next transfer, manually select a few to send them on their way.

Performance of PoSV

One of the things that has interested me for a long time with Reddcoin is how the POS mechanism behaves over time.
PoSV is unique amongst the POS crypto-currencies in the way that the weighting mechanism works, and in the way the stake reward is weighted depending on how long the coins have had to age.
A lot of things can influence the amount for each of your stake rewards,
Working with @deadpool, and @reddibrek, they have been trying to define it is simple to understand terms
But I am also studying the network in much greater detail in relation to a post on the ReddcoinTalk forum regarding PoSV v2.
This was the original statement made about 1 year ago, and I believe there is merit in re-visiting this PoSV v2 proposal. It provides and extra incentive to everyone who continues to stake, and in doing so get a bigger percentage of return.
So in my spare time I have been extracting information about the current network, the blockchain and the metrics of how it is functioning, what returns stakers currently get and whether this remains a viable option.

Getting involved

We are a global community, and cross many borders but boundaries do not need to hinder us.
The crypto currency world has not reached its tipping point yet, but when it does, it is sure to escalate at an amazing rate. There are going to be many ups and downs, and an interesting ride for sure.
If you would like to get involved and dont know where to start, reach out and we will see where you can jump in @Deadpool has a great Trello site going with activities that need looking at.

In Closing

There is still plenty to do, but we are getting closer and I look forward to another productive week.
So where ever you are, enjoy your week ahead
Keep on staking!
x-posted (
submitted by cryptognasher to reddCoin [link] [comments]

The ultimate back-up plan: Your private key, stored in the block chain, encrypted

[edit: It is the ultimate back-up, but it doesn't mean it is the safest. I'm too tired to figure that out. I'm just explaining how to store a private key in the block chain, in case it is useful or can be made useful.]
I had that idea if someone is interested, though I guess people won't like it. It's a bit wild. We encrypt the key and put it in the block chain with a trick.
I'm not saying everyone should do this, but it could be useful to know it can be done.
If you trust encryption and your password more than back-ups or a third-party, then it could be nice. I'm no encryption expert but it should be strong enough.
"Instead of taking 1.3 quadrillion years, our magical cracking supercomputer would only need 328 trillion years."
If it's flawed or gets cracked after a billion years, I decline all responsibility. But you can be sneaky about it. I propose a sneaky trick at the end. It's a bit rough on the edges and crazy but I'll put it out there. If people like it, there are always ways to streamline.
Anyway, you can't memorize the key as you can memorize a password. It's true you can put it on paper; then lose the paper. You can encrypt it and keep it on hard drive, then lose the hard drive. Or on a service, and lose the service. The block chain though, is going to stay around as long as you need the key. So I suggest this whole alternative.
You can still put the information on paper if you want. But now, just your memory is enough. Just the password.
The drawback is the infinitesimal odd of someone finding out and spending a lot of years and resources on brute-forcing. I'm not sure what would be the odds of success. Just make it so decades of computing resource cost more than what's inside.
Now I'll explain how to do it from A to Z, for the few interested.
Plan: 0) Vanity 1) Get the key 2) Encrypt the key 3) Put the key in the block chain 4) Retrieval 5) Conclusion
0) Optional: Vanity I recommend a vanity address (choosing the first part of the address). So if worst comes to worst, you find it from memory in the block chain. And also, it's kinda neato. How-to: first, download VanityGen, direct/wiki. Extract it, then Open a console window at the location with shift-right click in the folder, if you have vista/7/8. Then type "vanitygen 1something" in it. It has to start with 1. If it's too long it'll take a lot of time. Ctrl-C to cancel if it's too long. Faster with GPU: oclvanitygen -D 0:0 1something (maybe broken atm) When you have the key, type "importprivkey mykey" in Help->Debug->Console of bitcoin-qt, to add it. Result of this optional step: A beautiful address which can be retrieved from memory if needed (after it has been seen in the block chain with a transaction)
1) Get the key - Download open source Pywallet: direct/profile - Extract somewhere. Shift-right click in the folder and "open a console window" - In the console, type: pywallet --dumpwallet dump.txt If your wallet is encrypted, then add --passphrase=PASSPHRASE Now you find the key in dump.txt. (note: it reads the wallet at C:\Users\x\Bitcoin) Result of this step: the private key; it looks like 51 characters starting with the number 5. (To delete dump.txt, you can use a software so it can't be recovered from HDD, like Recuva it seems)
2) Encrypt the key - Choose an algorithm. Personally, I pick AES-256. - Download a trustworthy program to encrypt text with the algorithm. Here are two with GUI I found. It's open source but I didn't check it, so it's not 100% safe: They're both jar files. Maybe you can click them. Personally I have to go in the console; I'm so tired of that coffee cup. "C:\Program Files (x86)\Java\jre7\bin\java.exe" -jar ImmediateCrypt.jar. It gave me an error though. Not the other. Maybe someone can suggest better. - Choose a good password. It's all about the password (and the software). AES is weak with weak password. And crazy strong with a good password. This is not like websites with protection against brute-force. People can brute-force fully if they find out. I like psycho-pass method which is about a pattern on the keyboard instead of semantics. Side Info: Or a passphrase if you want. Here is a nice table with password entropy: Below 64 bits of entropy, it's too unsafe, it's too weak. We need 128 bits or above, as far as I know. That is 25 random alphanumeric. If you're feeling paranoid, 256 bits. You can check entropy of password roughly here: Remember it is not like websites. There is no "Forgot password?" button. Memorize it permanently; and maybe write it down in your favorite book just in case, I don't know. Result of this step: the encrypted key. It doesn't matter what it looks like as long as it takes you back to the key when you click "Decrypt". (on a different software, preferably)
3) Put the key in the block chain It works by sending some minimum amount to fake addresses, with data encoded in the addresses. Can't try this part because I don't have bitcoins. :[ Only a wallet! If some liked the guide particularly: 1thxd4KJLhBMcfCYaVKYMA8Atv3Dfx9hb :3 I'll follow the method of this great article: (the blog is remarkable!) - We're supposed to split the encrypted key in chunks of 20 characters. Then convert from ASCII to hex. Last chunk we fill with extra zeros. I wrote a little javascript to do it all automatically! If you don't like it, find a software, or do it manually. Not tested much but seems to work for my test. I'll say how to know if it worked. Copy that: encrypted='';har=(encrypted.split ('').map(function(c){return c.charCodeAt(0).toString(16); }));ek="";har.forEach(function(c){ek+=c;});while(ek.length%40!=0)ek+='0';iEK=0;ek2='';while(ek.length>0){ek2+=ek.substr(iEK,iEK+40) + "\n";if(ek.length>=40)ek=ek.substr(40,ek.length-40);else ek='';};ek2;
Check eventual comments to know if it's a hack/broken mess.
I don't do much Javascript, or much anything. Paste the whole thing in the javascript console. To open the console: Chrome, Ctrl-Shift-J. Firefox, Ctrl-Shift-K. IE9, F12. Put your encrypted key between the '' right at the beginning, then enter.
This should display rows of 40-characters chunks of the encrypted key in hex format (numbers, and a to f). I have 6 chunks but it depends on encryption. It should give twice as much characters as the input except for last zeros, and follow this conversion table from Char to Hx column. If it doesn't, call the police. Or use some Ascii to Hex service.
Now we take these chunks one by one and use to convert to BTC addresses.
Send spare money to each one (the strict minimum is suspect and it'd get found easily) in the right order (wait for 1 or 2 confirmations each time to be sure).
And we're done! The information is safe and cozy, in the block chain. Not safe from brute-forcing, but safe from ourselves; and that's safer, isn't it?
4) Retrieval
Alright, how do we go back from the addresses to the encrypted key? I can't try it myself, but apparently, according to the article: 1) Get the transaction ID on, by going to the wallet's profile 2) Go to 3) There will be something like that: "out":[ { "value":"25.08603421", "scriptPubKey":"OP_DUP OP_HASH160 27a1f12771de5cc3b73941664b2537c15316be43 OP_EQUALVERIFY OP_CHECKSIG" } ]
And you need to translate the "27a1f12771de5cc3b73941664b2537c15316be43" part from hex to Unicode. The result should be the chunk of encrypted key, written in hex again. You put all the parts together in order, remove extra zeros. Then use a program to go back from hex bytes to ASCII. Maybe someone can do it or I'll put the javascript one of these days if people are interested; I don't think they'll be. Usually I'm serious and extensive but you can't imagine how tired I am these days, of everything. Anyway, you put that ASCII in the AES program with your password, you click Decrypt.
Then you have your private key.
If you do this, don't lose other back-ups until you have successfully retrieved the key, to know it works.
5) Conclusion I understand that there's a small chance that someone figures the transactions are data, reassembles the parts, has massive luck and breaks the crazy strong encryption with supercomputers and botnets in less than decades, or aliens hack your bitcoins with quantum computers, ect... But I don't know, that seems very unlikely to me; more unlikely than losing personal back-ups or third-parties being untrustworthy.
More importantly, it gives peace of mind of not having to manage back-up stuff. You can format your hard drive and burn your house down if you want without worrying about losing stuff; well, except the house. And maybe the wife. Or you go to prison 20 years, and it'll still be there. If some of you want to go to prison. I know of one.
Here's a complicated idea for the extra-extra-paranoid: You send just one letter by one letter of the encrypted key, into dozens of fake addresses, to which you send bitcoins you got from an exchange and not from the main wallet, and only you know the correct addresses/order with the data, because of a pattern in the other letters. For example, the 2nd letter of the 1st data part is the 1st letter of your password when it's hashed. The 3rd letter of the 2nd data part is the 2nd letter of your hashed password. Ect... And it's not true for the other parts. So you know the order, but not someone without the password. It can go like this for many parts, then maybe if you run out of letters you send through a different wallet. All other characters are misleading except the 1st one, or last one, being the key character. And you also send money to other fake wallets which are purely misleading. Even if a flaw in AES was found and it could be broken instantly, an attacker would have to find the correct combination even before the strong encryption brute-forcing, he can't even know if he has the right combination, and that can be a big number of combinations. You can do the math. It's exponential stuff, I think. That's something I just thought of quickly, and I don't know much about any of that. Someone can find better. (Maybe, or maybe not, there's something about the encryption output which makes it so we can find the order back without password, then we'd need some kind of trick to obfuscate the position or nature of key characters but I won't spend any more time on something likely to be wrong/uninteresting).
tl;dr: "It works by sending some minimum amount to fake addresses, with data encoded in the addresses. "
Point is, once we know we can store data in the block chain, there are plenty of ways to make it so we're never locked out from the main address.
Well, if you can remember the password.
I hope this was useful to someone!
submitted by yemethzi to Bitcoin [link] [comments]

Bitcoin How to import your old wallet into new one ... How to recover your Bitcoin private key-Facebook like @findBTC Getting your Private Keys from the Bitcoin Core wallet ... how to import bitcoin address to wallet and unlock private key ZCL Electrum Wallet - How to Import/Sweep Private Key

Importing private key text to your wallet This is how to import using the copy-to-clipboard method. If you receive an email on your device with your exported wallet, or choose "Copy to clipboard", on most devices you can press the screen and wait for a “Paste” button to appear, then paste the backup code in to the field. Bitcoin Private Electrum Wallet - How to sweep/import Private Key > Bitcoin Private Electrum Wallet - How to sweep/import Private Key Step 1. Install the Bitcoin Private Electrum Wallet Install the wallet following these instructions , and create a new wallet. Step 2. Go to Wallet - Private Keys - Sweep In this field, To import a private key you need to access the advanced developer menu. Exodus supports both compressed and uncompressed PrivateKeys. Also, for Bitcoin and Bitcoin Cash Exodus also supports importing encrypted (password protected) Private Keys. Below we a One such way is to use the PyWallet Bitcoin wallet importer/exporter Python script that has been available for ages and that ... If there are you can then just import the public/private key in a new wallet and then do whatever you want with the coins inside. Importing the key pair can vary depending on the wallet you choose to use, so check what is the procedure and make sure that you can ... When successully imported through the "Import/Export" screen, the bitcoins assigned to a private key can be immediately sent to any Bitcoin address. Using BIPS . As of August 2013, BIPS allows for easy import of private key using Paper Wallet - Import. User can choose to type in the private key manually or scan a QR code containing the private ...

[index] [6234] [10119] [19201] [15232] [4197] [32686] [35295] [27586] [13158] [40323]

Bitcoin How to import your old wallet into new one ...

In this tutorial we are going to get our private keys from the bitcoin core wallet. This only works when you created the bitcoin address in the same wallet. ... Learn how to Import and Export the private key in the Bitcoin-Core Wallet and bitcoind.exe and bitcoin-cli.exe How to import Private Key (Bitcoin Address) into Blockchain Wallet? [New 2018] - Tamil Review Today - Duration: 7:33. Tamil Review Today 26,683 views. 7:33. Copy and Read me files prom file in downloads in C drive and paste in python 27 folder Copy your wallet.dat file from your Bitcoin wallet folder in C:\Users\Your username ... A real working program for hacking bitcoin addresses Hack bitcoin addresses Brute force Program to search for private keys Brute ...