Tokenview.io Launches ETH 2.0 Beacon Chain Explorer

The all-currency blockchain browser Tokenview.io officially launched the ETH 2.0 Beacon Chain (Beacon Chain) browser. The purpose of the Beacon Chain is to support the transition from Proof-of-Work (PoW) to Proof-of-Stake (PoS), and it is the first step needed to complete the merger. It is reported that the merger of Ethereum is expected to happen around September 10th to 20th, but the hard fork of the beacon chain is determined to happen on September 6th.

01 About the beacon chain?

The Beacon Chain is a ledger of accounts that manages and coordinates a network of stakers. It is a completely independent decentralized network that runs in parallel to the Ethereum mainnet, and it does not process transactions or smart contract interactions. The Beacon Chain uses a proof-of-stake consensus mechanism instead of Ethereum's current proof-of-work consensus mechanism.

The role of the beacon chain is summarized as follows:

  • The Beacon Chain brings Proof-of-Stake to the Ethereum ecosystem.

  • The beacon chain will coordinate the network, serving as the consensus layer.

  • The beacon chain is an important precursor to upcoming scaling upgrades such as sharding.

The Beacon Chain transition began in November 2020 when the one-way bridge began moving the proof-of-work chain to the proof-of-stake chain and began accepting deposits. A month later, the Beacon Chain launched and acquired millions of ETH through multiple validators. So far, data on the Tokenview chain shows that the number of ETH2.0 pledges has exceeded 13.4 million ETH.

02 Beacon chain and merge?

The merge is a planned ethereum network upgrade that removes the proof-of-work consensus layer and merges the beacon chain's proof-of-stake network into the current ethereum mainnet. The merger will focus on upgrading the consensus mechanism and aligning it with its original mission: to migrate from proof-of-work to proof-of-stake, verify transactions on the blockchain, and add new blocks. The merger will have an immediate and far-reaching impact on the carbon footprint of the Ethereum network. It also lays the foundation for future scalability upgrades such as sharding.

03 Beacon chain introduces pledge

The Beacon Chain brings Proof of Stake to Ethereum. This is a new way to help keep Ethereum safe. Think of it as a public good that will make Ethereum healthier and users earn more ETH in the process.

Staking is similar to mining, but differs in many ways. The latter requires significant upfront expenditure in the form of powerful hardware and energy consumption, thereby generating economies of scale and facilitating centralization. Mining also does not require locked assets as collateral, which limits the ability of the protocol to punish bad actors after an attack. In contrast, the transition to proof-of-stake will make Ethereum more secure and decentralized. The more people participating in a network, the more decentralized it is and the less vulnerable it is to attacks.

Tokenview.io Launches Beacon Chain

The all-currency blockchain explorer Tokenview.io officially launched the ETH 2.0 beacon chain explorer. beacon.tokenview.io supports data query including validator information, block list, epoch list, and ETH2 deposit. The beacon chain browser launched this time is the 125th blockchain browser supported by Tokenview. The beacon chain will introduce a proof-of-stake consensus mechanism (PoS) and validators in Ethereum, and will eventually merge with the mainnet.

validator data

beacon.tokenview.io/cn/validator supports querying data information such as all validators, active validators, validators to be confirmed and withdrawn validators.

Era data

beacon.tokenview.io/cn/epoch supports the latest epoch, epoch details, and epoch block list.

block list

beacon.tokenview.io/en/slot supports the latest slot (slot) and fork block list data.

ETH2 deposit list

beacon.tokenview.io/cn/eth2deposits supports real-time query of ETH2 deposits, including deposits from Ethereum and deposits to Beacon.

Guess you like

Origin blog.csdn.net/Tokenview/article/details/127054732