From a9868314f8d9d1052744f3243e6170d9419240c5 Mon Sep 17 00:00:00 2001 From: jflo Date: Fri, 10 Jan 2025 14:24:09 -0500 Subject: [PATCH 1/3] Q4 report for besu Signed-off-by: jflo --- .../2024/2024-Q4-Hyperledger-Besu.md | 57 +++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md diff --git a/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md b/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md new file mode 100644 index 0000000..6b7c8ea --- /dev/null +++ b/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md @@ -0,0 +1,57 @@ +--- +layout: default +title: 2024 Q3 Hyperledger Besu +parent: 2024 +grand_parent: Project Updates +--- + +# Project Health + +The Besu project continues to thrive. [Fleet Mode](https://consensys.io/blog/besu-fleet-the-future-of-rpc-scaling) has bolstered interest in Besu from public blockchain networks and private chains, with both Layer 2 and RPC providers considering Besu for their infrastructure. Community activity on Discord is stable, though external contributions are at a seasonal lull. Overall, the project remains healthy. + +# Questions/Issues for the TOC + +Besu contributors have been asking to use a single [CLA](https://en.wikipedia.org/wiki/Contributor_License_Agreement) instead of the DCO requirement for every commit, which is a source of unnecessary friction. The new [LFDT Charter](https://www.lfdecentralizedtrust.org/about/charter) does not mention anything about requiring either, and as such the Besu team intends to relax the DCO requirement in favor of a single CLA. + +# Releases + +This quarters releases: + +- 24.10.0 +- 24.12.0 +- 24.12.1 +- 24.12.2 + +Highlights include: + +- named network support for the Ephemery testnet. This is a public testnet that will be torn down and rebuilt from scratch periodically. This implementation was submitted by a non-maintainer, thanks [@gconnect](https://github.com/gconnect)! + +As usual, each release also included important bug fixes. + +Challenges include: + +- post release of 24.12.0 we noticed that some nodes can freeze up to 2 hours when opening RocksDB database. Besu was impacted by an upstream change in RocksDB (our database) as we moved from RocksDB 8.3.2 in Besu 24.10.0 to RocksDB 9.7.3 in Besu 24.12.0. This change triggers some compaction work depending on the size of the database to apply the new configuration (recommended). Not all upgraded nodes faced the freeze, and this was not seen during testing. The compaction can still happen in the background, but some users reported up to 2 hours freeze. +- 24.12.1 was a hotfix to address publishing besu maven artifacts. + + + +# Overall Activity in the Past Quarter + +Over the past several months, the Besu team and community contributors have addressed a variety of enhancements, bug fixes, and performance optimizations. A number of improvements target transaction processing speed, and accompanying metrics to better visualize and analyze those improvements. + +Equally notable is the growing community involvement in troubleshooting, code reviews, and feature proposals. Contributors have tackled concurrency issues, refactored internal modules, updated dependencies, and implemented new configuration options—efforts that reduce technical debt while enabling better customization for diverse use cases. + +Since the deprecation of the Hyperledger brand, the Besu project has begun the process of migrating their repositories to the `besu-eth` organization on GitHub. + +The team has adopted automation to better manage issues- GitHub actions are used to mark any issues or prs that have had no activity for the last 2 weeks as stale, and if they are not tended to in in the subsequent 2 weeks the will be closed. This will enforce regular review of issues. + +# Current Plans + +The Prague and Osaka upgrades will be the primary focus in Q1 2025. We continue to invest in our plugin architecture and modularizing the codebase to accommodate that. Integration with the Portal Network will be invested in to reduce the storage footprint required by mainnet nodes. + +# Contributor Diversity + +Due to an increase in trivial or automatically generated PRs, we have had to refine our [policies around insignificant contributions](https://github.com/hyperledger/besu/blob/main/CONTRIBUTING.md#guidelines-for-non-code-and-other-trivial-contributions) likely intended to farm future rewards. + +# Additional Information + From 8b71ced4ea3234f9a3635b7530566560670ff060 Mon Sep 17 00:00:00 2001 From: jflo Date: Fri, 10 Jan 2025 14:25:58 -0500 Subject: [PATCH 2/3] header correction Signed-off-by: jflo --- tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md b/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md index 6b7c8ea..ef88598 100644 --- a/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md +++ b/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md @@ -1,6 +1,6 @@ --- layout: default -title: 2024 Q3 Hyperledger Besu +title: 2024 Q4 Hyperledger Besu parent: 2024 grand_parent: Project Updates --- From d9d9e86bda784fcce712fd32fbcbcdd0d1adf433 Mon Sep 17 00:00:00 2001 From: Justin Florentine Date: Mon, 13 Jan 2025 10:14:29 -0500 Subject: [PATCH 3/3] Update tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md ty for proofing Co-authored-by: Tracy Kuhrt Signed-off-by: Justin Florentine --- tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md b/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md index ef88598..e9fb800 100644 --- a/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md +++ b/tac/project-updates/2024/2024-Q4-Hyperledger-Besu.md @@ -43,7 +43,7 @@ Equally notable is the growing community involvement in troubleshooting, code re Since the deprecation of the Hyperledger brand, the Besu project has begun the process of migrating their repositories to the `besu-eth` organization on GitHub. -The team has adopted automation to better manage issues- GitHub actions are used to mark any issues or prs that have had no activity for the last 2 weeks as stale, and if they are not tended to in in the subsequent 2 weeks the will be closed. This will enforce regular review of issues. +The team has adopted automation to better manage issues- GitHub actions are used to mark any issues or prs that have had no activity for the last 2 weeks as stale, and if they are not tended to in the subsequent 2 weeks they will be closed. This will enforce regular review of issues. # Current Plans