Create a slonik cluster with a few nodes (say 1,2,3).

The perform an uninstall node on 1 and 2.

Start slonik back up and init cluster(id=1);  and store node(id=2);

Start slonik up again.

uninstall node(id=3);
subscribe set(id=1, provider=1,receiver=3);

slonik will print stuff like:
'waiting for events  (3,5000000077) only at (3,0) to be confirmed on node 1'

When slonik sees an uninstall node it needs to erase the remembered 'last event' from that node.

This was observed with 2.1.0 beta 2