Enable quic

[nflaig]

In the next release (v1.41.0) we will have quic, this PR enables it by default on dappnode.

@Marketen is there anything else that needs to be considered? and regarding the default port, I just used p2p port + 1 which is also the default behavior

[github-actions]

❌ SYNC TEST REPORT - FAILED

This CI runs on a real DAppNode using the same RPC calls a user would make to configure a staker setup: execution client, consensus client, web3signer, MEV-boost, and relays. The self-hosted runner is pre-loaded with synced (or near-synced) execution client volumes, enabling fast sync and attestation tests with any client combination. Consensus clients use checkpoint sync, so no pre-synced volume is required.

Sync Test: Verifies that both execution and consensus clients reach a synced state. This test ensures the staker configuration is valid and clients can synchronize with the network.

📦 Clients Used

Component	DNP Name	DNP Version
Execution	hoodi-reth.dnp.dappnode.eth	0.1.4
Consensus	lodestar-hoodi.dnp.dappnode.eth	0.1.8
Web3Signer	web3signer-hoodi.dnp.dappnode.eth	0.1.3
MEV Boost	mev-boost-hoodi.dnp.dappnode.eth	0.1.1
Network	hoodi

🔖 Version Tracking

Execution Client Versions

Stage	Version
Before Install	reth/v1.9.2-74351d9/x86_64-unknown-linux-gnu
After Install	reth/v1.9.2-74351d9/x86_64-unknown-linux-gnu

Consensus Client Versions

Stage	Version
Before Install	Lodestar/v1.40.0/66aff77
After Install	not available

⏱️ Timing Measurements

Environment Setup

Operation	Duration	Status
SetStakerConfig	38.123s	✅
PackageInstall	19.032s	✅

Test Execution

Operation	Duration	Status
WaitForBeaconchainSync	6m13.788s	❌

Total Duration: 9m4s

🔴 Container Error Logs

⚠️ Showing up to 3 error lines per container. See CI logs for complete details.

DAppNodePackage-reth.hoodi-reth.dnp.dappnode.eth:

2026-03-15T21:36:15.811809437Z �[2m2026-03-15T21:36:15.811738Z�[0m �[33m WARN�[0m Beacon client online, but no consensus updates received for a while. This may be because of a reth error, or an error in the beacon client! Please investigate reth and beacon client logs! �[3mperiod�[0m�[2m=�[0m249.385640504s

DAppNodePackage-brain.web3signer-hoodi.dnp.dappnode.eth:

2026-03-15T21:34:28.946343825Z �[31m�[0m[ERROR]�[31m�[0m [CRON - reloadValidators]: Error reloading data
2026-03-15T21:34:28.946377658Z ValidatorApiError: Error getting remote keys from validator. Request to /eth/v1/remotekeys failed with status code ECONNREFUSED: connect ECONNREFUSED 172.33.0.26:3500.
2026-03-15T21:34:28.946384761Z ValidatorApiError: Error getting remote keys from validator. Request to /eth/v1/remotekeys failed with status code ECONNREFUSED: connect ECONNREFUSED 172.33.0.26:3500.

DAppNodePackage-validator.lodestar-hoodi.dnp.dappnode.eth:

2026-03-15T21:33:48.118085065Z Mar-15 21:33:48.117[]                 �[32minfo�[39m: Waiting for genesis message=Request to http://beacon-chain.lodestar-hoodi.dappnode:3500/eth/v1/beacon/genesis failed, reason: getaddrinfo ENOTFOUND beacon-chain.lodestar-hoodi.dappnode
2026-03-15T21:34:00.143195318Z Mar-15 21:34:00.143[]                 �[32minfo�[39m: Waiting for genesis message=Request to http://beacon-chain.lodestar-hoodi.dappnode:3500/eth/v1/beacon/genesis failed, reason: getaddrinfo ENOTFOUND beacon-chain.lodestar-hoodi.dappnode
2026-03-15T21:34:12.168470188Z Mar-15 21:34:12.168[]                 �[32minfo�[39m: Waiting for genesis message=Request to http://beacon-chain.lodestar-hoodi.dappnode:3500/eth/v1/beacon/genesis failed, reason: getaddrinfo ENOTFOUND beacon-chain.lodestar-hoodi.dappnode

❌ Error Details

check beaconchain sync attempt 60 failed: Get "http://beacon-chain.hoodi.dncore.dappnode:3500/eth/v1/node/syncing": dial tcp: lookup beacon-chain.hoodi.dncore.dappnode on 127.0.0.11:53: no such host

---

📋 View full CI logs

[nflaig]

CI is expected to fail until we upgrade to v1.41.0