-
Test fails randomly half of the time, needs fixing
```
Running: tests/p2p/les/test_flow_control
[OK] consistent costs
/home/arnetheduck/status/nim-beacon-chain/vendor/nim-eth/eth/p2p/rlp…
-
## Description
The BN can follow the beacon chain whilst the EE is syncing, this is called *optimistic sync*. A node has an *optimistic head* when the head of the beacon chain has not been verified…
-
Currently, we faced with a problem relate to queue_monitoring package when use Bus::chain:
[2021-08-10 03:41:22] local.ERROR: class_parents(): Class Closure (ABC.php:) does not exist and could not …
-
**Description**
Print the set feeRecipient on startup of the VC for each validator
**Example**
`info: Validator exists in beacon chain validatorIndex=xx, pubKey=0xxx, feeRecipient=Ox39`
**…
-
### Description
As a node operator, I want the `eth_syncing` endpoint to be consistent with the specification so that I can write integration tests against the client.
### Acc…
-
```
23:28:29.436 INFO keep-entry: [member:2] submitting relay entry [0x14ee9abbe50a50706e84b315095a74fcad4ac0bcb9e2f2226ec17b3e08d51afc135c61f0c22ed57361d7ca211e3fa27ac8660cd71449a2deaa565d40b228df0…
-
## Overview
Port over the [beacon chain consensus helper algos](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#helper-functions) to huffmate (in their respective …
-
Because we are promoting our current development environment to other teams in Status, i think we should stop using `config.nims` file in root directory, i'm talking about https://github.com/status-im…
-
network: holesky
validators: 3.3k attached through web3signer
some of them appear to be invalid (i.e the same attester index doesnt appear in both logged attestations), but there are indeed valid …
-
Should the asterisk not be retained if we're in a chain of digipeaters?
When we digipeat the packet, should we keep the asterisk next to BERR37*? along with
adding the asterisk to our own callsig…