Instead of the fencing token, could the scenario in the blog post be prevented using a good hashing function?<p>When you perform a write, instead of the token, send a hash of the object previously read. The storage can then compare this against a hash of the resource&#x27;s current state. If it doesn&#x27;t match the lock expired and the write is not accepted.<p>This would reduce the state to keep track off to the resources themselves.