PS The sooner oil is depleted the better. We could finally take on new energy sources with full force.

I'm waiting for the block reward to drop to 12.5.

Same here, I now have over $0.05 USD... and I keep it in my bank pending its conversion to bitcoin.

I'm Linux/BSD nerd. I just use SSH for remotely logging into my machine. You can even do X forwarding with the 'XC' flags (X forwarding+compression). Unfortunately, I don't currently have my computers set up 'just so', so no bitcoin.

By "off-site" I mean: will survive building destruction by being somewhere else. At the risk of being accused of money laundering, I plan on using a safe-deposit box.

I know that was in response to a question, but that deserves the Triple-facepalm picture you were asking for.

The real problem is that bitcoin infrastructure is immature and, due to the underlying immaturity of the computer industry, may remain so for decades. In particular, the "default" bitcoin client is largely a proof-of-concept. In order to use it securely, you need to understand at a fundamental level how your computer works. You need to not only guard againts hardware failure with verified, off-site backups. You also need to make sure that any attacker compromising your day-to-day wallet is not also able to compromise your offline wallet (that may have been transiently written to the disk during creation).

The most secure way of generating a savings wallet is to generate bitcoin keypairs offline, then printing the result, then wiping the disk (or RAM if disk was not written to), then sending the coins to the public address from an Internet-connected computer. Secure storage of paper is a known problem that people understand well. However the are a few caviats to keep in mind: (1) You need a good quality, trusted random number generator, (2) any copy of the private key is equally valid, (3) AFAIK the 'default' client can not import such keypairs for spending.

If you are the average user who has not taken extreme measures to secure their computer, using an online service as your day-to-day wallet may be a reasonable way to limit the damage if your day-to-day wallet get comprised. One difficulty is that the value of bitcoin has increased dramaticly over the past two years. What was once "spending money" may suddenly represent a substantial sum of money. Until the "default" client, or a third-party client that becomes trusted supports multiple wallets in a secure way; doing this separation on your home computer will be difficult and error-prone.

I think infrastructure is going to be a diffcult issue. If Bitcoin adpotion increases exponentially, I would expect trnasaction volume to also increase exponentially. The Asian-Pacific region is expected to run out of IP addresses by the end of the year, but few (north american) ISPs have made the transition to IPv6. Asside from the addressing issue is the fact that the Terms of Service attached to most consumer Internet connections prohibit hosting servers; or using more bandwidth than some arbitrary limit. If we don't carefully plan ahead, the bitcoin network will become even more centralized. I also feel that bitcoin nodes should be using hardware and software from diverse suppliers. I think the bitcoin community may run more diverse hardware than most.

I shit you not, it actually takes me longer to backspace and un-capitalize words, and to write improperly. You should practice it... most people don't have to sit there and think about how to spell and use proper grammar. Kinda like using blinkers in a lane change (I'm guessing you're too holier-than-thou to do that, either). It just becomes habit if you ever gave 2 shits enough to think about it.

And really, I already refuted you 2 pages ago. I just didn't have to (nor want to) reply to you, but rather to the other people that actually took the minuscule amount of mental effort to present their ideas in a meaningful and more linguistically-respectable manner.

tldr: Suck it, you're not worth the time nor mental effort I've already expended in trying to reason with you.

edit: But 'gratz on your 666th post. 

But that is not how it all started last time. People talked about it happening in a trickle.
They were told it was completely their fault, etc.. Then it all blew up with a password file
being handed around like nothing days after.

Is there any chance the coins will be available through a distributor in europe at some point? I'd buy a couple as presents (and one for myself because they're awesome) but not if I have to deal with customs. The last time I had to was when I bought some merchandising from the U.S. You wouldn't believe the amount of documents I had to send in before I finally received the parcel. And then the postman who delivered the parcel and collected the customs fees didn't have any idea if he needed to do anything special, like letting me sign some extra paperwork, so after a minute or two he just gave me the parcel reluctantly.

I stopped taking you seriously at that "your" part, but continued to read through your self-perpetuated lack of capitalization* just for entertainment value. And for similar entertainment value, I figure I should tell you that it would've been just as effective, and much less damaging, to have just left out the part about "how the passwords are stored" and just cut to the "if your password is this long" part. There was absolutely no benefit to blurting out exactly how the passwords are stored.

* - that is, "what does it matter to me what some idiot forum noob thinks about my spelling" / "i don't need to be in grammer class whenever i go onlien, fukk you" / "i feel like relaying my low mood and chronic depression through the use of nocaps" / "I Swear i could write Proper Grammar when I need too, I don't need some Stupid forum troll telling me what too do!"

Salting bascially changes the original value and the comparison value with a known figure so the hashes can't be referenced to a lookup table, and so they can't be broken without knowing the salt value. Oh wait, we know the salt value now. Haha, that was easy™.

Again, with the big exclamation of, "Everyone lock your doors, they might have gotten a copy of the KEY TO THE KINGDOM! *attachment: high-res picture of key to the kingdom.jpg*"

The funniest thing about this discussion (besides ShadowOfHarbringer, or course, who makes me cringe with each post) is that in a forum dedicated to software which depends on hashing the shit out of SHA256 -- where people buy cheap video cards which are capable of generating literally hundreds of millions of SHA256 hashes per second on a single video card -- people still think that sha256 is a great way to slow down offline password cracking.

Pathetic. And the hits will keep on coming. More stolen password databases from poorly secured websites. More stolen emails and more stolen passwords. An endless comedy of errors and bad PR.

Also, nice ponzi scheme signature, theymos... inspires a lot of confidence in those who are first learning about bitcoin to see that a "Global Moderator" peddles a fucking ponzi scheme. I'm sure that won't reinforce the suspicions that people already have...

BTW. Keypass uses SHA256 to truncate or expand a user's password to 256 bits. It has nothing to do with adding computational cost to cracking.


Who knows? The authors apparently don't go out of their way to make it clear, but then again, I don't use keepass... smells a bit too much like snakeoil.

tightvnc is good

So were do I store the USD I use to buy during downturns? In my wallet file? 
Actually, bitcoin has caused me to hold more usd than I have ever before. Isn't that ironic?

KeePass uses SHA-256.