Sort:  
  • Trending
    • [-]
     8 years ago 

    I would not call that a quick buck. It probably took a very good knowledge in EC cryptography and some research effort to find this short cut (if he really found one).

    [-]
     8 years ago 

    If he found a short cut, there is no way except to exploit the same short cut to beat him.
    If he has a GPU miner than hat's off to him, he is the only one who has it. No one could beat him.

    $0.00
      Reply
      [-]
       8 years ago 

      @alpha I'm guessing it's a GPU miner if the name is GTX-1080. That, or he loves his new nvidia card so much he named the accounts after it.

      $0.00
        Reply
        [-]
         8 years ago 

        No amount of CPU mining will beat a GPU. I promise you unless you have access to like 1k+ cores to work with. That's why GPU mining is so much better, faster and efficient. CPU's are number crunching machines and everything is onboard the card so no bottle-necking just pure unadulterated computational work.

        $0.00
          Reply
          [-]
           8 years ago 

          As I point out, his nonce computation is different. It is possible that he might have a GPU miner.

          $0.00
            Reply
            [-]
             8 years ago (edited)

            I really didn't want to start tearing apart source tonight but there goes the evening, and on goes the coffee. I just finished optimizing my stupid CPU miner to hit about 7 or 8 blocks a day but if no one gives a crap out playing fair then it's so on...

            $0.00
              Reply
              [-]
               8 years ago 

              This is the ​quote from @arhag's post about the new algorithm​.

              So the real solution is to simply get rid of the degree of freedom provided when the system allows the user to arbitrarily choose the private key d (or at least the system should allow no more of a degree of freedom than that allowed by iterating a nonce or account name which changes the pseudorandom cryptographic hash output that is used as the private key). So the private key d should instead be deterministically determined by a cryptographic hash dependent on the latest_block_id, miner_account_name (this is to necessary to prevent the PoW from being stolen by another account within the same block), and the nonce. input should also depend on those three values, so it can simply be defined as the SHA256 cryptographic hash of the private key d. The rest of the algorithm is more or less kept the same.

              $0.00
                Reply