|
Best option imho is to use "android bitcoin paper wallet" on totally offline phone. Just generate private key and write it BY HAND. Spending is bit cumbersome but possible offline and is not as weird as buying "two macbooks" for that.
|
|
|
|
|
I refreshed this project few days ago to make it look bit better on tablets and new devices, fixed the only crash and updated hash algorithm from SHA-1 to SHA-256 in random number generator.
|
|
|
|
|
Banks exchanges by a relatively huge transactions about once a day, so it is not a problem.
|
|
|
|
It's one of the basic rule for all the newcomers out there, "CHANGE THE PASSWORD REGULARLY"
I tried to change ALL my passwords at once. It took about 2 weeks. How many account do you have then? This way it looks like you have over 20k accounts  Not that many, about a hundred. No, there are few hundreds. But definitely less than a thousand :-) Well anyway it took you quite a time to change every password. I thought you had even more accounts when you did that for 2 weeks  You know, when every single service invents its own way to change password it takes awhile to change everything ) |
|
|
|
It's one of the basic rule for all the newcomers out there, "CHANGE THE PASSWORD REGULARLY"
I tried to change ALL my passwords at once. It took about 2 weeks. How many account do you have then? This way it looks like you have over 20k accounts Not that many, about a hundred. No, there are few hundreds. But definitely less than a thousand :-) |
|
|
|
It's one of the basic rule for all the newcomers out there, "CHANGE THE PASSWORD REGULARLY"
I tried to change ALL my passwords at once. It took about 2 weeks. How many account do you have then? This way it looks like you have over 20k accounts Not that many, about a hundred. |
|
|
|
It's one of the basic rule for all the newcomers out there, "CHANGE THE PASSWORD REGULARLY"
I tried to change ALL my passwords at once. It took about 2 weeks. |
|
|
|
whats btc?
Badass Toyota Car(s) How does one own 0.5 badass Toyota? You can shred one badass toyota car up to 100 million pieces. But how many badass Toyotas will there ever be? MILLIONS :-) |
|
|
|
whats btc?
Badass Toyota Car(s) How does one own 0.5 badass Toyota? You can shred one badass toyota car up to 100 million pieces. |
|
|
|
Just like the title says I'm looking to pickup an inexpensive laptop for bitcoin cold storage. Any ideas?
Lightweight, highly portable, good battery life and cheap would be a great combination.
A smartphone? |
|
|
|
But this view is not universal, apparently:
Reusing addresses is therefore the preferred method of maintaining the privacy of your sources. - http://bitcoinpete.com/2014/05/05/on-reusing-bitcoin-addressesI still don't get how a dozen people sending to a single address of mine is protecting their privacy better than if I provide one address per transaction. And I'm more interested in MY privacy than theirs, anyway. If they want privacy, that's their job to mix or obfuscate -- not mine. That's quite simple. Creating a very secure paper wallet requires some efforts. Dealing with multiple paper wallets requires even more efforts. When you deal with multiple paper wallets there is always a risk that you loose a paper wallet and that means that a single paper wallet might be more safe than many wallets. |
|
|
|
|
Thanks everyone! Seems ESCDA is much less secure than I thought but even with all the weaknesses and moore law we are good to reuse addresses for at least 100 years :-)
|
|
|
|
https://en.wikipedia.org/wiki/Key_size#Asymmetric_algorithm_key_lengthsIf you think that is strange as pointed out it takes 3,072 bit RSA key to achieve the same security. Also note that in 2010 a 768 bit RSA key was broken by brute force. http://www.theregister.co.uk/2010/01/07/rsa_768_broken/There isn't sufficient energy in our solar system to do that to a symmetric 256 bit key in the lifetime of our sun yet it was done for a 768 bit RSA key in a few years. Why? It takes far less operations to brute force a RSA key than its key length would suggest and as such a 768 bit RSA key isn't the equivalent of a 768 bit symmetric key but closer to a 64 bit symmetric key. For SSL no CA will issue a 1,024 bit RSA key anymore due to the fact that it only has 80 bit key strength and thus is on the edge of what a dedicated (think NSA) attacker could brute force. Thanks, that's very interesting! Do you know most "promising" attack on the ECDSA? (I'll try to google it for now by myself ;-) but maybe you know something interesting about) |
|
|
|
ok, so I understand that you shouldn't re-use an address
because then people will see the public key rather than
the hex-encoded hash, and it weakens the security
from 160 bit to 128 bit...
But, can you receive multiple transactions at the same
address (as long as you dont send) with no security
compromise?
Private key is 256 bit. Public key is 256 bit too. Hash of public key is 160 bit. How revealing of public key (256 bit) reduce strength to 128 bit? It's reduced to 256 bit ECDSA. I fail to see the 128 bit strength :-) The bit strength of a key refers to the equivalent strength of a symmetric key of that length. The key strength is only equal to the length of the key for uncompromised symmetric ciphers (and usually hashing algorithms). For public key cryptography, the bit strength will always be less than the key size. For ECDSA it is 1/2 the key length. For 256 bit ECDSA keys used in Bitcoin that means 128 bit security. I don't know why Satoshi chose a 160 bit PubKeyHash as a 128 bit one would be sufficient and would result in shorter addresses. As a side note sometimes people ask why ECC, why not RSA? To achieve 128 bit security using RSA would require a 3,072 bit public key and that would mean very large transactions. Can you give any links what proves the point please? I can understand that hashing to 160 bit means that there are many ECDSA 256bits what corresponds to an address, but saying that real security of ECDSA is 340282366920938463463374607431768211456 times lower than it's key size sounds... strange. |
|
|
|
ok, so I understand that you shouldn't re-use an address
because then people will see the public key rather than
the hex-encoded hash, and it weakens the security
from 160 bit to 128 bit...
But, can you receive multiple transactions at the same
address (as long as you dont send) with no security
compromise?
Private key is 256 bit. Public key is 256 bit too. Hash of public key is 160 bit. How revealing of public key (256 bit) reduce strength to 128 bit? It's reduced to 256 bit ECDSA. I fail to see the 128 bit strength :-) |
|
|
|
I say NO !
Don't talk to food. |
|
|
|
I agree with that terminator seeds killing other crops so that the corporations and GMO can sell the farmers fertilizer and receive a cut of all their future revenues by forcing them to buy their seeds and nutrients making them dependent on them for their livelihood and at the same time killing their soil quality and bees to boot.
That is pretty hardcore evil right there
Terminator seeds don't kill other crops, they terminate their own reproduction. They're just sterile seeds. Basically the conversation went like this: "But what if the GMOs reproduce out of control and take over the whole ecosystem? That's terrible!" "No, it's okay, we can just engineer them so that the seeds are sterile and they can't reproduce. See? Problem solved!" "But then farmers will have to keep buying seeds! That's terrible!" "Dammit, is there no pleasing you people?" "No. No, there isn't." Even if scientists will figure out how to make GMO food without a single DNA/RNA inside they will cry that is the most horrible DNA modification ever, don't waste your time :-) |
|
|
|
|
Version 2.30 is out. There are automatic fee calculation and better UX.
|
|
|
|
|
Show Posts
