The Boxcutter Applier uses hashes to detect changes and create new revisions.
Hashing is troublesome because changes to the hash algorithm or the API will change the computed hash, resulting in the creation of a new Revision object.

Change detection can be offloaded to the kube-apiserver, making the whole hash handling obsolete.