lambdaclass / lambda_ethereum_consensus

Elixir implementation of an Ethereum consensus client, which offers high reliance & fault tolerance
Apache License 2.0
101 stars 33 forks source link

chore(deps): bump bls from v5.2.1 to v5.3.0 in /native/bls_nif #1271

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps bls from v5.2.1 to v5.3.0.

Release notes

Sourced from bls's releases.

Risotto Groupon

Summary

This medium-priority release contains performance optimisations, bugfixes and new features. There are several breaking changes detailed below.

The main optimisations are:

  • Faster beacon node start-up due to an optimisation to the database schema (sigp/lighthouse#5897). The schema migration is a backwards-incompatible change which is described in more detail below.
  • More reliable block proposals due to the use of the new v3 block production API (sigp/lighthouse#5292).
  • Improvements to the validator client's broadcast mechanism (sigp/lighthouse#5976, sigp/lighthouse#6223).
  • Support for gossipsub IDONTWANT (sigp/lighthouse#5422). This allows nodes to reduce their bandwidth usage by avoiding the download of duplicate messages.

The main bugfixes are:

New features include:

Breaking Changes

🗑️ Removed CLI flags

The following CLI flags have been removed completely and will cause the BN to fail to start up if provided:

  • --builder-profit-threshold: This flag was already deprecated and has been incompatible since v5.2.0 (sigp/lighthouse#6131).

You should remove any instances of these flags from your beacon node startup command.

👎 Deprecated CLI flags

Beacon node:

  • --disable-lock-timeouts: Lock timeouts are now disabled by default so this flag does nothing. It will be removed in a future release (sigp/lighthouse#6048).
  • --self-limiter: The self limiter is now enabled by default. This flag will be removed in a future release. The purpose of this is to prevent Lighthouse from sending excessive requests to peers in case of bugs or edge case scenarios. The rate limit quotas can be configured via the existing --self-limiter-protocols flag (sigp/lighthouse#6093).

Validator client:

  • --produce-block-v3: The produce block v3 API is now enabled by default and cannot be disabled, so this flag does nothing. It will be removed in a future release (sigp/lighthouse#5292).

You should remove any instances of these flags from your BN/VC commands, although failing to do so will only result in a warning, not a failure to start.

🦀 Minimum Supported Rust Version 1.78.0 🦀

... (truncated)

Commits


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 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)