Bernard Stojanović
Bernard Stojanović
## Description After following instruction from [scripts/local_testnet](https://github.com/sigp/lighthouse/tree/unstable/scripts/local_testnet) block is not initialized with one beacon node ## Version branch `unstable` (Lighthouse/v1.0.4-c1e27f4+) ## Present Behaviour running one beacon node and validator in...
On the Tutorial -> `Build a blockchain` -> `Authorize specific nodes` There is a wrong URL in the example for using a dependency https://docs.substrate.io/tutorials/build-a-blockchain/authorize-specific-nodes/#add-node-authorization-dependencies
 Currently, logs screen dose not show most relevant, to fix this when user get to the screen it should scroll to bottom of the logs and stick on bottom...
As the current state of adding beacon node flow is kinda confusing  We should change the title to `Add your beacon node ` move input to a separate window...
The electron has 2 processes by default `main` and `renderer` Now we keep all processes on `renderer` that start causing UI freezes due to blocking resource usages (loops API calls...
Observed few times that running and syncing 2 nodes (latest case `lighthouse` and `teku`) will fall in some type of limbo and stuck and same syncing state. Tests need to...
Lighthouse fix issues with a local test-net setup which required at least 2 beacon node to interpolate https://github.com/sigp/lighthouse/issues/2094#event-4590744307
implement check if is enough deposit made on contract _Originally posted by @mpetrunic in https://github.com/NodeFactoryIo/ChainGuardian/pull/370#discussion_r549337350_