feat(blockchainnodeengine): update the api

#### blockchainnodeengine:v1 The following keys were added: - schemas.EthereumDetails.properties.beaconFeeRecipient.deprecated (Total Keys: 1) - schemas.EthereumDetails.properties.validatorConfig.$ref (Total Keys: 1) - schemas.ValidatorConfig (Total Keys: 2)
googleapis · Dec 7, 2023 · c21fe23 · c21fe23
1 parent f0d3b8d
commit c21fe23
Show file tree

Hide file tree

Showing 2 changed files with 45 additions and 6 deletions.
diff --git a/docs/dyn/blockchainnodeengine_v1.projects.locations.blockchainNodes.html b/docs/dyn/blockchainnodeengine_v1.projects.locations.blockchainNodes.html
@@ -128,14 +128,19 @@ <h3>Method Details</h3>
     },
     &quot;apiEnableAdmin&quot;: True or False, # Immutable. Enables JSON-RPC access to functions in the `admin` namespace. Defaults to `false`.
     &quot;apiEnableDebug&quot;: True or False, # Immutable. Enables JSON-RPC access to functions in the `debug` namespace. Defaults to `false`.
-    &quot;beaconFeeRecipient&quot;: &quot;A String&quot;, # An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as &quot;suggested&quot;, as we run the execution node we can trust the execution node, and therefore this is considered enforced.
+    &quot;beaconFeeRecipient&quot;: &quot;A String&quot;, # Deprecated: Use the same field in the ValidatorConfig message as replacement. An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as &quot;suggested&quot;, as we run the execution node we can trust the execution node, and therefore this is considered enforced.
     &quot;consensusClient&quot;: &quot;A String&quot;, # Immutable. The consensus client.
     &quot;executionClient&quot;: &quot;A String&quot;, # Immutable. The execution client
     &quot;gethDetails&quot;: { # Options for the Geth execution client. See [Command-line Options](https://geth.ethereum.org/docs/fundamentals/command-line-options) for more details. # Details for the Geth execution client.
       &quot;garbageCollectionMode&quot;: &quot;A String&quot;, # Immutable. Blockchain garbage collection mode.
     },
     &quot;network&quot;: &quot;A String&quot;, # Immutable. The Ethereum environment being accessed.
     &quot;nodeType&quot;: &quot;A String&quot;, # Immutable. The type of Ethereum node.
+    &quot;validatorConfig&quot;: { # Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client. # Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client.
+      &quot;mevRelayUrls&quot;: [ # URLs for MEV-relay services to use for block building. When set, a GCP-managed MEV-boost service is configured on the beacon client.
+        &quot;A String&quot;,
+      ],
+    },
   },
   &quot;labels&quot;: { # User-provided key-value pairs.
     &quot;a_key&quot;: &quot;A String&quot;,
@@ -245,14 +250,19 @@ <h3>Method Details</h3>
     },
     &quot;apiEnableAdmin&quot;: True or False, # Immutable. Enables JSON-RPC access to functions in the `admin` namespace. Defaults to `false`.
     &quot;apiEnableDebug&quot;: True or False, # Immutable. Enables JSON-RPC access to functions in the `debug` namespace. Defaults to `false`.
-    &quot;beaconFeeRecipient&quot;: &quot;A String&quot;, # An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as &quot;suggested&quot;, as we run the execution node we can trust the execution node, and therefore this is considered enforced.
+    &quot;beaconFeeRecipient&quot;: &quot;A String&quot;, # Deprecated: Use the same field in the ValidatorConfig message as replacement. An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as &quot;suggested&quot;, as we run the execution node we can trust the execution node, and therefore this is considered enforced.
     &quot;consensusClient&quot;: &quot;A String&quot;, # Immutable. The consensus client.
     &quot;executionClient&quot;: &quot;A String&quot;, # Immutable. The execution client
     &quot;gethDetails&quot;: { # Options for the Geth execution client. See [Command-line Options](https://geth.ethereum.org/docs/fundamentals/command-line-options) for more details. # Details for the Geth execution client.
       &quot;garbageCollectionMode&quot;: &quot;A String&quot;, # Immutable. Blockchain garbage collection mode.
     },
     &quot;network&quot;: &quot;A String&quot;, # Immutable. The Ethereum environment being accessed.
     &quot;nodeType&quot;: &quot;A String&quot;, # Immutable. The type of Ethereum node.
+    &quot;validatorConfig&quot;: { # Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client. # Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client.
+      &quot;mevRelayUrls&quot;: [ # URLs for MEV-relay services to use for block building. When set, a GCP-managed MEV-boost service is configured on the beacon client.
+        &quot;A String&quot;,
+      ],
+    },
   },
   &quot;labels&quot;: { # User-provided key-value pairs.
     &quot;a_key&quot;: &quot;A String&quot;,
@@ -302,14 +312,19 @@ <h3>Method Details</h3>
         },
         &quot;apiEnableAdmin&quot;: True or False, # Immutable. Enables JSON-RPC access to functions in the `admin` namespace. Defaults to `false`.
         &quot;apiEnableDebug&quot;: True or False, # Immutable. Enables JSON-RPC access to functions in the `debug` namespace. Defaults to `false`.
-        &quot;beaconFeeRecipient&quot;: &quot;A String&quot;, # An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as &quot;suggested&quot;, as we run the execution node we can trust the execution node, and therefore this is considered enforced.
+        &quot;beaconFeeRecipient&quot;: &quot;A String&quot;, # Deprecated: Use the same field in the ValidatorConfig message as replacement. An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as &quot;suggested&quot;, as we run the execution node we can trust the execution node, and therefore this is considered enforced.
         &quot;consensusClient&quot;: &quot;A String&quot;, # Immutable. The consensus client.
         &quot;executionClient&quot;: &quot;A String&quot;, # Immutable. The execution client
         &quot;gethDetails&quot;: { # Options for the Geth execution client. See [Command-line Options](https://geth.ethereum.org/docs/fundamentals/command-line-options) for more details. # Details for the Geth execution client.
           &quot;garbageCollectionMode&quot;: &quot;A String&quot;, # Immutable. Blockchain garbage collection mode.
         },
         &quot;network&quot;: &quot;A String&quot;, # Immutable. The Ethereum environment being accessed.
         &quot;nodeType&quot;: &quot;A String&quot;, # Immutable. The type of Ethereum node.
+        &quot;validatorConfig&quot;: { # Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client. # Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client.
+          &quot;mevRelayUrls&quot;: [ # URLs for MEV-relay services to use for block building. When set, a GCP-managed MEV-boost service is configured on the beacon client.
+            &quot;A String&quot;,
+          ],
+        },
       },
       &quot;labels&quot;: { # User-provided key-value pairs.
         &quot;a_key&quot;: &quot;A String&quot;,
@@ -368,14 +383,19 @@ <h3>Method Details</h3>
     },
     &quot;apiEnableAdmin&quot;: True or False, # Immutable. Enables JSON-RPC access to functions in the `admin` namespace. Defaults to `false`.
     &quot;apiEnableDebug&quot;: True or False, # Immutable. Enables JSON-RPC access to functions in the `debug` namespace. Defaults to `false`.
-    &quot;beaconFeeRecipient&quot;: &quot;A String&quot;, # An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as &quot;suggested&quot;, as we run the execution node we can trust the execution node, and therefore this is considered enforced.
+    &quot;beaconFeeRecipient&quot;: &quot;A String&quot;, # Deprecated: Use the same field in the ValidatorConfig message as replacement. An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as &quot;suggested&quot;, as we run the execution node we can trust the execution node, and therefore this is considered enforced.
     &quot;consensusClient&quot;: &quot;A String&quot;, # Immutable. The consensus client.
     &quot;executionClient&quot;: &quot;A String&quot;, # Immutable. The execution client
     &quot;gethDetails&quot;: { # Options for the Geth execution client. See [Command-line Options](https://geth.ethereum.org/docs/fundamentals/command-line-options) for more details. # Details for the Geth execution client.
       &quot;garbageCollectionMode&quot;: &quot;A String&quot;, # Immutable. Blockchain garbage collection mode.
     },
     &quot;network&quot;: &quot;A String&quot;, # Immutable. The Ethereum environment being accessed.
     &quot;nodeType&quot;: &quot;A String&quot;, # Immutable. The type of Ethereum node.
+    &quot;validatorConfig&quot;: { # Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client. # Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client.
+      &quot;mevRelayUrls&quot;: [ # URLs for MEV-relay services to use for block building. When set, a GCP-managed MEV-boost service is configured on the beacon client.
+        &quot;A String&quot;,
+      ],
+    },
   },
   &quot;labels&quot;: { # User-provided key-value pairs.
     &quot;a_key&quot;: &quot;A String&quot;,

diff --git a/googleapiclient/discovery_cache/documents/blockchainnodeengine.v1.json b/googleapiclient/discovery_cache/documents/blockchainnodeengine.v1.json
@@ -487,7 +487,7 @@
       }
     }
   },
-  "revision": "20231108",
+  "revision": "20231129",
   "rootUrl": "https://blockchainnodeengine.googleapis.com/",
   "schemas": {
     "BlockchainNode": {
@@ -629,7 +629,8 @@
           "type": "boolean"
         },
         "beaconFeeRecipient": {
-          "description": "An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as \"suggested\", as we run the execution node we can trust the execution node, and therefore this is considered enforced.",
+          "deprecated": true,
+          "description": "Deprecated: Use the same field in the ValidatorConfig message as replacement. An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html or https://docs.prylabs.network/docs/execution-node/fee-recipient for examples of how this is used. Note that while this is often described as \"suggested\", as we run the execution node we can trust the execution node, and therefore this is considered enforced.",
           "type": "string"
         },
         "consensusClient": {
@@ -702,6 +703,10 @@
             "Holds the same data as full node as well as all of the blockchain's history state data dating back to the Genesis Block."
           ],
           "type": "string"
+        },
+        "validatorConfig": {
+          "$ref": "ValidatorConfig",
+          "description": "Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client."
         }
       },
       "type": "object"
@@ -955,6 +960,20 @@
         }
       },
       "type": "object"
+    },
+    "ValidatorConfig": {
+      "description": "Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client.",
+      "id": "ValidatorConfig",
+      "properties": {
+        "mevRelayUrls": {
+          "description": "URLs for MEV-relay services to use for block building. When set, a GCP-managed MEV-boost service is configured on the beacon client.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
     }
   },
   "servicePath": "",