Data retrieved from a peer may be stored in an application cache so that future requests for that data can be served faster. To maintain the data in the cache up to date, the application must monitor changes in the underlying ledger and update the cached data with new state modifications. As discussed earlier, the peer emits event notifications about newly committed transactions into the ledger. The notification can be intercepted by the client and by inspecting the content of the transaction, the client can determine whether the cache should be updated with new values.