Forum Home
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    Bitcoin QT user gets an address that already exists!

    Feathercoin Discussion
    10
    13
    2410
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      chrisj Regular Member last edited by

      @alikim from Bitcointalk put up this post: [url=https://bitcointalk.org/index.php?topic=314617.0]I generated an address that already exists[/url]

      In his words:
      [quote]That shouldn’t be very probable, should it?

      I used Bitcoin Qt client, pressed “New address” button to generate the address, sent a small amount to it and then checked on blockchain.info if the transaction was registered. To my surprise there are two other transactions made over a year ago using that address.

      https://blockchain.info/address/1J9UHx3q9D1ZxZ5KwV8VGWJd7ksyTJtLTB[/quote]

      If this is true is this a problem for all QT clients?

      1 Reply Last reply Reply Quote 0
      • M
        Magic8Ball Regular Member last edited by

        Its random chance. Very small chance but a finite one nonetheless.

        1 Reply Last reply Reply Quote 0
        • Bushstar
          Bushstar last edited by

          Wow. This is going to be one to watch. Chances are if he did generate a private key to an address already in use then there is a flaw in the RNG. We will watch to see the result and possible fix.

          Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz

          1 Reply Last reply Reply Quote 0
          • M
            mnstrcck last edited by

            This is kind of cool actually, if it happened on a minute statistically probable level.

            1 Reply Last reply Reply Quote 0
            • U
              UKMark last edited by

              As with all probabilities there is a chance of it happening. However the address space is amazingly massive, the odds of this happening are a staggering.
              2^160
              or
              1,461,501,637,330,902,918,203,684,832,716,283,019,655,932,542,976 to 1 :o

              1 Reply Last reply Reply Quote 0
              • M
                mnstrcck last edited by

                [quote name=“UKMark” post=“31925” timestamp=“1382276030”]
                As with all probabilities there is a chance of it happening. However the address space is amazingly massive, the odds of this happening are a staggering.
                2^160
                or
                1,461,501,637,330,902,918,203,684,832,716,283,019,655,932,542,976 to 1 :o
                [/quote]

                He should play the lottery.

                1 Reply Last reply Reply Quote 0
                • A
                  adamstgbit last edited by

                  [quote name=“erk” post=“31912” timestamp=“1382271375”]
                  That’s the way it’s designed, there is no checking to see if an address is unique. It’s supposed to be improbable.
                  [/quote]

                  i guess the Client could look at TX history when generating bitcoin address, but it shouldn’t have to, its really is 999,000,000,000,000,000,000 in 1 chance of getting a collision

                  1 Reply Last reply Reply Quote 0
                  • kris_davison
                    kris_davison last edited by

                    I guess technically both of them as its the same logical account. First to move the coins wins I suppose. That’s a scarry thought.

                    Is there anything stopping me just creating millions of new accounts looking to duplicate accounts? Its almost mining in itself?

                    1 Reply Last reply Reply Quote 0
                    • kris_davison
                      kris_davison last edited by

                      Although with that huge number millions isn’t going to cut it.

                      1 Reply Last reply Reply Quote 0
                      • K
                        Kevlar Spammer last edited by

                        There’s no proof of this. The most likely candidate is that user error is involved.

                        Nothing to see here.

                        1 Reply Last reply Reply Quote 0
                        • ghostlander
                          ghostlander Regular Member last edited by

                          Come on guys, no panic :) It’s his address. He used it previously for a 50 BTC change when sent 50 BTC using a 100 BTC input. He had this change spent later, and there is a record of this transaction in his wallet. So, his client has re-used an old address.

                          1 Reply Last reply Reply Quote 0
                          • kris_davison
                            kris_davison last edited by

                            so this number is somewhere in the region of a Thousand quinquavigintillion or Quinquagintillion if you happen to be american (who happily renamed all the large numbers).

                            1 Reply Last reply Reply Quote 0
                            • R
                              raptorak last edited by

                              [quote name=“Kevlar” post=“32006” timestamp=“1382306044”]
                              There’s no proof of this. The most likely candidate is that user error is involved.

                              Nothing to see here.
                              [/quote]

                              This is what happened. Someone already had him go through diagnostics and found that the address he “generated” was actually one he had before. He had restored a backup which stores 100 addresses in the beginning. This “new” address was just because he backed up his wallet, restored it and it was running through the spool of 100 and that was the next address in the line.

                              In other words, it was user error. The same thing has been reported over and over by different people and so far every time it’s been from people restoring from backups and not understanding how the addresses are stored.

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post