Private network without kurtosis

[edonskov]

Hello!
I have a task to deploy a private network for educational purposes. However, one of the exercises is to practice the function of searching and connecting a new node to demonstrate the scalability of the network. But I can't find information about this in the new implementation of the private network through kurtosis. I don't understand how to add a new node to an already launched network.
Ideally, try to launch the minimum possible network with 1 geth without kurtosis, but get requires a client beacon.
Dev mode not good, cause there is no discovery for adding a new node.
Please help me understand what actions are required to correctly configure a network with a proof of stake consensus with a mining function. Maybe there is a full manual?

[1033309821]

When you start the network, you can configure the number of nodes in the network. If they are new nodes, their configs need to be consistent so that they can discover and connect to each other. You can find Kurtosis related materials here: https://geth.ethereum.org/docs/fundamentals/kurtosis. Also I don't understand how to

configure a network with a proof of stake consensus with a mining function.

Mining should not be required in PoS mode.

[yohanelly95]

Hi @1033309821 Ive tried this manually, but I get the error that

WARN [05-06|15:05:50.011] Forkchoice requested unknown head        hash=c26ab9..ea5ba4

on geth when I reach slot 0 for a PoS network.

Note that the beacon chain is running in parallel and at slot 0 it should bootstrap to a deneb network. But it always fails, no blocks are produced. I have added sufficient validators for consensus etc for the custom chain, no errors on that front.

On the CL(lodestar) I get the following error :

Execution Layer Syncing
Error: Execution Layer Syncing

EL is always left syncing and so the CL is never able to propose blocks and produceBlocksV3 on lodestar fails.

[the-shadow-coder]

Yeah, there could be a couple of issues here. The forkchoice requested unknown head error usually indicates a mismatch between the genesis.json used by the Execution Layer (EL) and the genesis.ssz used by the Consensus Layer (CL). This means they’re not aligned for the current fork configuration. It can also happen if the genesis block itself is not correctly set up.

To fix this, you can generate a consistent genesis using the Ethereum Genesis Generator:

🔗 https://github.com/ethpandaops/ethereum-genesis-generator

Setting up a private testnet without Kurtosis can be a bit tricky, but it's definitely doable—I just tested this setup a few days ago.

@eth-team I'd be happy to contribute a guide or documentation page here with detailed steps for setting up a custom network from scratch. Is there a preferred place where I can publish or propose this or any .md file in this repo will also be good ?

[edonskov]

Setting up a private testnet without Kurtosis can be a bit tricky, but it's definitely doable—I just tested this setup a few days ago.

@the-shadow-coder
Maybe you can create your own repo with md? It can help eth-team to decide faster and also help me with my issue :)