How? Security of private keys

[bitpop]

So the addresses will be get longer sometime in the future?

BUT then again, bitcoin was designed when mining was astonishingly slow on the cpu. Now we are already 10000X faster, can bitcoin be strengthened if in 5 years GPUs can crack a key in a month?

Yes, it can be strengthened.

[dooglus]

So the addresses will be get longer sometime in the future?

Or the hashing function that's used could get more computationally intensive.

2. Can private keys somehow be different for the same address and the correct one can be checked against the blockchain?

There are lots of different private keys for each bitcoin address.  If you can find any one of them then you can spend the coins at that address.  The problem is that it's too hard to find any them.

[memvola]

There are lots of different private keys for each bitcoin address. If you can find any one of them then you can spend the coins at that address.

Will it still be the case if the address has been spent before?

[kokjo]

(My math probably isn't right)

You can generate 1 address a second.

86,400 seconds in a day = 86,400 keys a day.

26 bits in a btc address, 403291461126605635584000000 permutations.

so 403291461126605635584000000/86400 = 4667725244520898560000 days.

So, you wanna wait

1.27882883411531467397260273972602739726027397260273972602739726027397260273972 6027397260273972602739726027397260273972602739726027397260273972602739726027397 260273972602739726027397260273972602739726027*(10**19) years?

I didn't think so.

there are 160 bits in a btc address. so its: 2**160 seconds you have to wait. so its about 10**93 years.

EDIT: my math failed to, i used ln instead of log. correct is ~10**40 years

[SomeoneWeird]

(My math probably isn't right)

You can generate 1 address a second.

86,400 seconds in a day = 86,400 keys a day.

26 bits in a btc address, 403291461126605635584000000 permutations.

so 403291461126605635584000000/86400 = 4667725244520898560000 days.

So, you wanna wait

1.27882883411531467397260273972602739726027397260273972602739726027397260273972 6027397260273972602739726027397260273972602739726027397260273972602739726027397 260273972602739726027397260273972602739726027*(10**19) years?

I didn't think so.

there are 160 bits in a btc address. so its: 2**160 seconds you have to wait. so its about 10**93 years.

lol yeah, i thought it was wrong. meh

[chiropteran]

there are 160 bits in a btc address. so its: 2**160 seconds you have to wait. so its about 10**93 years.

EDIT: my math failed to, i used ln instead of log. correct is ~10**40 years

Even that estimate is too low, because there is no big flashing sign that says HEY YOU GOT A USEFUL PRIVATE KEY!

You have to add time to test each and every key you generate if your goal is to find one with money in it, which increase the time by another order of magnitude...

[bitpop]

Is using a vanity address ANY less secure than using a regular one since the scope decreases?

[rjk]

Is using a vanity address ANY less secure than using a regular one since the scope decreases?

The only reduced security is if some noob looks at the beginning and doesn't compare the rest of the string to see whether the rest of the address is legit.