To increase data availability to client applications, an additional committing peer (or multiple peers) may be deployed topologically closer to the client application or to middleware components accessing the data. The committing peer receives newly created blocks and maintains up to date ledger. It does not participate in the endorsement process and thus does not receive transaction proposal requests from clients. The performance of the peer is thus fully dedicated to maintaining ledger and responding to requests for data. An important considerations in terms of network performance and system security configuration is to choose and set up the location such that the committing peer can unobstructed connect to the channel and the network throughput allows to receive newly created blocks with a low delay.