Skip to content

Commit

Permalink
fix references of builder's comparision factor to boost factor (#398)
Browse files Browse the repository at this point in the history
  • Loading branch information
g11tech committed Dec 21, 2023
1 parent cac30c0 commit 4882aa0
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions apis/validator/block.v3.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -53,22 +53,22 @@ get:
payload, and receives valid responses from both the builder endpoint _and_ the paired
execution node. When these preconditions are met, the server MUST act as follows:
* if `exec_node_payload_value >= builder_comparison_factor * (builder_payload_value // 100)`,
* if `exec_node_payload_value >= builder_boost_factor * (builder_payload_value // 100)`,
then return a full (unblinded) block containing the execution node payload.
* otherwise, return a blinded block containing the builder payload header.
Servers must support the following values of the comparison factor which encode common
Servers must support the following values of the boost factor which encode common
preferences:
* `builder_comparison_factor=0`: prefer the execution node payload unless an error makes it
* `builder_boost_factor=0`: prefer the execution node payload unless an error makes it
unviable.
* `builder_comparison_factor=100`: default profit maximization mode; choose whichever
* `builder_boost_factor=100`: default profit maximization mode; choose whichever
payload pays more.
* `builder_comparison_factor=2**64 - 1`: prefer the builder payload unless an error or
* `builder_boost_factor=2**64 - 1`: prefer the 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_comparison_factor` do not trigger overflows or errors. If this parameter is
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.
Expand Down

0 comments on commit 4882aa0

Please sign in to comment.