The future of Geth and Hypra
author

tagKnife

February 06, 2024

The future of Geth and Hypra

Hypra has made huge strides in our goals to keeping a proof-of-work ethereum chain running and up to parity with Ethereum mainnet. This has not been without struggle most notable with the recent Gaspar fork to enable Shanghai where we failed the activate it the first time around due to code traps for beacon and Proof-of-stake. We did prevail in the end to activate the upgrade without any lasting breaking changes.

What is the future with Geth

The difficulty we faced with Gaspar showed us we need a different way to keep upgrading the chain with ethereum upgrades without fighting back Proof-of-stake. Ethereum devs has displayed anamosity to Proof-of-work in their upgrades, with highly opinionated work putting as much effort as possible to require chains to use Beacon.

This is dishearting as at the time when Ethereum switched to proof-of-stake and maliciously removed Proof-of-work code from the codebase. It is estimated 1000+ Proof-of-work chains were cut off from the feature pipeline unless they upgraded to use Beacon. Most of these chains used the base ethereum Geth with trust that ethereum wouldnt cut them off, but here we are.

The Hypra team has been exploring and researching possiblities to move away from the Ethereum base Geth towards other implimentations with a more sensable approach to the EVM ecosystem as a whole. That would allow Hypra to seemlessly upgrade the chain with easy and continued support.

Possible candidates

We have identified 2 possible candidates for this, both are modular in design and support multiple different networks within 1 codebase. They are actively developed and supported and frequently port ethereum features without the battle with Proof-of-stake.

Option 1: Nethermind
Nethermind is an ethereum client built with c#, with modularity and multichain support. Primarly designed to be a diversity client for ethereum.

Pros

  1. Fast and more efficeint, nethermind uses custom data storage and syncing methods to be faster.
  2. Funded developement, nethermind is a company with funding to support developement.
  3. Multichain support, supports Ethereum, Gnosis, Base, Optimism, POA and more.

Cons

  1. C#, the hypra team does not have adequate experience with C#.
  2. Company backing could lead to pushing there own narrative.

 

Option 2: eth-core
eth-core is a modified version of geth with modularity and multiple eth chain support as its there core princaples. With focus on supporting the base Ethereum protocal and building ontop of it.

Pros

  1. Modified Geth to support multiple chains and modular design.
  2. Backed by Ethereum Classic and Ethereum Foundation.
  3. Multichain support, supports Ethereum, Ethereum Classic, POA and Mint.
  4. Familiar code, based on geth so easier to get to grips with.

Cons

  1. Compared to Nethermind, slower to port over Ethereum features.

 

What would Hypra need to do to transition?

Part of the challange of adding support to either of these clients for Hypra would be to to port over EthashB3 and our custom reward distrobution. Unlike other ethereum based chains, Hypra has a predetermined decreasing mining rewards plan every 3 years, While other chains has a set base reward.

Adding the ethashb3 custom algorithm will not be hard as the modular design allows for such additions. But adding the custom chain paramters and chains might be difficult, we will see.

So for 2024, Hypra team will be working towards a modular client and deprecate the standard geth client, to help facilitate future chain upgrades with minimal brain fires. When we decide to upgrade to cancun we will not be doing so on geth and will fully migrate to the new client.

Top