status-im/infra-nimbus

Run MEV on some Prater/Goerli nodes

tersec opened this issue · 3 comments

This is going to be the main long-lived, ongoing testnet, since first Kiln then Ropsten are scheduled for deprecation this year.

One or two nodes should be fine, but it'd probably be better for them to be individually not terribly larger, no more than in the low hundreds of validators until status-im/nimbus-eth2#3998 is fixed, at which point it won't matter how many validators are present/active.

I've configured two unstable nimbus.prater nodes with the payload builder: cca16d27

'metal-04.he-eu-hel1.nimbus.prater': # 30 each
- { branch: 'stable', start: 20044, end: 20074, build_freq: '*-*-* 11:00:00' }
- { branch: 'testing', start: 20104, end: 20134, build_freq: '*-*-* 15:00:00', nim_commit: 'version-1-6' }
- { branch: 'unstable', start: 20074, end: 20104, build_freq: '*-*-* 13:00:00', payload_builder: true }
- { branch: 'libp2p', start: 20134, end: 20164, build_freq: '*-*-* 17:00:00', nim_flags: '-d:json_rpc_websocket_package=websock' }
'metal-05.he-eu-hel1.nimbus.prater': # 60 each
- { branch: 'stable', start: 20164, end: 20224, build_freq: '*-*-* 11:00:00' }
- { branch: 'testing', start: 20284, end: 20344, build_freq: '*-*-* 15:00:00', nim_commit: 'version-1-6' }
- { branch: 'unstable', start: 20224, end: 20284, build_freq: '*-*-* 13:00:00', payload_builder: true, open_libp2p_ports: false }
- { branch: 'libp2p', start: 20344, end: 20404, build_freq: '*-*-* 17:00:00', nim_commit: 'version-1-6', nim_flags: '-d:json_rpc_websocket_package=websock' }

Will this work for you?

looks good

Cool.