-
BEP: 333
Title: BNB Chain Fusion
Status: Draft
Type: Standards
Created: 2023-11-29
# BEP-333: BNB Chain Fusion
[BEP-333: BNB Chain Fusion](#bep-333-bnb-chain-fusion)
- [1. S…
-
## Description
I'm trying to setup a private network through this repo. It works for me with this docker-compose.yml:
```
version: "3.9"
services:
create-beacon-chain-genesis:
image: "gc…
-
Currently, the commitment returns the root of the Beacon block plus its timestamp. While this is the most canonical form of the commitment, it is difficult to verify on-chain as the [beacon roots cont…
-
**Describe the bug**
The Ethereum validator detects no valid validators, although the keys are load onto the web3signer.
**To Reproduce**
Dappnode OS is installed
The validator docker stora…
-
## Recent BlockHeaders / Ephemeral BlockHeaders
EL `BlockHeader`s that are still in the current `period` cannot have a proof against `historical_summaries` as they are not part of the used `sta…
-
**Describe the bug**
After about a month of uptime, Nimbus beacon node crashed and refuses to start anymore complaining database is malformed. This happened on two separate hosts about 1h apart.
…
-
## Description
On `peer-das-devnet-2`, I'm seeing the same block getting written to the database multiple times (4 times within 2 ms!). This occurred on a supernode.
I think this is because we k…
-
This will allow the beacon chain to start running and allow validators to get online and in sync, before the EVM execution chain comes online. This will be useful for
- Maintaing EVM state when re-ge…
-
### Problem description
Currently when it comes to [testing](https://chainsafe.github.io/lodestar/contribution/testing/) the correctness of new changes that involve interacting with `BeaconChain` we …
-
### Describe the bug
My lodestar `v1.21.0/ae1f9d5` fails to run after an upgrade.
```
Sep-09 11:58:43.501[] info: Lodestar network=mainnet, version=v1.21.0/ae1f9d5, commit=ae1f9d…