Coinbase, the digital asset exchange, has acknowledged user concerns regarding its heavy reliance on the Go Ethereum (Geth) execution client and has revealed its efforts to enhance diversity in this regard.
In a recent post on X (formerly Twitter), Coinbase addressed community worries about the dominant usage of Geth as the sole execution layer on the platform, assuring users that plans were underway to address this issue.
According to the statement, the lack of execution client diversity has been a significant concern for both users and the Coinbase team. As a result, the platform is actively working to reduce its complete dependence on Go Ethereum.
The post also disclosed that when launching the staking feature on the platform, Geth was the only execution client that met the exchange’s requirements, which contributed to its predominant use.
Coinbase Cloud places the utmost emphasis on the security of customer assets and the underlying blockchain infrastructure. When we introduced Ethereum staking and assessed execution layer clients to optimize these critical aspects, Geth emerged as the sole client that met our rigorous technical criteria.
Back in 2022, two years prior to the launch of the staking feature, Coinbase Cloud and other network operators arrived at the same conclusion, resulting in the prevalence of Geth.
At present, 84% of Ethereum validators rely on Geth, but there are ongoing efforts to develop and scale alternative solutions with the potential for network integration in the future.
Coinbase emphasized its commitment to taking client diversity seriously to enhance the overall user experience. The exchange also mentioned that it will conduct further evaluations and reach conclusions regarding the next steps in this direction, with the details expected to be unveiled in February.
Coinbase user flags Geth dominance
The recent controversy began when a user voiced concerns on X (formerly Twitter) regarding the potential risk posed by the dominance of Geth to the system. The user emphasized the possibility of losing their assets in the event of an unforeseen Geth consensus bug, leading them to decide that the risk was not acceptable.
Coinbase CEO Brian Armstrong took note of this incident and pledged to investigate the matter that prompted this comprehensive response from the platform.
Addressing previous concerns
In February 2022, Coinbase also grappled with similar concerns regarding client diversity in Ethereum 2.0 (eth2), particularly in relation to validators heavily relying on Prysm. The exchange emphasized the importance of safeguarding user assets on the network and made the decision to begin with Prysm because it was the most viable option at the time.
To enhance security for eth2 validators on Coinbase, the platform introduced remote signers. This feature allowed validators to generate and store keys in isolated environments rather than keeping them on the validator itself, significantly boosting security measures.
As a result of their commitment to client diversity and providing users and partners with more choices, Coinbase concluded its efforts to onboard Lighthouse remote signers, thereby expanding options in the ecosystem.
