200+ salt variations tested.

Kill me now.

I've been running this since yesterday. Been aware of the echo newline injection and the JTR limitation from the get go.

D-Wave produces an adiabatic quantum computer with a lot of limitations (high noise and error rate). It can only solve particular problems that are solvable by quantum annealing with very high error rates, such as protein folding. Running Shor's/Grover's algorithms with that amount of decoherence would produce nothing meaningful. And I'm not even sure you could construct Shor's algorithm in such a way that it runs in a D-Wave computer because their implementation is very specific and not general purpose.

TL;DR decoherence fucks you up

And as others have said, classic cryptographic algorithms that are impervious to quantum computers do exist. It is the general consensus that quantum computers will never be able to solve NP-hard problems. If a quantum cpu is close to factoring large numbers everyone will see it coming, and new algos will be implemented pretty much everywhere, not only for Bitcoin.

I do like Armory. In fact it has been my client of choice for quite some time. But the absolute safest way (we're talking maximum paranoia here) is to use the openssl lib offline on a livecd after verifying the ISO's hash.

This is the best solution I've seen so far.

There's nothing wrong with bitaddress.org but it will take ages to go through the code. Especially the ECDSA math.

"Hedge funds"





Pay them back out of the goodness of his heart? Never going to happen unless he is forced to do so by the legal system. 260k is a boatload of money to pay off in a country where the average monthly salary is $1.2k. If by work you mean bitcoin related projects then I don't see how can anyone trust him with their money ever again.

I'm particularly worried by the "recreate key if hexsize != 64" deal. Won't that effectively reduce the keyspace? I know it won't be much but still.

I hope my post isn't considered a necro but this method needs more exposure and most importantly more scrutinization (is that even a word?) by people who know the internals of bitcoin.

There should always be a secure way to create addresses offline with readily available tools in a standard linux distro. Since the privkey is generated by a single openssl command, you know 100% that it hasn't been tampered with. As opposed to trusting a website and downloading a program from it.

Am I too paranoid?

Welcome to Bitcointalk.
Where men are women,
women are men,
and 14 year olds are SEC agents.

looks real to me

It's an exercise in futility but look into javascript clients.
It would be funny to see how many hashes/sec javascript clients can get on an iphone/ipad.

I predict no more than 0.00001 BTC per month (and your battery gone within an hour) 

Hence my "average joe" comment. I should have said "your average non-technologically inclined person". I'm just talking about the average user that uses the internet for facebook and/or buying things online once in a while.

It is pointless to explain the internals of Bitcoin and cryptography to a person like that. Trust me I have tried. However, my knowledge in both topics is quite deep. Therefore I think I am in the position to make that decision for them and if they trust me they will follow my advice.

In that case, what I do mention to them is that a web wallet should only be used for micropayments and that all BTC transactions are irreversible unlike credit cards.

Slashdot, around 2 years ago.

I wish I rode the initial mining wave

Why? It's so inefficient and provides a poor user experience.

Power users and developers will understand the need for it to download the entire 3.5GB+ blockchain, however the average Joe will not.

I understand that the 0.8 ultraprune client will reduce first run time to 30 minutes, however that is not enough. Until the official client is snappy enough and has a sleek & sexy interface (think Electrum on MacOS), I will be recommending Electrum/Armory or web wallets like BlockChain/Coinbase to people who ask me about Bitcoin.