owned this note
owned this note
Published
Linked with GitHub
You might have heard of the term ["Ethereum 2.0"](https://etherworld.co/2021/01/02/ethereum-2-0-basic-terminology/) or "The Merge" if you have been following the blockchain space lately. To know more about The Merge, read our article [here](https://etherworld.co/2022/07/20/what-do-bellatrix-paris-ttd-mean-in-ethereum-merge-upgrade/).
In short, "The Merge" is just a transition of Ethereum from a PoW to a PoS implementation. Ethereum 1 was all about PoW i.e. using Computer hardware and electricity to add a new block and mine for Ethereum. However, Ethereum 2.0 will use Proof of Stake, i.e. users will participate in the blockchain by staking their ETH and become a validator, making Ethereum more reliable, scalable, secure and environmentally liable, and eco-friendly.
In this post we are gonna talk about:
---
### Table of Contents
* <a href="#section1" class="btn"> What is Beaconchain? </a>
* <a href="#section2" class="btn"> What is Ethereum Node? </a>
* <a href="#section3" class="btn"> What are Nodes and Clients? </a>
* <a href="#section4" class="btn"> How Node Works? </a>
* <a href="#section5" class="btn"> Why should I Run Ethereum Node? </a>
* <a href="#section6" class="btn"> Beaconchain Node API </a>
* <a href="#section7" class="btn"> Prysm </a>
* <a href="#section8" class="btn"> Lighthouse Book </a>
---
<h1 class="section one" id="section1"> What is Beaconchain? </h1>
As it can be risky to move to PoS mechanism right away. Since there are thousands of existing smart contracts operating on the Ethereum chain, with billions of dollars in assets at stake. So as the first step of this upgrade, Ethereum launched something called Beacon Chain on December 1st, 2020. Beacon Chain is nothing but a separate Ethereum chain that works on PoS which is running along with Mainnet without affecting anything on it. In the Next stage, the Beacon chain will connect to Mainnet in an event popularly known as "The Merge". With this, the transition of Ethereum from PoW to PoS will be completed.
Unlike the Ethereum Mainnet, the Beacon Chain does not handle transactions or smart contracts. Instead, it coordinates the entire Ethereum network by randomly assigning stakers (who validate the proof of stake blocks) to validate different shards. Shards consist of different shard blocks which run independently as their blockchain. Instead, of running the entire Ethereum network validators can just validate the node to which they are assigned and the transactions associated with that shard.
<iframe width="560" height="315" src="https://www.youtube.com/embed/nJ57mkttCH0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
Indeed, these are the two features of the Beacon Chain that make it important for the new upgrade. The Beacon Chain has always been a part of Ethereum founder Vitalik Buterin’s vision since 2015 for what eventually Ethereum should become.
<h1 class="section two" id="section2"> What is Ethereum Node? </h1>
An Ethereum node is software that runs the Ethereum network. Ethereum is a distributed network of computers (known as nodes) running software that can verify blocks and transaction data. The software application, known as a client, must be run on your computer to turn it into an Ethereum node.
<h2 class="section three" id="section3"> What are Nodes and Clients? </h2>
A "node" is any instance of Ethereum client software (like a computer) that is connected to other computers also running Ethereum software, forming a network. Depending on what the needs are each node will interpret data differently and offer different retrieve updated information for your client.
On the other hand, a client is an implementation of Ethereum that verifies data against the protocol rules and keeps the network secure. These clients are useful for developers as they let them interact with the network and other network nodes.
<h2 class="section four" id="section4"> How Node Works? </h2>
As we all know Ethereum currently consists of two layers:
- **The Execution Layer**: It listens to new transactions which are broadcasted in the network, executes them, and holds all the information about Ethereum.
- **Consensus Layer**: It follows proof-of-stake and enables the network to be validated by validators and also to achieve agreement based on validated data from the execution client.
With the Merge, Ethereum transitions to proof-of-stake by connecting these networks. Consensus clients and execution clients work together to verify Ethereum's state.
![](https://i.imgur.com/5mPyHOF.png)
<center><h6><a href="https://ethereum.org/static/7a59bdb7a666b01a74535e8bea21a532/8b936/eth1eth2client.png">Simplified diagram of a coupled execution and consensus client.</a></h6></center>
<h2 class="section five" id="section5"> Why should I Run Ethereum Node? </h2>
Even though you don't get the same financial rewards as validators or miners do, running a node on Ethereum has many other benefits, including privacy, security, reduced dependence on third-party servers, censorship resistance, and improved network health and decentralization.
By running your node, you can use Ethereum privately, independently, and without trust. The data can be verified by you with your client, so there is no need to trust the network. It is a popular blockchain mantra to "don't trust, verify.".
<h1 class="section six" id="section6"> Eth Beacon Node API </h1>
API specification for the beacon node, which enables users to query and participate in Ethereum 2.0 phase 0 beacon chain.
All requests by default send and receive JSON, and as such should have either or both of the "Content-Type: application/json" and "Accept: application/json" headers. In addition, some requests can return data in the SSZ format. To indicate that SSZ data is required in response to a request the header "Accept: application/octet-stream" should be sent. Note that only a subset of requests can respond with data in SSZ format; these are noted in each individual request.
To participate in Ethereum's proof-of-work system there are two steps:-
**1) Running Clients:**
Running a client means you'll be an active participant in Ethereum. Your client will help keep track of transactions and check new blocks. One of the popular js based Clients is [beacon-api-client](https://github.com/ralexstokes/beacon-api-client) developed by ralexstokes. It follows [Eth Beacon Node API](https://ethereum.github.io/beacon-APIs/#/).
**2) Staking ETH:** Staking is the act of depositing 32 ETH to activate validator software. As a validator, you’ll be responsible for storing data, processing transactions, and adding new blocks to the blockchain. This will keep Ethereum secure for everyone and earn you new ETH in the process.
For learning more about how to run a node you can visit [here](https://ethereum.org/en/run-a-node/)
<h2 class="section seven" id="section7"> Prysm </h2>
Prysm is one of the platform that supports the official Eth Beacon Node API specification, the official API standard developed by the Ethereum. The specification describes a RESTful set of endpoints which should be implemented by an Eth beacon node or a third-party service. This reduces the overhead of having to learn a new set of APIs when trying out a different client, and it allows network participants to reliably talk to each other over HTTP.
The API is exposed by default on 127.0.0.1:3500. Performing a request is straightforward - simply concatenate the host with the port and the API's URL, providing any required URL and query parameters.
<h2 class="section eight" id="section8"> Lighthouse Book </h2>
Lighthouse also implements the standard Beacon Node API specification. A Lighthouse beacon node can be configured to expose a HTTP server by supplying the `--http` flag. The API includes several endpoints which can be used to trigger heavy processing, and as such it is strongly recommended to restrict how it is accessed. Using `--http-address` to change the listening address from localhost should only be done with extreme care.
## Similar Reads
* [What do Bellatrix, Paris & TTD mean in Ethereum Merge Upgrade?](https://etherworld.co/2022/07/20/what-do-bellatrix-paris-ttd-mean-in-ethereum-merge-upgrade/)
* [Ethereum Mainnet Shadow Forking: An Overview](https://etherworld.co/2022/04/20/ethereum-mainnet-shadow-forking-an-overview/)
* [The Merge Transition](https://youtu.be/pyfKM_hOKaM)
* [Proof of Stake](https://www.youtube.com/watch?v=z5pw1sCHBQU)
* [Ethereum: The Great Renaming](https://youtu.be/nJ57mkttCH0)
<font size="2" color=#a6a6a6>
*Disclaimer: The information contained on this web page is for education purposes only. Readers are suggested to conduct their research, review, analyze and verify the content before relying on them.*
To publish press releases, project updates, and guest posts with us, please email contact@etherworld.co.
Subscribe to EtherWorld [YouTube channel](https://www.youtube.com/channel/UCnceAY-vAQsO8TgGAj5SGFA) for ELI5 content.
Support us at [Gitcoin](https://gitcoin.co/grants/5287/etherworld)
If you've something to share with the blockchain community, join us on [Discord](https://discord.io/EtherWorld)!
Follow us at [Twitter](https://twitter.com/ether_world), [Facebook](https://www.facebook.com/etherworld2017), [LinkedIn](https://www.linkedin.com/company/etherworld/), and [Instagram](https://www.instagram.com/etherworld.co/).
</font>