Bitcoin Forum
November 11, 2024, 01:43:14 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 »  All
  Print  
Author Topic: is the money safe?  (Read 1085 times)
spyvingen (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
May 12, 2013, 09:12:04 AM
 #1

Im thinking if you have an asic or similar wouldn't it be possible to generate an address with public key see if there is any money on the address and if not generate new one and see if there is money on that one.

Or are used addresses excluded somehow when generating a new or something because if you have asic i guess you could go through a couple of thousand addresses in a second and soon enough you will find an address that has money?

Even if you have an offline wallet the money is in the network the only differences is that the one who created it has not broadcast it on internet.

So my question is how does the bitcoin network prevent these things. Or do they rely on statistics like the chance of finding an address is so small we don't have to do anything about it?

Please correct me in this matter so i feel safe with my coins Smiley

//Jonas
FaradayC
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
May 12, 2013, 04:22:01 PM
 #2

You could search the blockchain to see if there is money in an address... But you've totally skipped over getting access to the money.  Just because you have a public (or even a private) key, doesn't in anyway mean you now have access to someone's coins, that's just not how it works...
nocoin
Full Member
***
Offline Offline

Activity: 168
Merit: 100


View Profile
May 12, 2013, 04:26:54 PM
 #3

It's more profitable to generate NEW coins, than bruteforcing keys trying to sleal OLD one. Even with asics.
AzureEngineer
Member
**
Offline Offline

Activity: 98
Merit: 10



View Profile
May 12, 2013, 04:29:27 PM
 #4

What you're talking about is called an address collision, and yes, it is entirely possible for someone to generate one of your addresses and be able to access the money held to it. However, I don't think you quite understand the chances of that happening. There are 2^256 addresses available. That is not a small number.


If you used your Bitcoin client to generate addresses at hundreds of times per second, it would take millions of years for you to generate someone else's non-zero address. i.e. you have a better chance of being struck by three bolts of lightning and simultaneously winning the lottery than someone does of generating your address.

My name was simply a play on "Blue Engineer" from Team Fortress. I am not affiliated with Microsoft or the Azure project.
spyvingen (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
May 13, 2013, 09:20:05 AM
 #5

Hehe i crunched the numbers of adresses i its like 77 figures Smiley

But could someone by misstake generate it? I guess its kinda a lot of adresses generated daily.
superresistant
Legendary
*
Offline Offline

Activity: 2156
Merit: 1131



View Profile
May 13, 2013, 10:08:30 AM
 #6

it would take millions of years for you to generate someone else's non-zero address. i.e. you have a better chance of being struck by three bolts of lightning and simultaneously winning the lottery than someone does of generating your address.

Made me laugh.
FaradayC
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
May 13, 2013, 11:44:21 AM
 #7

You say by mistake, it's all probability.  The answer is yes, they could generate your address, they would not have access to your coins though.  Also, even by accident it's three bolts, the lottery and being the first human with super powers...
DannyHamilton
Legendary
*
Offline Offline

Activity: 3486
Merit: 4832



View Profile
May 13, 2013, 09:57:53 PM
 #8

Just because you have a . . . private . . . key, doesn't in anyway mean you now have access to someone's coins, that's just not how it works...

You are mistaken.  That is exactly how it works.
spyvingen (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
May 14, 2013, 07:41:14 AM
 #9

Ok so i could be pretty safe after all then.

The answer is yes, they could generate your address, they would not have access to your coins though.
Why could thay not get access to the coins if they have generated my adrees and private key?
I guess you cant generate diffrent private keys to a single adress and if there is only one correct private key thats the one that has access to the adress.
Correct me if im wrong here.
DannyHamilton
Legendary
*
Offline Offline

Activity: 3486
Merit: 4832



View Profile
May 14, 2013, 01:00:50 PM
 #10

Ok so i could be pretty safe after all then.

The answer is yes, they could generate your address, they would not have access to your coins though.
Why could thay not get access to the coins if they have generated my adrees and private key?
I guess you cant generate diffrent private keys to a single adress and if there is only one correct private key thats the one that has access to the adress.
Correct me if im wrong here.

I don't know if anyone has proven it yet, but there are almost certainly multiple private keys that can access each bitcoin address.

There are a total of approximately 2256 (1.158 x 1077) private keys, and only about 2160 (1.462 x 1048) potential bitcoin addresses. As far as I know, it is not even known if every potential bitcoin address has a valid private key.  If anyone gains access to any of the private keys that compute to the same bitcoin address, then they have access to all bitcoins at that address.

Note that 2160 is still a VERY LARGE number, and as such, the odds of stumbling across a private key that matches a bitcoin address in use accidentally or intentionally are still astronomically huge. There are much more horrible things that are far more likely to happen that you never worry about.
IHackedBitcoin
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
May 14, 2013, 01:09:06 PM
 #11

Quote
Or are used addresses excluded somehow when generating a new or something because if you have asic i guess you could go through a couple of thousand addresses in a second and soon enough you will find an address that has money?

There is no ASIC doing RIPEMD160(SHA256(...)) efficiently out there. But you can use this method to hack addresses on GPUs.
The possibility to find ANY is high, the possibility to find exactly yours is around 1/1600000 times smaller. Stay relaxed. The chances are low you will loose your money.
IHackedBitcoin
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
May 14, 2013, 01:12:33 PM
 #12

Quote
There are a total of approximately 2256 (1.158 x 1077) private keys, and only about 2160 (1.462 x 1048) potential bitcoin addresses.

Actually NOT

There are 2^256 - 2^32 - 2^9 - 2^8 - 2^7 - 2^6 - 2^4 - 1 private keys and also A LOT FEWER than 2^160 bitcoin addresses.
Gabi
Legendary
*
Offline Offline

Activity: 1148
Merit: 1008


If you want to walk on water, get out of the boat


View Profile
May 14, 2013, 01:19:06 PM
 #13

Possible? Yes. But it will take more than the universe life. Good luck.

bitcoinbitcoin27
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
May 14, 2013, 01:43:30 PM
Last edit: May 14, 2013, 01:53:47 PM by bitcoinbitcoin27
 #14

"If we express 2^160 in proper scientific notation it’s about 1.46e+48. That’s still way too big for most people to comprehend, even folks who understand the scientific notation. It’s estimated, for example, that there are 10^21 grains of sand on the entire planet, which is about the biggest “everyday” comparison number I could come up with but you’d need 1.46e+27 Earths worth of sand to have a number of sand grains equal to the number of Bitcoin addresses. In other words, if every grain of sand were actually its own entire planet just like Earth with its own 10^21 grains of sand, you’d still come up short. 1.46e+27 is a really big number!" - http://codinginmysleep.com/stealing-bitcoins-the-hardest-way/

DannyHamilton
Legendary
*
Offline Offline

Activity: 3486
Merit: 4832



View Profile
May 16, 2013, 12:01:02 AM
Last edit: May 16, 2013, 01:40:34 PM by DannyHamilton
 #15

- snip -
you can use this method to hack addresses on GPUs.
The possibility to find ANY is high,
- snip -

Quote
There are a total of approximately 2256 (1.158 x 1077) private keys, and only about 2160 (1.462 x 1048) potential bitcoin addresses.
Actually NOT

There are 2^256 - 2^32 - 2^9 - 2^8 - 2^7 - 2^6 - 2^4 - 1 private keys and also A LOT FEWER than 2^160 bitcoin addresses.

^^ TROLL ^^

Proof:

https://bitcointalk.org/index.php?topic=204424.0
Scott_Stark
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
May 16, 2013, 06:05:24 AM
Last edit: June 13, 2013, 06:27:23 AM by Scott_Stark
 #16

It's nice discussion about money saving, and also really nice above comments, which about money saving, i also want to say something about it. Money saving is really good idea, because, if you keep save your money then,  you can use this money when you really need to use, no doubt there are many way's for saving your money but i think banks are one of the best place for save your money ...
trailer hire Brisbane
machinegunate
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
May 16, 2013, 06:49:17 AM
 #17

Swing and a miss...
malhoni
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
May 16, 2013, 10:29:43 AM
 #18

Made me laugh.
Koekienmonster
Newbie
*
Offline Offline

Activity: 23
Merit: 0



View Profile
May 16, 2013, 11:31:27 AM
 #19

Made me laugh.
Dasneko
Member
**
Offline Offline

Activity: 82
Merit: 10


View Profile
May 16, 2013, 11:58:32 AM
 #20

What keeps your bitcoins secure is not the address they are sent to but your secret "private key".
How secure is that? Well since its not bound to your identity like lets say a bank account its security lies in being "hidden". That said since its not bound to your identity someone cant pose to be you and gain access to your account. In essence its one of the most secure systems on this planet.
Pages: [1] 2 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!