Use ipfs-dev-gateway

[pablomendezroyo]

No description provided.

[github-actions]

✅ SYNC TEST REPORT - PASSED

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-geth.dnp.dappnode.eth	0.1.4
Consensus	prysm-hoodi.dnp.dappnode.eth	0.1.5
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	Geth/v1.16.8-stable-abeb78c6/linux-amd64/go1.24.11
After Install	Geth/v1.16.8-stable-abeb78c6/linux-amd64/go1.24.11

Consensus Client Versions

Stage	Version
Before Install	Prysm/v7.0.1 (linux amd64)
After Install	Prysm/v7.0.1 (linux amd64)

⏱️ Timing Measurements

Environment Setup

Operation	Duration	Status
SetStakerConfig	26.222s	✅
PackageInstall	8.519s	✅

Test Execution

Operation	Duration	Status
WaitForBeaconchainSync	1m14.963s	✅
WaitForExecutionSync	2m36.088s	✅

Total Duration: 4m33s

🔴 Container Error Logs

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

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

2026-02-05T10:18:05.674953233Z time="2026-02-05 10:18:05.67" level=error msg="Could not request attestation to sign at slot" error="rpc error: code = Unavailable desc = Could not get attestation data: the node is currently optimistic and cannot serve validators" prefix=client pubkey=0xb1a6afab47a6 slot=2339440

---

📋 View full CI logs