Memorize a simple password in your head 1234BitcoinEater, then memorize the hashing procedure, e.g. SHA256(HEXTOBIN()) then use it as your password.
If you have multiple passwords you could combine multiple one way hashing algorithms and add 1 to the end of your memorized password, then every time you need a new one simply add 1 to it and hash the same way to get a completely different password.
Here's another hare brained scheme for you guys to consider: - Take out your camera and take a picture. - Make a hundred billion copies of that picture and stick it everywhere. In USB sticks, DVDs, memory cards. Throw them around the house. Make sure a few tiny memory cards end up behind the sofa like loose change. Even wear one as an amulet around your neck. - Use the sha256sum of the picture as your password. Very easy to do on *nix sha256sum my_not_so_secret_pic.png
- And if you need multiple passwords just append a number: echo "1" | cat - my_not_so_secret_pic.png | sha256sum
Now we can tie our BTC to our testicles, thanks for the great info. I use the SHA256 hash of a picture of me standing in my kitchen to access my Bitcoin savings. I did not store the picture to be safe, because I can always take a new one but no one else can get a picture like that. I have not stored the picture anywhere so it's like a brain wallet but I feel it's more secure as that's more entropy than I'd like to just remember. I hope my house doen't burn down... I don't think so but maybe I should consider printing such a pic and taking it to a bank vault
|
|
|
0.052 BTC/Gh, would like to see how the proud holders are doing now
|
|
|
Jesus, how come this thread is always in the first page of Bitcoin discussion? There's more relevant Bitcoin discussion going on in the off-topic section. Do you guys live in the Bible Belt or why is this thread not long forgotten?
|
|
|
Very interesting topic. I've been investigating the possibility of building a dead man's switch. I really love that idea: a dead man's switch to transfer your coins to a location where your inheritors can access them.
First I thought it's possible to create a completely 3rd party independent dead man's switch by creating a time locked transaction which you could replace with a longer time lock if you're still alive. That would not require a program to do anything for you after death. This is apparently not possible due to the DDOS issues of replacing tx.
Now the best I can come up with is multiple types of dead man switches where you need to have a server set up to broadcast the transaction after death. That is okay, but not as rock solid. It's probably the best we can do since anything else requires that the transaction can be broadcast before time of death.
Interesting to see this post because this is just what was on my mind too! Maybe it's the finnish winter and grimness? Well, I don't have anything useful to say but this topic cleared things up, very nice!
|
|
|
I know the whole deal is "solving math problems" so I just liken it to solving crossword puzzles or sudoku when explaning it to my mom The "solving hard math problems" explanation is a stupid analogy. A better analogy is picking lottery numbers, but even that is not really the point. The point of mining is validating transactions. Yeah. As a math student, I find that annoying. It's just poo-loads of the most trivial kind of computations. The part I am still trying to figure out is how do transactions get processed after all bitcoins are mined? Since transactions are only attached to a valid bitcoin block and there are a finite number of bitcoins that will ever be produced, will we lose the ability to perform transactions once all bitcoins have been mined?
Miners will keep mining blocks, there as just no longer any block rewards. The miners now get their income from the transaction fees, so there is still incentive for mining. You can do mining, just keep hashing blocks, there does not need to be a BTC reward for every new block.
|
|
|
Sure just send it to this address: 1111111111111111111114oLvT2
it's well understood that nobody has the private key for this. It is the bitcoin address that corresponds to a public key hash of 0.
Ops, there are almost 3BTC there, seems that people are really destroying BTC's. ;-) OP: Basically, you can just randomly generate a valid public bitcoin address (without the corresponding private key) and send the money there. Just note that it should also be an address like "1ThisisABitcoinEaterAddressjkjf8ejifnsin8w3" or "111111111111111idjfiufj3" (probably not valid) so that people can be sure (at least sure enough) that you don't have the private key. Of course you can "destroy" (render unusable) your BTC but to do it publicly as OP wanted to, others need to be sure they are untouchable, which will not happen if you just generate some address; it must be obvious that with a very high probability no one has the private key (nor will ever have). Yes, there are wasy. But 99.9999% of the population dont have the means.
Most certainly, everyone who has control over any amount of BTC can send them to for example 1111111111111111111114oLvT2 as Mike suggested. We should come up with a clever plan to get people to send their BTC there (of course knowing what they do!). Some kind of a "who's the richest" pissing contest type of thing but something with more appeal
|
|
|
I remember a time when the password was something you could actually remember It's in the name: pass-word. Why call it a password if it's not a word? I always thought it was a "word", meaning, concatenation of characters from a given alphabet.
|
|
|
There is such a problem? I have always received mine with no difficulties.
|
|
|
This topic has been discussed ad nauseam. Perhaps you should try searching for some of the previous discussions if you are looking for answers.
And the topic will keep being discussed until a solution is presented and implemented. This has been discussed a thousand times and Satoshi thought about this too. How do you mean implemented, you can get a light client that does not download the whole chain.
|
|
|
m is standard for milli µ is standard for micro, but if you cannot type a µ character then u is standard for micro n is standard for nano
#1 reason for using nBTC is that it will make everyone will feel very rich because they can easily own millions of nBTC!
Windows Hold alt and pres 230... in case anyone ever wanted to know I cant do it Yes you can, you just need a better keyboard. Alt+230? Huh? Does alt gr + M not work (almost) everywhere? I've been using that forever on all sorts of systems.
|
|
|
Why would it push the price up? Simple. Each mbtc would be sold for $1 and that would push the final btc price much higher.
The only way 1 mBTC would sell for $1 is if one whole BTC is *ALREADY* priced insanely high. So no ... your argument doesn't work. We're discussing right now. When one mBTC is worth $x.xxxxxxx1. We are not discussing 100 years from now when an mBTC is priced at $1.00 I want to know how it gets to that point. Next? What? 1 mBTC is about 0.7 $ at the moment and has already been worth more than 1 $.
|
|
|
That's awesome man, I'll check out your NES emulator! I don't know how technical it would be, you should be able to look at the blockchain and then find bitcoin addresses there and see the order. I'd suppose it's nothing too complicated, no need to mess with cryptography or transactions. You might want to look into it, I'm considering myself but I don't know... Here's Python source for some firstbits lookup, I haven't even seen it but I'll consider checking it out later: https://github.com/bitcoin-abe/bitcoin-abe/blob/master/Abe/firstbits.pyEdit: And BTW, if you haven't seen this, take a look: http://visual6502.org/Transistor-by-transistor hardware simulation of the 6502. Very neat.
|
|
|
I'm a programmer too. Mostly C and x86 assembly. My #1 interest is writing emulators for CPUs/systems in software. Very fun... and sometimes frustrating. Cool! What kind of things have you done? x86 ASM is a pain in the ass though. I like assembly but I stick to the good old 6502. A lot prettier too. Can't find much beauty in the Z80, x86 etc. stuff I've been looking into. Wasting those cycles like hell! But what I wanted to say, I know a really good programming project. It's making firstbits addresses work again, a working firstbits lookup. For example, I might have an address starting with 1kuverty, and if that was the first address in the blockchain to start with those characters, then 1kuverty would be my firstbits address. They were popular some time ago, but they were criticized a lot and now there is no working service for those. It should be a doable project for someone who knows programming and a great intro to Bitcoin-related stuff, parsing the blockchain for addresses. For extra credit you could do Litecoin/Peercoin/Primecoin too. I'd like to know if someone takes interest in this, I've been interested in doing this but I really can't code. I hope you find interesting stuff to program involving Bitcoin, there is a load of things to do... happy hacking!
|
|
|
Don't know what I was thinking when I wrote that firstbits could be used for a brainwallet. Firstbits is for addresses, not private keys, so obviously it wouldn't be of any use. Duh.
I thought you meant that you if have a brain wallet like the one generated by "correct horse battery staple", which, if you use the default settings at brainwallet.org, corresponds to the address 1JwSSubhmg6iPtRjtyqhUYYH7bZg3Lfy1T; then you could accept payments or send yourself some money by remembering only the firstbits, which could be 1JwSS, quite short. This way you could keep all the stuff you need for using Bitcoin in your head. You obviously remember your brain wallet's passphrase, so you can access your funds if you need; with firstbits you can also quite easily remember your wallet's address, memorizing the full address would be unnecessary (it's difficult, many people probably would not want to do it).
|
|
|
Well try several ones: - Koblitz: Number Theory and Cryptography - get the crucial understanding of elliptic curves math from complete zero, - then try a great "Introduction to Modern Cryptography" by Jonathan Katz and Yehuda Lindell and you good to go.
Both are good, Koblitz is really a must and also very interesting for other things besides crytography. Additionally, Arto Salomaa's Public-Key Cryptography is a classic text regarding, surprsise, public-key cryptography and I found it was particularly clear and well-written.
|
|
|
It's like a pyramid scheme. Only reason you're making money is by conning someone else. This is fraud. Last person holding your worthless ghs loses. Hot potato anyone?
No secret that the price will keep going down, nothing fraudulent there.
|
|
|
Will be a little late, but I'm giving a paper wallet worth 1 BTC to a good friend of mine, complete with a nice vanity address.
|
|
|
I use an online wallet, http://blockchain.infoI have set my account so that only my IP address can withdraw funds, and I have purchased a YubiKey for 2 factor authentication. The YubiKey costs about $25, and my wife and I have our own separate YubiKeys. I am not aware of anyone losing funds with 2FA and blockchain, other than the Android cell phone encryption bug last summer. doesn't sound real safe. what happens if you change ISPs or your current ISP becomes bankrupt, or changes hands? Yeah, locking to your IP is watertight in theory, but your address may not be static or stay the same forever. I'd just use the 2-factor auth and set up another password to be able to spend funds. You can also block TOR connections. Blocking TOR connections sounds like a good idea... the user could be asked about this when registering. Also connections from other countries/known proxies, at least without e-mail confirmation.
|
|
|
|