Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

ValidatorConfig

import type { ValidatorConfig } from "https://googleapis.deno.dev/v1/blockchainnodeengine:v1.ts";

Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client.

interface ValidatorConfig {
beaconFeeRecipient?: string;
managedValidatorClient?: boolean;
mevRelayUrls?: string[];
}

§Properties

§
beaconFeeRecipient?: string
[src]

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.

§
managedValidatorClient?: boolean
[src]

Immutable. When true, deploys a GCP-managed validator client alongside the beacon client.

§
mevRelayUrls?: string[]
[src]

URLs for MEV-relay services to use for block building. When set, a GCP-managed MEV-boost service is configured on the beacon client.