<<  >> (p.5)
    Author Topic: Sick of the confirmation time...  (Read 4303 times)
    MegaFall
    Jr. Member
    *
    Offline Offline

    Activity: 56
    Merit: 1


    View Profile
    March 25, 2015, 07:20:27 PM
     #81

    What should happen is if a block takes more than 15 minutes to find, the difficulty should temporarily plunge.

    Also, how can that be implemented without a central time server?

    Does each node not have the time of the last block? When the clock on each node is over 15 minutes from the last block, send out a request to other nodes to confirm that they too agree it's been over 15 minutes, if there is a consensus among say 60% of the nodes that the time since the last block was over 15 minutes, then temporarily reduce the difficulty until the next block is found; then it goes back up to where it was.

    What happens if I'm a new node that just finished syncing, and receive a 20-min block with reduced difficulty? I have no way to know an agreement has happened, and will reject the block.

    So? You'd be one node of the thousands... you're rejection should have no bearing on what the other nodes do... once the other nodes confirm the block and a subsequent one, would your node not then accept it as being part of the chain and move on? Seems highly illogical and a major flaw in the design if it wouldn't.
Page 4
Viewing Page: 5