From c7c51062ab8e7568600c3d8d72066ca9eeeb801f Mon Sep 17 00:00:00 2001 From: Nikita Kryuchkov Date: Tue, 9 May 2023 07:15:06 +0000 Subject: [PATCH] Fix log on initializing external block builder (#4267) ## Issue Addressed #4266 ## Proposed Changes - Log `Using external block builder` instead of `Connected to external block builder` on its initialization to resolve the confusion (there's no actual connection there) ## Additional Info The log is mentioned in builders docs, so it's changed there too. --- beacon_node/execution_layer/src/lib.rs | 2 +- book/src/builders.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/beacon_node/execution_layer/src/lib.rs b/beacon_node/execution_layer/src/lib.rs index 09be379d24..16a7f3665f 100644 --- a/beacon_node/execution_layer/src/lib.rs +++ b/beacon_node/execution_layer/src/lib.rs @@ -328,7 +328,7 @@ impl ExecutionLayer { info!( log, - "Connected to external block builder"; + "Using external block builder"; "builder_url" => ?url, "builder_profit_threshold" => builder_profit_threshold, "local_user_agent" => builder_client.get_user_agent(), diff --git a/book/src/builders.md b/book/src/builders.md index f2a4b3936a..fc42f9b743 100644 --- a/book/src/builders.md +++ b/book/src/builders.md @@ -178,7 +178,7 @@ You can check that your builder is configured correctly by looking for these log On start-up, the beacon node will log if a builder is configured: ``` -INFO Connected to external block builder +INFO Using external block builder ``` At regular intervals the validator client will log that it successfully registered its validators