Hyperledger Global Forum 2022

From an Ethereum 1 client to an Execution engine Monolithic client infrastructure will make less and less sense as new roles appear. The Merge is pushing us to think of modularizing Besu. Maintaining a monolith that caters to both enterprises and mainnet users is not sustainable Gap between enterprise ethereum and mainnet ethereum is growing (EIP 1559, gas fee optimization… the Merge itself). Modular architecture: Is more aligned with Open Source Software. Enables more contributors from the ecosystem Enables configurations for different use-cases without extraneous components or complexity Unlock opportunities (ex: MEV support by extracting TX pool)

Trust is a key issue in any network, but is perhaps of paramount importance in blockchain networks. It is so crucial, in fact, that "Trust" and its derivatives are mentioned no less than 14 times in Satoshi's seminal Bitcoin whitepaper. Hyperledger Fabric networks are no exception; in Fabric, trust flows from the Certificate Authorities (CAs) to every participant on the network who utilize that trust to transact according to their role. Operating these CAs properly, then, is central to the trust and security model of Fabric. In this discussion, Alex will reinforce why using centralized PKI generators (such as cryptogen) presents a trust risk for production networks. Corsha's experiences with the Fabric CA will also be discussed, and why it was ultimately decided that the operational overhead of that system made ongoing maintenance challenging. Alex will introduce the cert-manager project and go over how Corsha integrated that with their Kubernetes-native Hyperledger Fabric networks. Finally, Alex will propose a Fabric network architecture that does not rely on a trusted setup and does not require any CA servers, with fully automated certificate management.