Follows %TzTraffic MVP

Now that we have the basic tools to run a local (incomplete) simulation/copy of a Tezos network, the goal is :

• To be able to deploy it on a simulated network of many machines
• To be able to copy more precisely (and more completely) the traffic from the copied network
• To build tools to monitor and evaluate results of experiments

Infra:

• Deploy tztraffic-nodes including an Octez-node + an Octez-baker both using the yes-crypto patched with <tezos-respo>/scripts/patch-yes_node.sh
• have all Octez nodes automatically start from the same snapshot/data-dir
• distribute delegate keys to each node (and patch their wallet using dune exec <tezos-repo>/devtools/yes_wallet/yes_wallet.exe convert wallet <path to wallet directory> inplace to make it compatible with the yes crypto
  • improve yes_wallet generator as described in #1
• add monitoring to each tztraffic-nodes:
  • teztale archivers that feed a single teztale server
  • metrics/grafana monitoring
• observe that the chain progresses
• ensure the deployed network has different name and bootstrap nodes
• ensure the spawned network is isolated but provide entrypoints
• maybe add a minimal block explorer to the spawned network
• Future work:
  • allow tztraffic nodes to be heterogeneous
    • hide all/some baker behind a front node
    • config heterogeneity (history mode, numbers of connections, etc.)
    • software heterogeneity (release versions)
    • introduce “hardware” heterogeneity
    • introduce misbehaviours:
      • add delays
      • force disconections
      • etc.
  • reduce network size by having multiple keys handled by a single tz-traffic node
  • make experiment faster using by warping time for each tz-traffic node (maybe using faketime)
  • ...

Traffic Generator

• Handle all types of operations
• Deep transformations of operations to adapt to the copied network
• Generate a report from tztraffic regarding the experiment

Tools

• Provide a minimal block explorer for the simulated network
• Evaluate the difference between resulting contexts on both network

Validation Experiment

At the end of the quarter, Tztraffic and tznet should be able to :

• Precisely simulate mainnet using 100 machines with different parameters, example : with block time of 10s.

Closed on 2023 Sept. 7th, unticked goals are transferred to the follow-up milestone or canceled according the new objectives. Follow-up in %Octez releases are manually tested in realistic simulated network