GHOST Square Ethernet protocol

A solitary block caused problems

The ether 1.0 square block out time decreased to about 15s, published block propagation time in the network itself needs to 10 seconds, no other node has enough time to receive the block, will become the norm that the bifurcation, and the number of bifurcation will be a lot, a lot of solitary block (orphan block) are not earnings. At the same time these forked force distribution caused by operator, to the security of Ethernet Square will bring risks, detailed analysis, see mining difficult chapters can not be too low .

Center brings more than proportional benefits (centralization bias)

Not the longest chain of legitimate solitary block not block out the awards for the miners to pay a count for nothing force. Also particularly unfair for artisanal miners, if artisanal miners and mining pools dug block almost simultaneously, resulting bifurcation, then mine pool because of the large proportion of operator force, is likely to continue to dig into the next block, all will continue along its own mining blocks dug up, and artisanal miners since the count is weak, can only hope that other miners continue mining along their block, so to get their own reward, but for other miners to He said there was no reason to mining along this block. So mine pool to become block legitimate longest chain of higher probability, been disproportionate advantage count forces.

In practice, the network location of large mining pools better, more quickly dug regional block will be released to other nodes, so the pool of relatively large-scale mining and artisanal miners is more likely to block reward.

For other miners, they will be more inclined to take the latter extent of mining in the mine pond, behind the artisanal miners since then, most likely on the white dig, which in turn makes the mine pool to obtain a greater probability of reward .

Two, GHOST agreement

The core idea of ​​the agreement is void GHOST blocks can also get some reward, this means the force will not be wasted, to solve the problems caused by temporary bifurcation.

To encourage consolidation fork contains an invalid block Winning block can receive an additional reward Ethernet 1/32 times the normal currency, in order to ensure the value of the currency Ethernet, can contain up to two blocks uncle.

Reward uncle block obtained was 2/8 ~ 7/8 times the normal award shown below:
Here Insert Picture Description
Design of the old block uncle reason rewards can be obtained:

  • Since winning a block can only contain two blocks uncle, more than two such a way that the blocks can be rewarded uncle.
  • Published slow, not enough time to be included uncle blocks can also be rewarded.
  • Mine prevent malicious competition pool, if not deliberately block belonging to contain the opponent's uncle came in, then the next block can still include it on a block uncle, rewarded.
  • Block reward decreasing uncle, uncle encouraged to include block as soon as possible.

Uncle block verification

Ether Square bonus award includes a block (block reward) and petrol (gas fee). But the uncle block the transaction is not executed, there is no need to verify the validity of inside trading, and therefore will not block uncle petrol. The actual cost of gasoline reward system is relatively low.

Uncle node just verify compliance with the difficulty of mining blocks, in line with the difficulty of mining block that is legitimate uncle uncle blocks corresponding to their uncle's uncle blocks rewarded according to seniority.

Block subsequent blocks uncle

Follow Block uncle blocks from being rewarded, otherwise malicious node could easily launch a fork attack, even if the attack fails bifurcation, bifurcation all blocks can also get the corresponding reward uncle. So subsequent blocks can not be rewarded.

Follow Block uncle blocks no reward but also encourage timely bifurcation merger, the miners more willing along the longest chain of legitimate mining.

Published 16 original articles · won praise 2 · Views 3258

Guess you like

Origin blog.csdn.net/ice_fire_x/article/details/104234567