-
Notifications
You must be signed in to change notification settings - Fork 20.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Private geth+prysm node #29772
Comments
First, I'd like to point out that Ethereum PoS is permissionless. Meaning anyone who gets their hands on enough ether in a network can become a validator and propose blocks. If your use-case is a private "permissioned" network, this will not be suitable for you. Otherwise: I think you will appreciate kurtosis. Save this to a file: participants:
- el_type: geth
cl_type: prysm
count: 3
additional_services:
- dora and then with a simple command:
you will have a network with 3 geth-prysm pairs, and a block explorer on top. |
@s1na I'm trying to set up a real-world copy of Ethereum without any connecton to real Ethereum (mainnet or testnets). If you have an additional comments, I'll be very appreciate it |
Ok then will close here. |
Hello @sergey-msu , have you made connection each other succesfully? I'm also trouble in same. I hope you leave some hint for it. |
Hi,
I'm trying to setup a full imitation of Eth mainnet - a PoS network which I plan to use far beyond testing purposes.
The requirements are
As I understand (please correct me if I'm wrond), I should use a private setup as a starting point: init geth with a genesis block, then start PoS concensus+validator node, and finally raise up other network nodes it the same way.
The first problem I faced - Geth and Prysm do not see each other.
Can anyone help me with initial setup?
my genesis.json:
which I pass to Geth as
./geth --datadir=gethdata init genesis.json
Then I start Geth with the command
./geth --http --http.api eth,net,web3 --ws --ws.api eth,net,web3 --authrpc.jwtsecret jwtsecret --datadir gethdata --nodiscover --syncmode full --allow-insecure-unlock --unlock 0x4e80Bb36022bF5947e0A00fF3701510c0efEEad4 --password password.txt
Then I start the Prysm
./beacon-chain --datadir=beacondata --execution-endpoint=http://localhost:8551 --chain-id=1234 --jwt-secret=jwtsecret --accept-terms-of-use --rpc-host=0.0.0.0 --grpc-gateway-host=0.0.0.0 --contract-deployment-block=0
the latter periodically shows the error
ERROR execution: Unable to process past deposit contract logs, perhaps your execution client is not fully synced error=processPastLogs: no contract code at given address
There are also some outputs in Geth console that seems strange to me, like
The Merge is not yet available for this network!
Engine API started but chain not configured for merge yet
Served eth_coinbase reqid=3 duration="15.964µs" err="the method eth_coinbase does not exist/is not available"
Finally, I start the validator
./validator --datadir validatordata --accept-terms-of-use --wallet-dir=./validator_wallets --beacon-rpc-provider=beacon-chain:4000 --datadir=./validatordata
which says
Please, tell me what could be the problem?
May be I should choose a different setup for my network?
The text was updated successfully, but these errors were encountered: