Fork Identity


The blocks of the BigBang Core system are connected in chronological order to form a tree structure with multiple forks. In BigBang Core, the
security primary chain and application fork are collectively referred to as "fork". Each fork will have a unique fork identifier for marking. The
security primary chain uses the genesis block hash as the fork ID, and the application fork uses the hash of the first block after fork as the fork ID. Before the fork point, the parent chain and the application fork have the same chain structure and transaction; the fork points are
independent of each other and do not interfere with each other. The same Token that appears before the fork point can create different
transactions in the parent chain and the fork after the fork point to send to different addresses; The block data before the fork point can also be used in the parent chain and the fork chain. The user needs to specify an anchor block when creating the transaction, and all branches that are calibrated after this block are valid. In Figure 2.1, if the anchor block is set to Block n-1, the created transaction will be included in two forks; If set to Block n, the transaction is only valid in the parent chain, and a new transaction can be created in the fork to send the Token to another address.