due to some issue with anvil's --load-state restarting the chain at blockNumber 0, when we start anvil, we need to advance it artificially.
However, the current docker-compose file only starts the chain without doing this, so the aggregator fatals and crashes.
There are 2 ways to fix this:
hacky way: run a script to advance the chain in the docker-compose file after anvil is up
proper way: I believe anvil has fixed this bug and now --load-state restarts the chain at the correct block number. Would have to do a bit of investigation (EDIT: not actually fixed.. see https://github.com/foundry-rs/foundry/issues/7502)
due to some issue with anvil's --load-state restarting the chain at blockNumber 0, when we start anvil, we need to advance it artificially.
However, the current docker-compose file only starts the chain without doing this, so the aggregator fatals and crashes.
There are 2 ways to fix this: