Skip to content

Chore/update client versions - #314

Merged
frbrkoala merged 2 commits into
mainfrom
chore/update-client-versions
Aug 17, 2026
Merged

Chore/update client versions#314
frbrkoala merged 2 commits into
mainfrom
chore/update-client-versions

Conversation

@frbrkoala

Copy link
Copy Markdown
Contributor

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.

Update the Frankendancer client from 0.1006.40100 to the latest Frankendancer mainnet release, 0.1105.40200 (bundled Agave submodule -> v4.2.0, plus minor improvements and security fixes).

This stays on the Frankendancer 0.xxxx line (Firedancer networking + Agave runtime subprocess), which is what this blueprint builds via 'make fdctl solana'. The full-Firedancer 1.x line (e.g. v1.1.3/1.1.4) is a separate client with a different runtime and is not used here.

The Agave v4.2.0 bump requires a larger validator dynamic port range, so the generated fdctl TOML dynamic_port_range was widened 8004-8029 -> 8004-8040 and the Solana security-group range 8001-8029 -> 8001-8040 to match; the gossip port-range test was updated accordingly.

Smoke-tested on Solana mainnet-beta (dev account): builds from source at v0.1105.40200, fdctl accepts the generated TOML, the validator starts and stays up (0 restarts), instance-store set up correctly, gossip connects to ~3800 nodes, and it downloads a snapshot to catch up. Build (tsc) and jest (473 tests) pass.
Besu 26.7.0 -> 26.7.1: security release closing unbounded-memory-growth paths in JSON-RPC filters/subscriptions. The new --rpc-max-active-filters, --rpc-filter-timeout-seconds, and --rpc-ws-max-active-subscriptions options are defaults-only and not set by the blueprint, so no flag changes are needed.

Geth 1.17.4 -> 1.17.5: maintenance release. Pebble v2 is used only for from-scratch datadirs and falls back to Pebble v1 for a pre-existing database, so --db.engine=pebble is unchanged and there is no forced migration. Note the upstream default GOGC change 20 -> 50 raises the memory peak.

Both are docker-image tag bumps; config file names, samples, the default config reference, and the ethereum config test were updated to match.

Smoke-tested on Ethereum mainnet (dev account): both start with the correct images (besu/v26.7.1, Geth/v1.17.5), execution+consensus peer over the engine API, RPC serves, and snap sync begins (Besu worldstate download; Geth beacon-header sync). Teku and Lighthouse checkpoint-sync. Build (tsc) and jest (473 tests) pass.
@github-actions

Copy link
Copy Markdown

Dependency Review

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

Scanned Files

None

@github-actions

Copy link
Copy Markdown

Scan for commit: 5988dc8 | Updated: 2026-08-17 12:15:06 UTC

🔒 Security Scan Results

Scanned files: 19

⚠️ Security findings detected. Please review and address before merging.

@frbrkoala
frbrkoala merged commit b426a67 into main Aug 17, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants