diff --git a/params.yaml b/params.yaml index 5037101..c3da3d3 100644 --- a/params.yaml +++ b/params.yaml @@ -5,9 +5,23 @@ network: - el_type: geth el_image: ethereum/client-go:v1.15.10 cl_type: lighthouse - cl_image: sigp/lighthouse:v7.0.0 + # ethpandaops/ethereum-package's recent update requires using the `perfect_peerdas_enabled` option + # with not less than 16 participants, and disabling `perfect_peerdas_enabled` requires setting the `supernode` flag + # (https://github.com/ethpandaops/ethereum-package/pull/1217). + # + # ssv-mini's main scenario doesn't require so many participants, so we use the `supernode` option. However, + # ethpandaops/ethereum-package uses the new `--supernode` flag instead of the old `--subscribe-all-data-column-subnets` for lighthouse + # (https://github.com/ethpandaops/ethereum-package/blob/4026af29de7267898e91e19bb269f26692a84e42/src/cl/lighthouse/lighthouse_launcher.star#L224). + # `--supernode` is the new flag added in v8.0.0-rc.1, but it's not included in any stable release yet. + # `--subscribe-all-data-column-subnets` is the old flag that will eventually be deprecated but still works on v8.0.0-rc.1 + # (https://github.com/sigp/lighthouse/pull/8083), + # + # Therefore, we have to use the RC version until lighthouse releases a stable version with the support + # of the `--supernode` flag, then the version must be updated. + cl_image: sigp/lighthouse:v8.0.0-rc.1 validator_count: 32 count: 2 + supernode: true additional_services: - dora # Helps to see validators are working @@ -18,7 +32,7 @@ network: deneb_fork_epoch: 0 electra_fork_epoch: 0 fulu_fork_epoch: 100000000 - perfect_peerdas_enabled: true + perfect_peerdas_enabled: false # 74 = 32 validators * 2(number of el/cl nodes) + 10 (running on SSV/Anchor nodes) # aligns with validator_count configuration under participants section @@ -27,6 +41,10 @@ network: # docs: https://github.com/ethpandaops/ethereum-package/blob/main/README.md#configuration # preset: minimal + port_publisher: + cl: + enabled: true + monitor: enabled: false