Shulou(Shulou.com)06/02 Report--

(the picture is from the Internet, and the copyright belongs to the original author.)

In the last hedgehog article, we introduced how the podcast chain realizes Dpos, and its essential process is: node An is packaged, the packaged block is sent to other nodes, and other nodes judge whether it should be packaged by A node according to the current time. If so, the package is considered successful; if not, the package is considered to have failed.

When we look at the above process, we find a question: how is the first packaging node determined?

There seems to be a problem of chicken or egg first.

The node generates a transaction with itself as the packaging node, and the transaction is sent to other nodes. After getting the transaction, the other nodes need to make sure that the node is the packaging node.

See, I wound myself in.

How does the broadcast chain solve this problem?

Here are a few concepts:

Verifier: the account used by the packaging node to package. For example, node An is packaged, then it needs to have an account when it is packaged, and this account is a verifier.

We know that Etay Fong has a concept called Coinbase, which is to set up the account used by this node when mining, so the process should be like this when the podcast chain is started:

Let's take a look at steps 5, 6 and 7:

The fifth step is to unlock the specified account. In this way, the account is the Coinbase of this node.

Step 6, set the Coinbase to the local validator, which will not generate transactions. The reason for this step is to avoid the problem of chicken or existing eggs mentioned above when making a trading judgment.

Step 7, set the Coinbase as the verifier, which will result in a transaction.

The eighth step is mining. Since a transaction has just been generated, mining in step 8 ensures that the transaction is packaged into a block, so that all subsequent activated nodes will get the block and will know that the account ("0x86bfbc33d4bef890c347d28fb714c00bf66c37a7") is the verifier.

With the first verifier, the broadcaster chain can normally handle transactions and package blocks.

But there can't be only one verifier.

We know that DPOS requires many validators, and the number of verifiers is the same as the number of super nodes. That means the broadcaster chain needs 23 verifiers.

How did these verifiers come into being? After it comes into being, how to notify the whole network and make them work?

Next time, let's talk about the first important contract of the broadcaster chain, the voting contract, and talk about how the broadcaster chain interacts with the contract and gets the results of the contract.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.