kasey b31e2ffe51 avoid copying the finalized state when computing cgc (#16355)
Reviewing some (unrelated) sync code today I noticed that we are using a
stategen accessor for the finalized state which copies the entire state
object to look up validator balances to compute the custody_group_count.
This excess memory allocation is likely causing GC pressure and
increasing memory utilization.

This PR avoids state copying for this purpose by making the following
changes:
- Adds a new method to the `ReadOnlyBalances` state interface:
`EffectiveBalances([]primitives.ValidatorIndex) (uint64, []uint64,
error)`. This method computes returns the sum of the effective balances
of the given list of validator indices, a list with the individual
effective balance of each requested index (where the i-th element in the
return corresponds to the i-th element of the parameter), and an error -
which is necessary due to index bounds checks and quirks of multi-value
slice that can apparently result in the state being unusable for such
lookups if not correctly initialized.
- Adds a new method to the stategen interface
`FinalizedReadOnlyBalances`, which returns the finalized state asserted
to the `ReadOnlyBalances` interface.
- Switches the peerdas code to use the sum given by `EffectiveBalances`.

There was some existing nil checking code in the peerdas package that I
didn't want to modify, so I added a new compound interface in stategen
to allow the returned state to also expose the `IsNil` method.

fixes https://github.com/OffchainLabs/prysm/issues/16354

---------

Co-authored-by: Kasey Kirkham <kasey@users.noreply.github.com>
2026-02-17 08:50:58 +00:00
2021-11-12 15:55:45 +00:00
2025-11-06 16:16:23 +00:00
2026-01-26 16:28:46 +00:00
2026-02-05 10:24:50 +00:00
2026-02-02 14:19:15 +00:00
2026-02-12 12:35:15 +00:00
2025-01-24 04:53:23 +00:00
2025-11-06 16:16:23 +00:00
2024-09-20 17:18:17 +00:00
2026-01-07 20:06:51 +00:00
2025-05-28 01:57:44 +00:00
2022-11-18 19:12:19 +00:00
2026-01-13 16:55:50 +00:00
2018-07-20 10:23:48 -05:00
2024-01-10 15:34:11 +00:00
2025-01-24 04:53:23 +00:00
2023-10-19 12:23:11 +00:00
2026-01-13 16:55:50 +00:00

Prysm: An Ethereum Consensus Implementation Written in Go

Build status Go Report Card Consensus_Spec_Version 1.4.0 Execution_API_Version 1.0.0-beta.2 Discord GitPOAP Badge


📖 Overview

This is the core repository for Prysm, a Golang implementation of the Ethereum Consensus specification, developed by Offchain Labs.

See the Changelog for details of the latest releases and upcoming breaking changes.


🚀 Getting Started

A detailed set of installation and usage instructions as well as breakdowns of each individual component are available in the official documentation portal.

💬 Need help? Join our Discord Community for support.


🏆 Staking on Mainnet

To participate in staking, you can join the official Ethereum launchpad. The launchpad is the only recommended way to become a validator on mainnet.

🔍 Explore validator rewards/penalties:


🤝 Contributing

🔥 Branches

Prysm maintains two permanent branches:

  • master - This points to the latest stable release. It is ideal for most users.
  • develop - This is used for development and contains the latest PRs. Developers should base their PRs on this branch.

🛠 Contribution Guide

Want to get involved? Check out our Contribution Guide to learn more!


📜 License

License: GPL v3

This project is licensed under the GNU General Public License v3.0.


📜 Terms of Use

Description
No description provided
Readme 845 MiB
Languages
Go 95.5%
Starlark 3.9%
Shell 0.4%
Smarty 0.1%