-
holesky has 2 bootnodes and besu is disconnecting them perhaps too aggressively
timeout threshold is 3
and useless response threshold is 5
```
sallymacfarlane@dev-elc-besu-teku-holesky-dev-…
-
The beacon-api voluntary exit is probably more restrictive than it should be.
We should ideally be able to post an exit for a future epoch and have it in the pool. I'm not sure what it would mean as …
-
### Describe the bug
There are several bugs in the keymanager api endpoints. To be more precise:
## feerecipient, gas_limt, graffiti
The endpoints:
- `/eth/v1/validator//feerecipient`
- `/eth…
-
### Description
As an Besu Client, I set Besu blockperiod as 2 seconds,
I built a smartcontract, and use one single account to deploy this smartcontract 800 times. the deployment…
-
-
cc @jrhea
This issue is a proposal of including the following counter-measures as recommendations into discv5 spec. Clients should make their own decision on whether to implement them or not.
…
-
### Description
I'm aware that running different version combination is not best practice, but i think this is still worth mentioning:
Running a Teku VC `24.8.0` with a Teku BN `24.10.1` (with d…
-
# Please supply an AppArmor profile for Teku
You know your application best and what it requires from the OS. Being able to easily "lock it down" inside a container to those paths it needs would be…
-
That would be the fourth page named *Install Ethereum 2.0* on [the figma mockups](https://www.figma.com/file/awkKHUCaDXju2czEnXvxC7/StakeHouse-UI-Design?node-id=0%3A1). This is the page where you sele…
-
From customer:
---
Getting these errors in teku beaconchain service when syncing along with `Geth/v1.14.11-stable-f3c696fa`.
Teku version: `teku/v24.10.3/linux-x86_64/-eclipseadoptium-openjdk64bits…