ethereum / ethereum/staking-launchpad

Launchpad still refers to Infura as a possibility for the execution layer

Open
#607 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
304
Forks
226
PR merge metrics
No merged PRs in 30d

Description

I think #448 and #527 missed the text displayed in
https://github.com/ethereum/staking-launchpad/blob/dev/src/pages/SelectClient/SelectClientSection.tsx

"To process incoming validator deposits from the execution layer
(formerly 'Eth1' chain), you'll need to run an execution client as well as your
consensus client (formerly 'Eth2'). You can use a third-party service
like Infura, but we recommend running your own client to
keep the network as decentralized as possible."

The translations also contain
"36j2ls": [
{
"type": 0,
"value": "To process incoming validator deposits from the execution layer (formerly 'Eth1' chain), you'll need to run an execution client as well as your consensus client (formerly 'Eth2'). You can use a third-party service like Infura, but we recommend running your own client to keep the network as decentralized as possible."
}
],

referenced in key
36j2ls

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.