nimbus-eth2/beacon_chain/nimbus_light_client.nim.cfg

-d:"chronicles_sinks=textlines[dynamic],json[dynamic]"
-d:"chronicles_runtime_filtering=on"
-d:"chronicles_disable_thread_id"

@if release:
  -d:"chronicles_line_numbers:0"
@end

-d:"json_rpc_websocket_package=websock"
add light client (standalone) (#3653) Introduces a new library for syncing using libp2p based light client sync protocol, and adds a new `nimbus_light_client` executable that uses this library for syncing. The new executable emits log messages when new beacon block headers are received, and is integrated into testing. 2022-05-31 10:45:37 +00:00			`-d:"chronicles_sinks=textlines[dynamic],json[dynamic]"`
			`-d:"chronicles_runtime_filtering=on"`
			`-d:"chronicles_disable_thread_id"`

			`@if release:`
			`-d:"chronicles_line_numbers:0"`
			`@end`
use `nim-websock` instead of `news` (#4061) `news` has a few open issues that are not present in `nim-websock`: 1. There is a 1 second delay between each MB of sent data. 2. Cancelling an ongoing `send` makes the entire WebSocket unusable. 3. Control packets do not have priority over ongoing message frames. Using `news`, there are quite a few of these messages in Geth: ``` Previously seen beacon client is offline. Please ensure it is operational to follow the chain! ``` It may take quite some time to reconnect when this happens. Using `nim-websock`, this message still occurs because `eth1_monitor` reconnects the EL connection when no new blocks occurred for 5 minutes, but reconnecting is quick and the message is rarer. 2022-09-06 21:41:33 +00:00
			`-d:"json_rpc_websocket_package=websock"`