Skip to content

Commit 48ebbcd

Browse files
nkryuchkovWoodpile37
authored andcommitted
Fix log on initializing external block builder (sigp#4267)
## Issue Addressed sigp#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.
1 parent 3dcf778 commit 48ebbcd

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

beacon_node/execution_layer/src/lib.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -377,7 +377,7 @@ impl<T: EthSpec> ExecutionLayer<T> {
377377

378378
info!(
379379
log,
380-
"Connected to external block builder";
380+
"Using external block builder";
381381
"builder_url" => ?url,
382382
"builder_profit_threshold" => builder_profit_threshold,
383383
"local_user_agent" => builder_client.get_user_agent(),

book/src/builders.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ You can check that your builder is configured correctly by looking for these log
178178
On start-up, the beacon node will log if a builder is configured:
179179

180180
```
181-
INFO Connected to external block builder
181+
INFO Using external block builder
182182
```
183183

184184
At regular intervals the validator client will log that it successfully registered its validators

0 commit comments

Comments
 (0)