A client C is responsible for using multistamps to ensure that it receives invalidations before their absence could lead to the current transaction viewing an inconsistency.
C maintains two tables that store information about servers it is connected to.
The client also maintains a set CURR that identifies all servers used by the currently running transaction. In other words, for all servers used by the current transaction, the invalidation information is as recent as is required. When the fetch reply arrives it processes the invalidations as described above. The main impact on system performance is in step 3 when an invalidation request is sent.