Lodestar pfp

Lodestar

@lodestar

0 Following
33 Followers
Lodestar pfp
Lodestar
@lodestar
- Adding an experimental keymanager endpoint (GET /eth/v0/validator/{pubkey}/proposer_config) that allows you to retrieve a proposer configuration which you may use to configure different settings such as feeRecipient and builder settings on different validator keys. See our documentation for more information: https://chainsafe.github.io/lodestar/run/validator-management/proposer-config
0 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
As we wind down 2024, we are happy to announce our year-end release v1.24.0! Thank you to all the external contributors also for your work in this release! For the full changelog, please see: https://github.com/ChainSafe/lodestar/releases/tag/v1.24.0 This recommended release includes some anticipated features like: - Using getBlobsV1 to import blobs locally from the execution layer - Supporting the latest nodeJS LTS version 22 (previously pinned at 22.4) - Adding the debug_getHistoricalSummaries endpoint to allow accessing HistoricalSummaries on the BeaconState post-Capella - A very useful one-line terminal command to install the Lodestar executable into your amd64 and arm64 box. See our documentation for more information: https://chainsafe.github.io/lodestar/run/getting-started/installation
1 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
We've just released v1.22.0! This is mostly a maintenance release and now includes our electra fork work compatible up to consensus specifications v1.5.0-alpha.4 for testing excluding light client specifications. Some minor performance optimizations are included such as deserializing a single state tree at startup rather than two separate trees, shortening startup time. This is a **low priority** update. For the full changelog, please see: https://github.com/ChainSafe/lodestar/releases/tag/v1.22.0
0 reply
0 recast
2 reactions
Lodestar pfp
Lodestar
@lodestar
Do you have a passion to drive the #ethereum blockchain forward and succeed at being the globally neutral settlement layer of digital assets? If you thought the Merge was cool, wouldn't it be cooler to be contributing to the next Ethereum hard fork first hand? If you have that passion to drive and solve problems which may not have concrete answers, we want to hear from you! Join our team as as our very own BlockOps Engineer! https://job-boards.greenhouse.io/chainsafesystems/jobs/5233688004 You'll have an opportunity to make a direct impact on the base chain and contribute to the successful outcomes of Ethereum Layer 1!
0 reply
1 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
Not sure how much more proof one needs to start running Lodestar on their setups. Small solo setups or large node operators alike. @chainsafe node ops runs 100% Lodestar to demonstrate its capabilities. Now part of the Top 25% of operators for @lidofinance in the last 30d!
0 reply
1 recast
2 reactions
Lodestar pfp
Lodestar
@lodestar
This release allows the disabling of flood publishing on gossipsub, which may lead to unnecessary latency in message propagation. You can enable this by updating to v1.18.1 and setting the flag --network.disableFloodPublish to only publish to mesh peers. This should resolve it!
0 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
We've pushed a hotfix release for any users that have been experiencing orphaned or missed block proposals from local block building, even though publishing is well within the 4s deadline. v1.18.1 is *recommended* for those experiencing these problems! https://github.com/ChainSafe/lodestar/releases/tag/v1.18.1
1 reply
1 recast
2 reactions
Lodestar pfp
Lodestar
@lodestar
Basic devcontainer support is now integrated for easier development setups such as Github Codespaces. For more information, see https://chainsafe.github.io/lodestar/contribution/getting-started#devcontainer
0 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
This new default setting means that the builder profit difference over a locally produced block must be greater than ~10% to be selected. The previous default setting was `maxprofit`, which chooses the most profitable. This can be changed in your local configuration.
1 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
`builder.selection` now has a `default` setting that gives slightly preferential treatment to locally produced blocks via `builderBoostFactor=90` . This configurable setting is set to 90 instead of 100 by default.
1 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
Target peers by default has been increased from 50 to 100 peers. Many users have already set this for better validator effectiveness and now we have it set by default to become a better peer on the network.
0 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
This release addresses many compatibility issues discovered from cross-client testing with Lodestar and other consensus clients. This also includes fixes for compatibility with some external DVT platforms and external APIs such as the keymanager.
2 replies
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
Our documentation located at https://chainsafe.github.io/lodestar/ is now using Docusaurus for a better experience. We've attached Plausible metrics to further help improve the contents of our documentation with minimal intrusiveness and open-source analytics.
1 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
Our new v1.18.0 release contains some noticeable facelifts! We **recommend** this update to all users of Lodestar. For the full changelog, please see https://github.com/ChainSafe/lodestar/releases/tag/v1.18.0 Some details outlined in the thread. šŸ§µ
1 reply
1 recast
2 reactions
Lodestar pfp
Lodestar
@lodestar
Did you set your logs verbosity to debug? Please join our ChainSafe Discord and weā€™ll work with you further to debug! https://discord.gg/t62jtXsG
0 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
Users can also set --archiveBlobEpochs now to archive past the default blob rentention window of 4096 or set to Infinity to retain all blobs. šŸ” Minor bug fixes & improvements in logging are also included! Special thanks to all users in our Discord for contributing improvements!
0 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
Minor features have been implemented such as emitting slashing events and completing our validator --builder.selection options with executionalways (alias of --builder.boostFactor=0). This setting will always return a local execution block unless it's not produced or timely.
1 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
You must update to this version before the Ethereum upgrade scheduled for 2024-03-13 13:55:35 UTC and Gnosis Chain upgrade scheduled for 2024-03-11, 18:30:20 UTC.
1 reply
0 recast
0 reaction
Lodestar pfp
Lodestar
@lodestar
We've just released our Deneb-ready version v1.16.0 for the mainnet upgrade! This update is mandatory for all users of Lodestar, including Gnosis users. If you fail to update to this version, you will fall off the network! https://github.com/ChainSafe/lodestar/releases/tag/v1.16.0
2 replies
2 recasts
2 reactions
Lodestar pfp
Lodestar
@lodestar
Hey everyone, we just released v1.15.1 which includes a few hotfixes for users using Besu as their execution client, using --blindedLocal feature and users with .lock file issues. For those users, we highly recommend updating to address these reported issues. https://github.com/ChainSafe/lodestar/releases/tag/v1.15.1
0 reply
3 recasts
2 reactions