-
### Description
Specifying a specific private key file is too hard with teku. A couple of improvements we should make:
- Automatically trim whitespace from the file before trying to parse as hex (c…
-
Tracking an improvement we could implement, we discussed it here: https://github.com/ConsenSys/teku/pull/6441#pullrequestreview-1180049006
-
Mplex is currently the main multiplexing protocol supported by all Ethereum consensus clients, while yamux `MAY` be supported:
https://github.com/ethereum/consensus-specs/blob/e3a939e439d6c05356c9c29…
jxs updated
11 months ago
-
It would be great to have metrics for all Teku's REST API endpoints. One use-case is to help monitor Beacon Nodes that are serving multiple Validator Clients. This data can also help any efforts to id…
-
With Eth2.0 merge approaching, would love to see new benchmark data on various Eth2.0 clients like Nimbus, Teku, Lighthouse, Prysm, Lodestar, etc once again! I think there was one done in [Feb 2021](h…
-
The weak subjectivity spec currently does not really define this behaviour, leading to client implementations potentially being inconsistent and dangerous . For example, my teku client simply went off…
-
There are several times where a node operator may want to use diffferent CLI flags than the ones that his beacon is currently running. Even if it were for just a few minutes. It would be nice to have …
potuz updated
2 years ago
-
Tried dshackle for a load balancer in several ETH2.0 clients (Lighthouse, Teku, Nimbus) and got this error: "_IllegalStateException: No executor delegate for eth_getLogs_". The host was Ubuntu 20.04.1…
E1458 updated
4 years ago
-
See [these notes](https://notes.ethereum.org/@ralexstokes/S1RSe1JlF) for some background.
> A first milestone here is to fork one of the production-grade beacon clients and build out the aforemention…
-
### Describe the bug
The endpoint returns `false` when sync is not started. It also randomly returns any value when a different consensus client is used on a stalled network.
```
curl -s -X POST…