🌟 TypeScript Implementation of Ethereum Consensus
We just released v1.15.1 which includes a few hotfixes for users using Besu as their execution client, using --blindedLocal and users with .lock file issues. For those users, we highly recommend updating to v1.15.1 to address these reported issues.
null.--blindedLocal feature on their setups. This fix parses the CLI flag as boolean.This update is recommended to all users of Lodestar and mandatory for those running Sepolia and Holesky testnets. This release is also ready for the Gnosis Chain Chiado fork.
This release includes some additional fixes for the Deneb hard fork, an upgrade to js-libp2p and minor fixes for UX and performance improvements.
max-old-space-size option from 4096 (4GB) to 8192 (8GB) in our scripts by default so users can benefit from testnets like Holesky with larger states and to better handle periods of network turbulance like non-finality before heap memory is exceeded. This does not increase memory usage. It was done proactively to improve UX as we continue to optimize our memory footprint.produceBlockV3 should be in wei (#6286) (@ensi321)produceBlockV3 should be in wei (#6286) (@ensi321)Hey everyone! We've released v1.14.0 of Lodestar which is recommended for all users on all networks. This is the same version as v1.14.0-rc.2 which was the mandatory release for Goerli users for Deneb hard fork readiness.
This release includes the scheduled Goerli test network fork for Deneb at epoch 231680.
If using Lodestar for the Ephemery testnet, this version is compatible with the Deneb fork scheduled for iteration 111 on January 18, 2024.
--blindedLocal is a new feature which allows local block publishing to be signed by the validator similarly to builder relays via blinded headers instead of having the full payload. For operators with their Lodestar beacon node and validator clients in separate hosts/networks, this feature will reduce block production latencies. This is only supported if it's a Lodestar beacon node using produceBlockV3.
Breaking change for Deneb fork: The Deneb fork epoch will trigger the migration to use produceBlockV3 on Lodestar. If you do not want this, you MUST disable it with --produceBlockV3 false. Alternatively, if you want to turn it on for testing pre-Deneb, you can enable it with --produceBlockV3 true. The automatic switch to produceBlockV3 will only affect the Goerli network (the only scheduled network to fork on this release).
Other block production optimizations to reduce block production latencies and likelihood of orphaning blocks due to reorgs.
Lodestar now supports shouldOverrideBuilder functionality where execution clients can identify censorship and force local block production irrespective of the builderBoostFactor. See https://github.com/ethereum/execution-apis/pull/425 for the specification and this note on the heuristics of how the execution client determines builder censorship: https://hackmd.io/@potuz/BkpzmOgK6.
produceBlockV3 API now supports builder_boost_factor. Our documentation here (https://chainsafe.github.io/lodestar/validator-management/vc-configuration/#configure-your-builder-selection-andor-builder-boost-factor) includes details on how to use this with our already implemented --builder.selection feature.
produceBlockV3 (#6207) (@ensi321)produceBlockV3 (#6207) (@ensi321)produceBlockV3 (#6207) (@ensi321)produceBlockV3 (#6207) (@ensi321)Happy holidays everyone! We've released our hopefully last release for 2023 with v1.13.0! We recommend users upgrade for some performance and user improvements. Some of which are highlighted below:
Lodestar now logs info about your connected service URLs. This is especially useful for users using Lodestar with multiple/fallback services to know on startup what they’re connected to.
PR #6132 now allows for voluntary exits by remote signers. Previously, Lodestar only allowed voluntary exits from locally imported keystores.
We previously did not include Eth-Consensus-Version header as part of our getStateV2 and getBlockV2 responses as per the Beacon-APIs spec. We are continuing to address this and are refactoring our SSZ API responses also for inclusion on the BlockV3 endpoint.
We’ve done a big refactor in our docs and will continue to build it with more context and education for Ethereum users, starting with PR #6134.
We cleared up usage of the --builder.url. We do not support multiple connected builders and will only use the first URL attached. If multiple URLs are supplied, it will now throw an error.
Other fixes include performance improvements such as implementing a shuffling cache (PR #6030) to verify attestations rather than using the state cache and regen, and improvements on how we process slashings (PR #6121).
consensus_block_value to produceBlockV3 (#6136) (@ensi321)hexToBuffer bug (#6098) (@orenyomtov)consensus_block_value to produceBlockV3 (#6136) (@naviechan)hexToBuffer bug (#6098) (@orenyomtov)