LiveL1DevNetwork provides a local obscuro network running on a live L1 Caller should provide a wallet per node and ideally an RPC URL per node (may not be necessary but can avoid conflicts, e.g.

NewInMemDevNetwork provides an off-the-shelf default config for a sim network tenConfig - the requirements of the L2 network we are spinning up l1Network - the L1 network we are running the L2 network on nodeOpL1Wallets - the funded wallets for the node operators on the L1 network (expecting 1 per node).

WithPredictableDeployer - will use a known private key for the deployer instead of generating a random one.

InMemDevNetwork is a local dev network (L1 and L2) - the TEN nodes are in-memory in a single go process, the L1 nodes are a docker geth network It can play the role of node operators and network admins to reproduce complex scenarios around nodes joining/leaving/failing.

InMemNodeOperator represents an Obscuro node playing a role in a DevSimulation Anything a node operator could do, that we need to simulate belongs here, for example: * start/stop/reset the host/enclave components of the node * provide convenient access to RPC clients for the node * it might even provide access to things like the database files for the node if needed Note: InMemNodeOperator will panic when things go wrong, we want to fail fast in sims and avoid verbose error handling in usage.

L1Config tells network admin how to setup the L1 network.

TenConfig describes the L2 network configuration we want to spin up.

L1Network represents the L1Network being used for the devnetwork (it could be a local geth docker network, a local in-memory network or even a live public L1) todo (@matt) - refactor to use the same NodeOperator approach as the L2?.