[petarjuki7]

Problem, Evidence, and Context

• v1.4.0 crashes at startup on nodes that use a wss:// execution endpoint: Could not automatically determine the process-level CryptoProvider from Rustls crate features.
• Found on the Sepolia canary. The rust-libp2p update in chore(deps): update Lighthouse to v8.3.0 #1349 enables rustls' aws-lc-rs backend (through libp2p-quic) alongside ring, so rustls can no longer pick a default.

Change Overview

• Install aws-lc-rs as the rustls crypto provider at startup.

Validation

• Built v1.4.0 and this branch and ran both against a public Sepolia wss:// endpoint: v1.4.0 panics in the event syncer; this branch connects and starts historical sync.
• make cargo-fmt-check, make lint, make test pass.

Rollback

• Revert this PR.

[dknopik]

lgtm

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.21%. Comparing base (2848ec5) to head (55578e0).

Additional details and impacted files

@@            Coverage Diff            @@
##           unstable    #1355   +/-   ##
=========================================
  Coverage     81.21%   81.21%           
=========================================
  Files           180      180           
  Lines         41831    41834    +3     
=========================================
+ Hits          33973    33976    +3     
  Misses         7858     7858           

Flag	Coverage Δ
rust	81.21% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mergify]

Queued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-22 16:40 UTC · Rule: default · triggered by @petarjuki7 with the merge queue checkbox
• ✅ Checks passed · on draft merge queue: checking #1355 on unstable (2848ec5) #1356
• 🚫 Left the queue — 2026-10-22 17:10 UTC · at 55578e07785eff85cfae39b31cafee5f9cce93b0

This pull request spent 29 minutes 59 seconds in the queue, including 27 minutes 31 seconds running CI.

Reason

Pull request #1355 has been dequeued

GitHub refused to merge the pull request. Repository rule violations found

Secret scanning is not enabled. Please enable secret scanning. This is usually enforced by a branch protection or ruleset rule.

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Required conditions to merge

• check-success=cli-reference-check
• check-success=run-local-testnet
• check-success=test-suite-success
• github-review-approved [🛡 GitHub repository ruleset rule unstable and release-v*]
  • fix: install the rustls aws-lc-rs crypto provider at startup #1355
• any of [🛡 GitHub repository ruleset rule unstable and release-v*]:
  • check-success = license/cla
  • check-neutral = license/cla
  • check-skipped = license/cla

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

• Requeue this pull request