feat: ethereum-package for real conditions network stress-test

[avilagaston9]

Add Ethereum Package

Description

Launches a local network using the ethereum-package with all Eigen and Aligned contracts deployed. Also adds some Makefile targets to launch and connect aligned components to the net.

• Start local net
• Add prefunded accounts.
• Add preloaded contracts.
• Connect the Batcher.
• Connect the Aggregator.
• Connect the Task Sender.
• Connect the Explorer.
• Connect Telemetry.
• Connect Operators.
• Spam transactions.
• Increase gas price

Warning

Kurtosis must be installed.

Note

new guide to use ethereum package:
docs/0_internal/ethereum_package.md

Commands

To start a local network run:

make ethereum_package_start

To restart the network run:

make ethereum_package_rm
make ethereum_package_start

To temporarily stop the network run:

make ethereum_package_stop

To start the batcher run:

make batcher_start_ethereum_package

To start the aggregator run:

make aggregator_start_ethereum_package

To start an operator run:

make operator_register_start_ethereum_package

To start Telemetry and the Explorer, run the usual commands:

make telemetry_full_start
make run_explorer

To spam transactions run:

make install_spamoor

and then:

make spamoor_send_transactions  \
  COUNT=<TOTAL_TX_TO_EXECUTE> \
  TX_PER_BLOCK=<LIMIT_OF_TXS_TO_SEND_PER_BLOCK> \
  TX_CONSUME_GAS=<HOW_MUCH_GAS_TO_USE_PER_TX> \
  NUM_WALLETS=<NUMBER_OF_WALLETS_FROM_WHICH_TO_SEND_TXS> \
  TIP_FEE=<TIP_TO_VALIDATORS>

For example:

make spamoor_send_transactions  \
  COUNT=10000 \
  TX_PER_BLOCK=200 \
  TX_CONSUME_GAS=150000 \
  NUM_WALLETS=1000 \
  TIP_FEE=10

In this scenario, we would be sending 200 transactions per block with an approximate consumption of gas of 150.000, amounting to a total usage of 200 * 150000 = 30.000.000 approximating the Ethereum block limit. Any block that exceeds 15.000.000 of gas used will increase the gas price.

Type of change

• New feature

Checklist

• “Hotfix” to testnet, everything else to staging
• Linked to Github Issue
• This change depends on code or research by an external entity
  • Acknowledgements were updated to give credit
• Unit tests added
• This change requires new documentation.
  • Documentation has been added/updated.
• This change is an Optimization
  • Benchmarks added/run
• Has a known issue
  • Link to the open issue addressing it
• If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
  • This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
  • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

[JuArce]

Seems ok. I will test it

[JuArce]

Sometimes it is needed to restart ethereum package to make it work.
Would be nice to add blockscout in another PR, so we have a block explorer available locally