Bitcoin Forum
March 28, 2024, 09:08:49 PM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: How to avoid nonce calculation  (Read 772 times)
Kevin7777777 (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
May 26, 2015, 03:02:47 PM
 #1


Miners spend a lot of computing power only to find the nonce in order to pull the hash number with a lot of ceros.
They compete with each other, to win the 25 bitcoin price.

Avoiding nonce calculations will stop bitcoin centralization.

We must use random number of transactions per block as an input to pick a winer miner choosing from the blockchain (the miner that solved each block) and the new miners (first miner that received and distributed every new transaction that is to be confirmed in the new block).

For example:

Number of transactions of the new block = 600

We generate a simple algorithm, maybe 600^3 = 216,000,000

Númber of blocks in the blockchain =  360,000

To pick the winer you put all the blocks from the block chain and the new transactions in a "circle" and start counting 216,000,000 positions around the circle. The miner that you pick, thats the winer for this new block.

Little diferences must be resolved and consensus reached to reply the new block to all miners.
1711660129
Hero Member
*
Offline Offline

Posts: 1711660129

View Profile Personal Message (Offline)

Ignore
1711660129
Reply with quote  #2

1711660129
Report to moderator
1711660129
Hero Member
*
Offline Offline

Posts: 1711660129

View Profile Personal Message (Offline)

Ignore
1711660129
Reply with quote  #2

1711660129
Report to moderator
"This isn't the kind of software where we can leave so many unresolved bugs that we need a tracker for them." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Delek
Full Member
***
Offline Offline

Activity: 157
Merit: 100


Salí para ver


View Profile WWW
May 26, 2015, 04:44:17 PM
 #2

W T F ?

\/\/\/\/\/\/\/
-> delek.net <-
/\/\/\/\/\/\/\
fbueller
Sr. Member
****
Offline Offline

Activity: 412
Merit: 265


View Profile
May 26, 2015, 05:19:00 PM
 #3

Taking the bait - this wouldn't work.

If the transaction history is used to elect a person to sign a block, then an attacker can attempt to modify the order of transactions so it favours them - and since reorgs are a perfectly natural phenomenon in bitcoin, if someone did this, the network would accept this longer chain.

Reordering transactions is far easier than accumulating a decent portion of the hashrate, so the attacks get easier.

Bitwasp Developer.
altcoinex
Sr. Member
****
Offline Offline

Activity: 293
Merit: 250


Director - www.cubeform.io


View Profile WWW
May 26, 2015, 06:11:08 PM
 #4


Miners spend a lot of computing power only to find the nonce in order to pull the hash number with a lot of ceros.
They compete with each other, to win the 25 bitcoin price.

Avoiding nonce calculations will stop bitcoin centralization.

We must use random number of transactions per block as an input to pick a winer miner choosing from the blockchain (the miner that solved each block) and the new miners (first miner that received and distributed every new transaction that is to be confirmed in the new block).

For example:

Number of transactions of the new block = 600

We generate a simple algorithm, maybe 600^3 = 216,000,000

Númber of blocks in the blockchain =  360,000

To pick the winer you put all the blocks from the block chain and the new transactions in a "circle" and start counting 216,000,000 positions around the circle. The miner that you pick, thats the winer for this new block.

Little diferences must be resolved and consensus reached to reply the new block to all miners.


I think you may not have a full and clear understanding of what the nonce does, and how the proof of work system actually works. It seems like you have a loose general understanding but you may be missing some aspects of how the proof of work system that is the core of bitcoin functions.

If you remove the nonce, it is either arbitrary as you will still be reordering transactions or altering the block time to produce a valid hash, or your completely changing the protocol/proof of work design/relevantly everything about bitcoin, in which case you need to elaborate in a great manner more of technical detail than just a whim idea with no real consideration to technical implication.

In this scenario, you essentially giving the majority of the future coins to those that have already solved blocks, which is far worse for distribution.

Also, one would be motivated to create bogus transactions to other addresses one owns sending through mining nodes you control so that they are the ones who distribute it to the network to get better chances to win.

As Bueller said, one would also be motivated to reorder transactions or other block details to ensure a likelihood of it resulting in an outcome in their part of the 'circle' or otherwise favorable to them.

Those are just the first considerations that come to mind....

It is great to be thinking of new options, features, variations, applications and modals for bitcoin and blockchain technology; but it is in vain if you either don't understand the actual application, or have not thought it out far enough to see if it is actually valid, or how it would be accomplished(to know that it can, and can in a manner with cost/reward worth doing).


                                     ╓╢╬╣╣╖
                                   ┌║██████║∩
                                   ]█████████
                                    ╜██████╝`
                                      ╙╜╜╜`
                                   ╓╥@@@@@@╥╓
         ╓╖@@╖,                 ,@║██████████╢@,                 ,╓@@╖╓
       ╓╢██████╢.              ╓╢███████████████╖               ║╢█████║╓
       ║█████████    ,,╓╓,,   ┌║█████████████████┐   ,,╓╓,,    ]█████████
       └╢██████║` ╓╢║██████╢║∩``╙╙╙╙╙╙╙╙╙╙╙╙╙╙╙╙╙`»╢╢██████╢║╖  ║███████╜
         "╜╜╜╜` ╖╢█████████╣╜                      └╢██████████@ `╜╜╜╜╜
               ║██████████╜                          ╙╢██████████
              ┌█████████╜                              ╙╢█████████
              └███████╨`                                 ╜████████
               ║████╨╜                                    `╢█████
                ╙╢╣╜                                        └╢█╜
                ,,                                            ,,
             ╓@║██┐                                          ┌██║@╓
            ╢██████                                          ]█████H
           ╢███████∩                                        ┌████████
  ╓@@@@╓   █████████                                        ║████████`  ╓@@@@╖
╓╢██████║. █████████∩                                      ┌█████████ ,║███████╖
██████████ └█████████                                      ██████████ ]█████████
`║██████╜`  └╢████████                                    ┌███████╣╜   ╙██████╨`
  `╙╜╜╙`      `╙╨╢████                                    █████╝╜`       `╙╜╜`
                      ]@╓                              ╓╖H
                      ███╢║@╓,                    ,╓@╢╢███`
                      ████████╢@╖╓.           ╓╖@║████████`
                      ]███████████╢║@╓,  ,╓@╢╢████████████
                       ╙╢█████████████╨` ╜██████████████╜
                         ╙╝╢███████║╜`    `╜║████████╝╜`
                     ,╓@@@╓  `²╙``             `╙²`  ╓@@@╖,
                    ║╢█████╢H                      ╓╢██████H
                    █████████                      █████████`
                    ╙╢██████╜                      ╙╢██████╜
                      └╨╩╝┘                          └╨╩╝╜
WINFLOW.
██
██
██
██
██
██
██
██
██
██
██
██
██
..
██
██
██
██
██
██
██
██
██
██
██
██
██
.
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!