Set up Madara against private Ethereum network

[amlord]

I've got a requirement for the potential to run our system in an on-prem, potentially air-gapped (to an as yet unspecified level) environment.

Our system currently runs on a private Ethereum network, but we're looking to move to an L2 against mainnet for our core offering for the benefits that it'll give.

I spoke with someone in the discord starknet server, and they recommended that I take a look at Madara to set up an appchain.

With this in mind, I'm trying to set up Madara against a private Ethereum network (i.e. not mainnet, sepolia, devnet, etc.) as a PoC to prove out the air-gapped option.

I've managed to use the bootstrapper to bootstrap the private L1 network I've created, but am strugging with setting up the L2 side, and connecting the two.

Is there an example configuration for such a setup somewhere?

My current assumption is that I need to:

1. run private ethereum network
2. bootstrap L1 network with Madara Bootstrapper core / setup-l1
3. run Madara sequencer node
4. bootstrap sequencer node

I'm struggling to get #3 above working, getting the following output:

2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 🥷  Madara Node
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] ✌️  Version 0.7.0-unknown
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 💁 Support URL: https://github.com/madara-alliance/madara/issues
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 🏷  Node Name: hakamo-o
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 👤 Role: Sequencer
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 🌐 Network: madara-sequencer (chain id `SN_PRIVATE`)
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 💻 Operating system: Linux 12 Debian GNU/Linux
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 💻 CPU architecture: x86_64
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 💻 CPU: 
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 💻 CPU cores: 12
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 💻 Memory: 15972MB
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 💻 Kernel: 6.10.14-linuxkit
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 💾 Opening database at: /tmp/madara
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] ⏳ Getting initial L1 gas prices
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 🚀 Subscribed to L1 state verification
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] ⛏️  Starting block production at block #0
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] ⟠ Starting L1 Messages Syncing...
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 📱 Running JSON-RPC server at 127.0.0.1:9944 (allowed origins=["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*"])
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] 📈 Prometheus endpoint started at 127.0.0.1:9615
2024-11-25 13:04:58 [2024-11-25 13:04:58 INFO] ⏳ Gracefully closing the database...
2024-11-25 13:04:59 Error: Failed to watch event filter
2024-11-25 13:04:59 
2024-11-25 13:04:59 Caused by:
2024-11-25 13:04:59     server returned an error response: error code -32000: invalid block range params

My sequencer node is as follows (NAME, CHAIN_ID & ETH_CORE_CONTRACT_ADDRESS replaced with relevant values):

chain_name: "{{.NAME}}"
chain_id: "{{.CHAIN_ID}}"
feeder_gateway_url: "http://localhost:8080/feeder_gateway/"
gateway_url: "http://localhost:8080/gateway/"
native_fee_token_address: "0x04718f5a0fc34cc1af16a1cdee98ffb20c31f5cd61d6ab07201858f4287c938d"
parent_fee_token_address: "0x049d36570d4e46f48e99674bd3fcc84644ddd6b96f7c741b1562b82f9e004dc7"
latest_protocol_version: "0.13.2"
block_time: "30s"
pending_block_update_time: "2s"
execution_batch_size: 16
bouncer_config:
  block_max_capacity:
    builtin_count:
      add_mod: 18446744073709551615
      bitwise: 18446744073709551615
      ecdsa: 18446744073709551615
      ec_op: 18446744073709551615
      keccak: 18446744073709551615
      mul_mod: 18446744073709551615
      pedersen: 18446744073709551615
      poseidon: 18446744073709551615
      range_check: 18446744073709551615
      range_check96: 18446744073709551615
    gas: 5000000
    n_steps: 40000000
    message_segment_length: 18446744073709551615
    n_events: 18446744073709551615
    state_diff_size: 131072
sequencer_address: "0x123"
eth_core_contract_address: "{{.ETH_CORE_CONTRACT_ADDRESS}}"
eth_gps_statement_verifier: "0xf294781D719D2F4169cE54469C28908E6FA752C1"

I've also tried running the sequencer node with the following flags (to just get the node up & running):

"--sync-l1-disabled",
"--no-l1-sync",
"--gas-price=0",

But get the following response in this case (even with the flags set):

2024-11-26 09:46:10 Error: Initializing the l1 sync service
2024-11-26 09:46:10 
2024-11-26 09:46:10 Caused by:
2024-11-26 09:46:10     No Ethereum endpoint provided. You need to provide one using --l1-endpoint <RPC URL> in order to verify the synced state or disable the l1 watcher using --no-l1-sync.

Any help would be greatly appreciated!