**Motivation**
Replace deprecated Holesky network support with Hoodi testnet
configuration. Hoodi is a new Ethereum testnet that will serve as a
replacement testnet, and this change updates Lodestar to support the new
network configuration.
**Description**
This PR removes Holesky network configuration and replaces all
references with Hoodi testnet support. Changes include:
- Removed `packages/cli/src/networks/holesky.ts` network file
- Removed `packages/config/src/chainConfig/networks/holesky.ts` chain
config
- Updated all network references from "holesky" to "hoodi" across CLI,
config, and test files
- Added Hoodi network configuration with proper chain parameters,
genesis data, and bootnodes
- Updated default environment configuration
- Updated unit tests to reflect the network change
<!-- Link to issues: https://github.com/ChainSafe/lodestar/issues/8595
-->
Closes #https://github.com/ChainSafe/lodestar/pull/8615
**AI Assistance Disclosure**
- [ ] External Contributors: I have read the [contributor
guidelines](https://github.com/ChainSafe/lodestar/blob/unstable/CONTRIBUTING.md#ai-assistance-notice)
and disclosed my usage of AI below.
<!-- Insert any AI assistance disclosure here -->
-PR content was developed using Cursor for code updates and
explanations; I reviewed and verified all changes manually.
**Motivation**
Launching Hoodi testnet which replaces Holesky.
**Description**
Replace Holesky testnet with Hoodi default testnet in the docs and in
code where `holesky` flag is used as a default testnet.
#7586
**Steps to test or reproduce**
- Check documentation
- Run a Hoodi testnet using the new flag
---------
Co-authored-by: Nico Flaig <nflaig@protonmail.com>
* Disable anonymous login in Grafana
* Don't expose API port by default
* Remove cli link in package.json
* Move NODE_OPTIONS to ENV to split beacon_node and validator limits
* Revert "Remove cli link in package.json"
This reverts commit 74c9b2ec9a.
yargs strict options do not allow to share ENVs between the beacon node and the validator. The GRAFFITI ENV prevent the beacon node from running at all. This is unfortunate and a better solution should be found eventually.
