Bitcoin Forum
April 26, 2024, 06:18:21 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: conflict between btc address  (Read 711 times)
x_seed (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 12, 2014, 01:03:23 AM
 #1

well i was wondering if 2 address used to receiveBTC could conflict as i have notice that afew BTC clients generate the code even when i have unpluged the internet ! Undecided Huh Huh
1714112301
Hero Member
*
Offline Offline

Posts: 1714112301

View Profile Personal Message (Offline)

Ignore
1714112301
Reply with quote  #2

1714112301
Report to moderator
1714112301
Hero Member
*
Offline Offline

Posts: 1714112301

View Profile Personal Message (Offline)

Ignore
1714112301
Reply with quote  #2

1714112301
Report to moderator
1714112301
Hero Member
*
Offline Offline

Posts: 1714112301

View Profile Personal Message (Offline)

Ignore
1714112301
Reply with quote  #2

1714112301
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714112301
Hero Member
*
Offline Offline

Posts: 1714112301

View Profile Personal Message (Offline)

Ignore
1714112301
Reply with quote  #2

1714112301
Report to moderator
killinitsoftly
Member
**
Offline Offline

Activity: 81
Merit: 10


View Profile
April 12, 2014, 01:12:52 AM
 #2

In before quantum-sun pictures explaining that the chances of this happening are literally astronomical.
byt411
Hero Member
*****
Offline Offline

Activity: 798
Merit: 1000


View Profile
April 12, 2014, 01:14:39 AM
 #3

well i was wondering if 2 address used to receiveBTC could conflict as i have notice that afew BTC clients generate the code even when i have unpluged the internet ! Undecided Huh Huh

This question has been asked millions of times. Since you aren't bothered to search the forums, read this long debate:
https://bitcointalk.org/index.php?topic=560557.0
Light
Hero Member
*****
Offline Offline

Activity: 742
Merit: 502


Circa 2010


View Profile
April 12, 2014, 01:24:05 AM
 #4

This isn't a problem. To put things into perspective read below.

Quote
Statistically speaking, unless the protocol changes to accommodate more decimal places, only 2.1e14 addresses could contain at least one Satoshi, and that's only if everyone only had one Satoshi. If anyone has more (and pretty much everyone who has any has more than one Satoshi), then there are fewer occupied wallets.

Within the set of 2256 private keys, they only map to 2160 unique wallet addresses. So the question is how does 2160 compare to 2.1e14? One in a million? One in a trillion?
The answer is one in 6.9595 decillion. Since "decillion" isn't a commonly used word, I'll save you the bother of having to look it up: it's a one with 33 zeroes after it.

To put that 6.9595 decillion figure into perspective: The Earth has a diameter of 12,742 kilometers, giving it a surface area just shy of 50 million square kilometers. A square kilometer is 1 million square meters, and a square meter is one million square millimeters, meaning the surface area of the Earth, in millimeters, is just shy of 50 quintillion mm2.

So here's the game we'll play. I've got 140 trillion earth-sized spheres. On one of them, I have randomly selected a single square millimeter as the prize winning spot. Find it, and you'll get to spin the prize wheel to see how much you've won. The prize wheel currently has about 22 million spaces. 21 million of them contain less than a dollar. But you only get to spin the wheel if you can find the secret spot on the secret sphere.

Wanna play?
Abdussamad
Legendary
*
Offline Offline

Activity: 3598
Merit: 1560



View Profile
April 12, 2014, 01:40:30 AM
 #5

In before quantum-sun pictures explaining that the chances of this happening are literally astronomical.

My dyson sphere is bigger than yours!
Pages: [1]
  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!