Try   HackMD

🔥🧱Prysm setup instructions for Kiln🔥🧱

Configs are under: https://kiln.themerge.dev/

Prysm: Use github.com/prysmaticlabs/prysm, branch develop
https://github.com/prysmaticlabs/prysm/tree/develop

:warning: Any execution layer client will work but I'm using geth as an example :point_down:

Geth: Use github.com/MariusVanDerWijden/go-ethereum, branch merge-kiln-v2, and the latest commit 223e5f5681a9458a8f5066442d166acc28774328
https://github.com/MariusVanDerWijden/go-ethereum/tree/merge-kiln-v2

Prysm docker images:
Beacon node- gcr.io/prysmaticlabs/prysm/beacon-chain:latest
Validator- gcr.io/prysmaticlabs/prysm/validator:latest

The following steps start beacon node with bazel. If you are interested in using other methods to start up, check out the start up docs. The parameters are similar.

Setting up Prysm

Download genesis state: https://config.kiln.themerge.dev/cl/genesis/genesis.ssz
Download config: https://config.kiln.themerge.dev/cl/genesis/config.yaml

bazel run //beacon-chain -- \
--genesis-state $genesis_state_path \
--datadir $db_path  \
--http-web3provider=$execution_server  \
--chain-config-file=$config_path \
--bootstrap-node=enr:-Iq4QMCTfIMXnow27baRUb35Q8iiFHSIDBJh6hQM5Axohhf4b6Kr_cOCu0htQ5WvVqKvFgY28893DHAg8gnBAXsAVqmGAX53x8JggmlkgnY0gmlwhLKAlv6Jc2VjcDI1NmsxoQK6S-Cii_KmfFdUJL2TANL3ksaKUnNXvTCv1tLwXs0QgIN1ZHCCIyk

Setting up Geth

Download genesis.json: https://config.kiln.themerge.dev/el/genesis/geth.json

make
./build/bin/geth init genesis.json --datadir $geth_db_path

./build/bin/geth \
--datadir $geth_db_path \
--networkid=1337802 \
--http --http.api engine,net,eth \
--ws --ws.api net,eth,engine \
--bootnodes enode://c354db99124f0faf677ff0e75c3cbbd568b2febc186af664e0c51ac435609badedc67a18a63adb64dacc1780a28dcefebfc29b83fd1a3f4aa3c0eb161364cf94@164.92.130.5:30303
Last changed by 
 
Prysmatic Labs
eth2 development team
0
5056

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