NAOFinance Mainnet Announces BSC Binance Smart Channel

On December 1, Ethereum developer Tim Beiko published an article explaining how the integration of Eth1 and Eth2 could affect the Ethereum application layer. 1. Block structure: The blocks in the tag chain have merged execution loads equal to the credentials blocks of the current operation. ExecutionPayloads is an interactive site with Ethereum. 2. Mining and Uncle Blocks: Several fields in the header of the Proof-of-Work block are obsolete and set to approximately 0. Because the proofs of stakes do not generate the uncle blocks like the proof of operation, the names of the uncle blocks are empty, and the hash of the names becomes an RLP encoded hash of the empty names. 3. Replace BLOCKHASH and DIFFICULTY opcodes: BLOCKHASH opcodes have low pseudo-randomness, DIFFICULTY opcodes have been modified and renamed to RANDOM. 4.Average block design time: about 13 seconds now, reduced to 12 seconds after sharing 5. Security header and final block: Rebuildable as proof of work. The final block is approved by more than 2/3 of the certificates. To create a collision, the attacker must break at least 1/3 of the total contract (currently around 2.5 million ETH, worth up to US $ 10 billion). A security header block is a block that must be placed in a specific directory in a network instance. Assuming the network latency is less than 4 seconds, the security header will not be an orphan block unless most validator nodes are fair and have no objection to the fork option. .