setup-wizard.yml

version: "2"
fields:
  - id: GRAFFITI
    target:
      type: environment
      name: GRAFFITI
      service: validator
    title: Graffiti
    maxLength: 32
    description: >-
      Add a string to your proposed blocks, which will be seen on the block explorer.
  - id: checkpointSyncUrl
    target:
      type: environment
      name: CHECKPOINT_SYNC_URL
      service: beacon-chain
    title: Checkpoint for fast sync
    description: >-
      To get Caplin up and running in only a few minutes, you can start Caplin from a recent finalized checkpoint state rather than syncing from genesis. This is substantially **faster** and consumes **less resources** than syncing from genesis, while still providing all the same features. Be sure you are using a trusted node for the fast sync.
      Use the Dappnode Official endpoint `https://checkpoint-sync-gnosis.dappnode.io` or the official one from Gnosis `https://checkpoint.gnosischain.com`.
      *Note - If you are going to provide your own checkpoint sync endpoint, make sure you do not use a slash `/` at the end of the URL.*
    required: false
  - id: feeRecipientAddress
    target:
      type: environment
      name: FEE_RECIPIENT_ADDRESS
      service: validator
    title: Fee Recipient Address
    description: >-
      Fee Recipient is a feature that lets you specify a priority fee recipient address on your validator client instance and beacon node. Make sure this is an address you control. After The Merge, Execution Clients will begin depositing priority fees into this address whenever your validator proposes a new block.
      Ensure compatibility with Erigon3 by properly setting this address.
    required: true
    pattern: "^0x[a-fA-F0-9]{40}$"
    patternErrorMessage: Must be a valid address (0x1fd16a...)
  - id: nodeType
    target:
      type: environment
      name: NODE_TYPE
      service: beacon-chain
    title: Node Type
    description: >-
      Choose the type of node you want to run. Archive nodes store all historical data, Full nodes store historical data and the current state, and Minimal nodes store only the current state.
      If you are unsure, choose Full. If you are  low on disk space, choose Minimal. If you want to have all the data, choose Archive.
      *Note - this setting cannot be changed after the node is running.*
    required: true
    enum:
      - Minimal
      - Full
      - Archive