chore(deps): bump bls from v7.0.1 to v8.0.0 in /native/bls_nif

[dependabot]

Bumps bls from v7.0.1 to v8.0.0.

Release notes

Sourced from bls's releases.

Brosephamons

Summary

This release includes the mainnet fork epoch for the upcoming Fulu-Osaka (Fusaka) fork and subsequent blob-parameter-only (BPO) forks. 🎉

Upgrading to v8.0.0 is mandatory for all mainnet users prior to the Fulu fork at epoch 411,392 (2025-12-03, 21:49 UTC).

This version also includes configurations for the following BPO forks (no additional action required):

• BPO 1: Epoch 412,672 (2025-12-09, 14:21 UTC) - increases blob count to target/max 10/15
• BPO 2: Epoch 419,072 (2026-01-07, 01:01 UTC) - increases blob count to target/max 14/21

Operators should expect bandwidth increases as the blob count rises with each fork.

Learn more:

• What's included in the Fusaka fork
• How Fusaka affects bandwidth requirements
• Understanding BPO forks

There are also other important changes in v8.0.0:

• This is the last Lighthouse release supporting Windows.
• Users requiring full blobs (e.g. for L2 sync) must add either the --supernode or --semi-supernode beacon node flag.
• It is recommended to remove the block-cache-size flag if it is being used.
• Default gas limit increases from 45M to 60M.

⚠️ Breaking Changes ⚠️

🍎 🪟 Platform Support Changes

This will be the last Lighthouse release supporting Windows. We have made this decision carefully after considering the low level of Windows adoption, and the difficulty of maintaining a high-quality build of Lighthouse for Windows. We recommend Windows users to switch to using Docker, WSL, Linux or another solution of their choice.

Pre-built macOS x86_64 binaries are no longer provided (#7862). Apple, GitHub runners, and Rust are dropping x86_64 macOS support, so we have made the decision to phase out support. macOS x86 users should use the Linux Docker image, the homebrew package, or build Lighthouse from source.

💾 Database Schema Upgrade

Lighthouse v8.0.0 includes a database schema upgrade to schema v28. This upgrade greatly reduces the size of fork choice on disk, leading to reduced I/O.

No action is required upon upgrading, Lighthouse will automatically upgrade your database to the new version.

If you would like to downgrade to a prior release (e.g. v7.1.0), then you must follow the instructions in the Lighthouse book for downgrading the database schema before switching your binary to the old version.

🐡 Changes to Blob Retrieval Beacon APIs

Once PeerDAS is activated from the Fulu fork:

• Users will no longer be able to retrieve blobs via the Beacon APIs by default. This is because each full node will only sample and store a small portion of blob data.
• To opt-in to full blob access, users must meet one of the following conditions:
  • Run the beacon node with either the --supernode or --semi-supernode flag.
  • Custody at least 50% of all columns by having at least 2,048 ETH in validator stake attached to the beacon node.
• Deprecated API /eth/v1/beacon/blob_sidecars/{block_id}: This endpoint will return empty blob proofs in post-Fulu blob sidecars. This is because consensus clients will use cell proofs instead of blob proofs for blob verification. This endpoint will be removed in a future release.
• New API /eth/v1/beacon/blobs/{block_id} (#8103): This is the successor to the deprecated blob sidecars endpoint. It supports querying blobs by block ID and versioned hashes. Users are encouraged to switch to using this API ahead of the deprecation of the blob sidecars endpoint.

... (truncated)

Commits

• e3ee7fe Release v8.0.0 (#8352)
• 5d0f8a0 Ensure custody backfill sync couples all responses before importing (#8339)
• 4908687 Proposer duties backwards compat (#8335)
• 25832e5 Add mainnet configs (#8344)
• b57d046 Fix CGC backfill race condition (#8267)
• 55588f7 Rust 1.91 lints (#8340)
• 5978b4a Bump gas limit to 60M (#8331)
• 1cee814 Fix: custody backfill sync display incorrect time estimation (#8291)
• 6f0d0de Fix failing CI for compile-with-beta-compiler (#8317)
• 5db1dff Downgrade gossip logs set to INFO level (#8288)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #1483.