This was a fix for very large URL arguments caused by large number of
validators applied to the connected validator client.
Unfortunately the values used were in bytes and not kilobytes.
In result we got unnecessarily high memory usage.
Signed-off-by: Jakub Sokołowski <jakub@status.im>
On `kiln`, `ropsten`, `prater`, `sepolia`, the BN code applies network
specific defaults `true` / `only-new`. `mainnet`: `false` / `none`.
This means that the overrides here are no longer needed, also avoiding
issues with planned renames of the parameters in the BN implementation.
Signed-off-by: Etan Kissling <etan@status.im>
We can't have multiple nodes controling a single Geth instance.
This will lead to unpredictable behavior on the execution layer.
https://github.com/status-im/infra-nimbus/issues/97
Signed-off-by: Jakub Sokołowski <jakub@status.im>
"Here’s an update on the Ropsten TTD: we’ve chosen to use a value of
50000000000000000. At the current hash rate, it would hit in several
weeks. That said, the EF will rent hash rate itself and work with
partners to accelerate things. With a modest increase in hash rate, we
should be able to make the Ropsten Merge happen on June 8/9. If your
team is running any validators, please perform a TTD override to
50000000000000000 on them ASAP."
Signed-off-by: Jakub Sokołowski <jakub@status.im>