4 votes
Accepted

What caused the forks in the Schlesi testnet?

What were the causes of the forks? There were some issues relating to rewards/penalties calculation. Both Lighthouse and Prysm were incorrectly computing the validator balances. Interestingly, ...
paulhauner's user avatar
  • 1,248
3 votes
Accepted

Ethereum beacon chain node (Lighthouse) fails to connect to GoEthereum

Any beacon chain node needs Engine JSON-RPC API available it to co-ordinate between consensus layer (beacon chain) and execution layer (GoEthereum). Normally the Engine API is exposed over special ...
Mikko Ohtamaa's user avatar
3 votes
Accepted

What is the tech stack behind the Lighthouse client?

What are Lighthouse's major components? From a very high level we have three components, each launched from the single lighthouse program: Beacon node: connects to the p2p network, verifies blocks ...
paulhauner's user avatar
  • 1,248
3 votes
Accepted

How do I expose and beacon chain API securely over HTTP and test my API works?

A beacon chain node port 5052 offers HTTP API with JSON and SSZ payloads. Any Internet facing port should have some sort of authentication, otherwise you will get a lot of knocking and random traffic. ...
Mikko Ohtamaa's user avatar
2 votes

GoEthereum and Lighthouse syncing issue: CRIT Failed to update execution head

It appears I had the same problem: Error 'CRIT Failed to update execution head' (Other related "Failed Called ... errors" ) started randomly appearing 30 hours ago; started with occasional ...
Udo's user avatar
  • 21
2 votes
Accepted

Beacon consensus client lighthouse syncing speed decrease every hour - might take 1+ month to sync fully

Syncing a full Ethereum node can be a resource-intensive process, and it's not uncommon for syncing speeds to decrease over time. However, there are a few things you can try to improve the speed: ...
Kevin Lee's user avatar
  • 128
2 votes

getting beacon node error after upgrading lighthouse client to v3.5.1

I had the same issue. This is an answer from the lighthouse developer michaelsproul. Just run lighthouse with --purge-db and --checkpoint-sync-url with one of the necessary nodes
Igor's user avatar
  • 121
1 vote

Geth reports it is synced when Lighthouse Beacon is not synced

Geth will only start sync process after full sync of Beacon chain. eth.syncing=false may indicate that the process do not started yet. Try the command eth.blockNumber to verify the newest block.
Rafael's user avatar
  • 348
1 vote

Checkpoint sync source for Ethereum beacon chain node

--checkpoint-sync-url https://[PROJECT-ID]:[PROJECT-SECRET]@eth2-beacon-mainnet.infura.io
mathewsun's user avatar
  • 111
1 vote
Accepted

Checkpoint sync source for Ethereum beacon chain node

In addition to popular infrastructure providers like Infura or QuickNode, you can now use various public endpoints from the Ethereum Beacon Chain checkpoint sync endpoints list. Endpoints from that ...
Rémy Roy's user avatar
  • 703

Only top scored, non community-wiki answers of a minimum length are eligible