Try   HackMD

UX for Becoming a Validator in Ethereum

As the proof of stake network matures, we would like to revist the user experience for first time users and provide some suggested revisions to both the Ethereum.org site as well as the Launchpad. These suggested revisions are intented to provide a more streamline and predictable way of entry into the Beacon Chain network as a validator/staker and help steer users away from unintented consequences such as premature penalties, onboarding to wrong network, and staking when not ready.

Current Entry Point(s)

Created with Raphaël 2.2.0Google.comGoogle.comEthereum.orgEthereum.orgLaunchpadLaunchpaddeposit clideposit cliBeacon NodeBeacon Nodeeth1eth1becoming a staker ethereumget stakingcreate keysupload  keymetamask depositlink to Beacon Nodeinstall Beacon Nodereg/install clientsync client or get urlbegin beacon syncui onboardingwait for activation
  • cons
    • pushes newusers into setting up Mainnet instead of Testnet
    • has users deposit before they are synced on eth1/eth2 beacons which may result in user getting penalized on their original stake for not setting up quick enough
Created with Raphaël 2.2.0Ethereum.orgEthereum.orgBeacon NodeBeacon Nodeeth1eth1LaunchpadLaunchpaddeposit clideposit cliurlinstall Beacon Nodereg/install clientsync client or get urlbegin beacon synclink to mainnet/testnetcreate keysupload  keymetamask depositlink to Beacon Nodeui onboardingwait for activation

url - https://ethereum.org/en/eth2/get-involved/

  • cons
    • perpetuates the term eth2 or ethereum 2.0 when searching get involved
    • Beacon Node URL outdated

Ideal Entry Point

Created with Raphaël 2.2.0Google.comGoogle.comEthereum.orgEthereum.orgLaunchpadLaunchpadBeacon NodeBeacon Nodeeth1eth1deposit clideposit clibecoming a staker ethereumpick your networkmainnet/testnetget stakinglink to Beacon Nodeinstall Beacon Nodereg/install clientsync client or get urlbegin beacon syncbegin ui onboardingui password creationreturn to create keyscreate keysupload  keymetamask depositimport key/enter key passwordwallet password creationcomplete ui onboardingwait for activation

or

Created with Raphaël 2.2.0Beacon NodeBeacon Nodeeth1eth1LaunchpadLaunchpaddeposit clideposit cliChoose your networkmainnet/testnetinstall Beacon Nodereg/install clientsync client or get urlbegin beacon syncbegin ui onboardingui password creationreturn to create keyscreate keysupload  keymetamask depositimport key/enter key passwordwallet password creationcomplete ui onboardingwait for activation

Suggested Revisions

Focus:

  • onboarding/beacon chain entry
  • individual experience ( as opposed to institution )

The following suggested revisions bring us closer to a streamlined predictable approach to entering the ethereum proof of stake network.

Ethereum.org

  • bring network (mainnet/testnet) selection into the forefront of participation
    • currently the main page forces users to join the mainnet right away which may bring unintended risk and confusion for new users, there should be more information around testnet participation and the corresponding launchpad urls
    • link users to the correct launchpad based on network selection
    • provide information on how to get initial eth based on network
  • begin migration away from use of Eth2 term and adjusting page (https://ethereum.org/en/eth2/get-involved/) for participation to reflect
  • update "get involved" website with new prysmatic labs website
    • currently still using old website

Launchpad

  • currently key actions ( syncing eth 1 and eth2 nodes ) from advisories section 9 (checklist) is easily missed
    • can we provide more warning on the select a client pages to ensure users are fully synced after installation or linked back to the check list
    • possibly even adding more warning on advisories section 9 to include risks for not completing checklist prior to deposit.
  • currently mentions "While you can use a third-party service like Infura, we recommend running your own client in order to ensure the network stays as decentralised as possible." is this the case for Test net as well ( reduces hardware requirements for testing)?
  • can we add during " choosing client sections " that setup should be for specific network ( launchpad network) that it's for x testnet so users are not accidentally syncing on the wrong network also repeating advisories on setup for the eth2 client?
    • perhaps provide some warning that without prior setup you may be subject to premature penalties ( activated validator without the validator running properly on machine)
  • provide more information on how to get initial eth for testnet onboarding
  • change UI design ( like color ) and possibly some of the risks based on network selection.
  • stretch: provide a launchpad for advanced users that would like to skip the checklist warnings ( suggestion detect if user already went through launchpad once somehow )
    • usecase for advanced users or ones that have been through the process prior
Last changed by 
 
Prysmatic Labs
eth2 development team
4
220

Read more

What Happens After Finality in ETH2?

A fundamental property of blockchains is the notion of "finality," which roughly means that after a certain period of time, transactions that have been included in the canonical chain are extremely difficult or almost impossible to revert. Eth2 has an "explicit" mechanism of chain finality enshrined within the protocol, which is different from the "probabilistic" finality found in proof-of-work chains such as Ethereum or Bitcoin today. In proof of work, consensus is fundamentally a global race that a lucky miner wins by being the first to produce a valid block: a result of finding a mathematical solution to a computationally difficult problem. As such, block times are probabilistic. The more blocks are added to the chain, the harder it is to revert, as each represents a cumulative sum of electrical and computational power required to create it. Given there are real, physical guarantees that would prevent an attacker from being able to revert the Bitcoin and Ethereum blockchains today, we can consider transactions past a certain amount of time included on-chain as "finalized." The objective of Stateless Ethereum RPC is to enable the client to operate without the need to store the entire state tree. Ethereum proof of stake, however, does not function on the concept of probabilistic finality. Instead, it enshrines finality into the protocol by saying "If > 2/3s of validators have voted correctly on the chain head for a long period of time, we can consider everything before a specific checkpoint as finalized". Finality is explicit, and nodes that follow the protocol will not be able to revert the finalized checkpoint as it is fundamentally impossible regardless of consensus weight. How Finality Works in ETH2 ETH2 is a synchronous protocol that operates on a "checkpoint" mechanism for bookkeeping. Essentially, a set of validators is assigned to either produce blocks or vote on blocks in a window of 32 potential slots. Each slot is a period of 12 seconds. Those 32 slots constitute an epoch. In an epoch, there are 32 assigned block proposers and everyone else is known as an attester, assigned to vote on proposed blocks once per epoch. There is only one block proposer assigned per slot, but many "attesters" can be assigned per slot For example, Alice is selected as a block proposer for slot 4 in the epoch and Bob, James, Charlie, and Susan are assigned as attesters at slot 4, meaning they should be voting on Alice's produced block as canonical.

Jul 4, 2024
Migrating Prysm to Slog

Contextual logging:

Dec 6, 2023
Running BOLD Challenges on Sepolia

This guide will set up

Nov 17, 2023
Generalized History Commitment

Today in BOLD, challenges can have subchallenges, and we have a total of 3 levels. We do this because at each challenge, validators have to commit to N state roots of a block’s history, which can be very expensive to compute. For example, computing 2048 machine hashes for the execution of a block and collecting them takes around 5 minutes on a modern MacBook Pro.

Aug 16, 2023
Read more from Prysmatic Labs
Published on HackMD