The standard implementation of a Fabric peer maintains the ledger of successful and invalid transactions, a world state (key/value database), and a history/index database. The peers commit transactions (RW sets) per channel they joined, and some peers also, endorse transactions by executing chaincode (smart contracts) and producing RW sets based on the executed RW operations on key/value pairs.
The peer nodes used by OBCS have a few enhancements. An OBCS peer maintains a pool of GO build containers, which allow it to build new chaincode faster and store the binary after successful build in the object store for easy access by other peers belonging to that organization. When the chaincode is instantiated in a channel, the peers ...
