chore(ethereum): bump Nethermind, Erigon, Prysm patches

[frbrkoala]

Drop-in, same-series patch bumps that require no smoke test (no blueprint CLI flag changes):

• Nethermind 1.39.2 -> 1.39.3 (upstream mandatory reliability update)
• Erigon 3.5.3 -> 3.5.4 (RPC gzip native memory-leak fix)
• Prysm 7.1.7 -> 7.1.8 (patch)

Rename the version-pinned config files and update the matching package.json availableConfigurations entries and samples/.env CLIENT_CONFIG references. Build (tsc) and jest (473 tests) pass.

What does this PR do?

🛑 Please open an issue first to discuss any significant work and flesh out details/direction — we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• New blueprint (adding a new protocol — see checklist below)
• Documentation update
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Testing

• I have run npm run build successfully
• I have run npm run test and all tests pass
• I have run npx cdk synth with a sample .env (e.g. from blueprints/dummy/samples/) and it succeeds
• I have run pre-commit hooks: npm run run-pre-commit

New Blueprint Checklist (if adding a protocol)

• Blueprint follows the structure of blueprints/dummy/ (reference implementation)
• Blueprint README follows the standard template (matches Dummy section titles and ordering)
• Setup section points to Getting Started (not inline instructions)
• Deployment section leads with AI-driven deployment (Option 1) and manual as Option 2
• Sample .env files are provided for at least one network (mainnet or testnet)
• Configuration scripts follow the install/run dispatch pattern (see blueprints/dummy/)
• Blueprint page added to website/docs/blueprints/ (.mdx mirror importing README)
• Client Release Channels table added to README under Additional Resources

Documentation

• I have updated relevant documentation (if applicable)
• I have run cd website && npm run build with no broken links (if docs changed)

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[github-actions]

Scan for commit: c65d199 | Updated: 2026-08-17 09:02:50 UTC

🔒 Security Scan Results

Scanned files: 7

✅ No security issues found.