-
PR: https://github.com/ethereum/consensus-specs/pull/3800
EIP: https://eips.ethereum.org/EIPS/eip-7742
Wait for merge and implement
Plus we don't need this until we have at least 1 EL which suppor…
-
## Description
Running `eth2fuzz_teku` on Windows results in the following error:
```
[eth2fuzz] Testing FuzzerJavaJQFAfl is available
No such file or directory (os error 2)
```
All 4 of the…
-
### Description
A fresh sync of mainnet Ethereum on Besu using snap sync got through FastImportBlocksStep, but did not start worldstate heal. It was "stuck" here.
### Steps to Reproduce (Bug)
…
-
### Describe the issue
Add tutorial on how to use Besu and Teku to launch a local Casper PoS devnet.
### What page has the issue?
n/a
### Issue type
Missing content
### Change suggestion
_No re…
-
### Description
- Find how to extract the Teku OpenAPI doc for key management (equivalent to https://ethereum.github.io/keymanager-APIs/#/Remote%20Key%20Manager but with the Teku source directly)
-…
-
Besu is timing out on the FCU. Restarting Besu is the only way to fix the error.
Seeing a lot of logs with
```
io.vertx.core.VertxException: Thread blocked
at java.base/jdk.internal.misc…
-
Currently, Lighthouse VC does not support this at process level, instead we have to provide per validator key value. Both Prysm and Teku VCs provide this option.
Prysm: https://docs.prylabs.network/…
-
I have the following running on a machine :
- geth - fully synced with Ephemery
- teku - talking to geth, and synced with Ephemery, with `--rest-api-enabled=true`
- checkpointz - with teku upstre…
-
Currently, Lighthouse VC does not support default builder config values. Instead, we have to specify per validator key. Both Prysm and Teku VCs provide this option.
Prysm: https://docs.prylabs.netw…
-
Hi,
This started happening recently, any idea what could it be and if I may have some misconfiguration?
```
lighthousebeacon | Jul 2XXXXX WARN Builder returned invalid payload parent…