You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


Introduction

The Hyperledger Besu Project aims to achieve an Ethereum client designed to be enterprise-friendly for both public and private permissioned network use cases. The Java-based Ethereum client (Besu) is becoming one of the most used Ethereum clients by enterprises from multiple industries that are actively exploring the Web3 and digital assets space. The increasing adoption of EVM-compatible technology within financial services and the accelerating trend of tokenization of assets are some of the key drivers for enabling a collaboration space for enterprise users of Besu and code contributors of Besu to come together to drive the evolution of Besu as an open-source project.

The interests of these two groups are a perfect match for collaborating on the adoption and success of the open-source tool.

  • Enterprise users of Besu in need of tech capabilities that meet enterprise requirements.
  • Code contributors of Besu aiming to maximize the value and adoption of Besu.

Naming Convention

The name of this workgroup shall be Hyperledger Besu Financial Services Workgroup (Besu FS WG). Additional appropriate name references shall be:

  • Hyperledger Besu Financial Services Workgroup (external, formal)
  • Besu Financial Services WG (external, informal)
  • Besu FS WG (internal, informal)

Scope and Deliverables

The mission is driving working sessions for enterprise users and code contributors to come together for:

  • Identifying challenges that enterprise users face when operationalizing and implementing Besu in their business solutions in alignment with standards, requirements, and common practices from the industry.
  • Defining new features and enhancements that strengthen the alignment between Besu and the requirements from enterprises adopting Blockchain and DLT (Distributed Ledger Technology) technologies.

The main deliverables expected to come out of this WG include, but are not limited to:

  • A prioritized and detailed list of enhancements of existing features of Besu
  • A prioritized and detailed list of new features of Besu
  • A prioritized and detailed list of technical limitations of Besu
  • A list of recommended practices of Besu for enterprise use cases

These deliverables will shape an inventory of use-case agnostic enterprise features and non-functional requirements that code contributors of Besu can use to define a product roadmap for Besu.

The workgroup may form subgroups to support, emphasize, or promote any of those items listed above.

Work Products

The initial work products include a set of working documents describing existing feature enhancements, new enterprise features, and recommended practices of Besu for enterprise use. The HBFS-SIG may also host in-person meetings and presentations to accelerate the Special Interest Group's mission.



  • No labels