From 9d54722123d7388d1e5b194ac6ed3328bb1b6882 Mon Sep 17 00:00:00 2001 From: rolfyone Date: Tue, 24 Sep 2024 21:57:16 +0000 Subject: [PATCH] deploy: e7f7d70423b0abfe9d9f33b701be2ec03e44eb02 --- beacon-node-oapi.yaml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/beacon-node-oapi.yaml b/beacon-node-oapi.yaml index ba77d7a3..4976be5a 100644 --- a/beacon-node-oapi.yaml +++ b/beacon-node-oapi.yaml @@ -43951,18 +43951,17 @@ paths: Servers must support the following values of the boost factor which encode common preferences: - * `builder_boost_factor=0`: prefer the execution node payload unless an error makes it + * `builder_boost_factor=0`: prefer the local execution node payload unless an error makes it unviable. - * `builder_boost_factor=100`: default profit maximization mode; choose whichever + * `builder_boost_factor=100`: profit maximization mode; choose whichever payload pays more. - * `builder_boost_factor=2**64 - 1`: prefer the builder payload unless an error or + * `builder_boost_factor=2**64 - 1`: prefer the external builder payload unless an error or beacon node health check makes it unviable. Servers should use saturating arithmetic or another technique to ensure that large values of the `builder_boost_factor` do not trigger overflows or errors. If this parameter is provided and the beacon node is not configured with a builder then the beacon node MUST - respond with a full block, which the caller can choose to reject if it wishes. If this - parameter is **not** provided then it should be treated as having the default value of 100. + respond with a full block, which the caller can choose to reject if it wishes. If the value is provided but out of range for a 64-bit unsigned integer, then an error response with status code 400 MUST be returned. schema: