Here, we would need to use the crypto interface defined within FAB-355 to build the commiting peer component that performs all the security checks within a transaction.
As an application/infrastructure developer I want to design a generic membership service interface
Pluggable interface for crypto algorithms to accommodate alternative implementations
Protobufs reflecting the next endorsement/consentor architecture
As an infrastructure developer and application developer i want to have availale a software based crypto provider implementing the interface of FAB-354 in golang.
Review fabric-next protocol from a security perspective