Network Selection and Bindings

GUI Network Selection

Allows defining a curated list of networks with human-readable names for UI display and selection.

gui:
  networks-select:
    <network-key>:
      name: <display-name>

Required fields per network:

• name: Human readable display name for the network

The network-key must correspond to a defined network in the networks section.

Example:

gui:
  networks-select:
    base:
      name: Base
    flare:
      name: Flare
    arbitrum:
      name: Arbitrum One

We'll need methods so that the front end can get a list of the available networks for the strat, and save it. The selected network will also need to go into state so it can be deserialized.

Network Bindings

Defines network-specific bindings that can be referenced in scenarios. When a network is selected, its bindings become available in the scenario context.

network-bindings:
  <network-key>:
    <binding-name>: <binding-value>

• Each network-key must correspond to a defined network in the networks section
• binding-name and binding-value are arbitrary key-value pairs
• Values are treated as strings and passed directly to the scenario context
• Bindings can be referenced in scenarios using ${network-bindings.}
• The active set of bindings is determined by the network of the deployment containing the scenario

Example:

network-bindings:
  base:
    raindex-subparser: "0x123abc"
    network-specific-constant: "42"
  
  flare:
    raindex-subparser: "0x456def" 
    flare-specific-value: "some-value"

Usage in scenarios:

scenarios:
  my-scenario:
    bindings:
      parser-address: ${network-bindings.raindex-subparser}

The network-bindings field can appear:

• In the main config YAML
• In separate YAML documents merged into the config
• Directly in .rain files as front matter

When a user selects a network from the networks-select GUI, the corresponding network bindings are automatically made available in the scenario context.