The SpiceDB project aims to provide a distributed authorization system that guarantees certain properties, including protection against the "New Enemy" problem. The New Enemy problem occurs when an ACL check returns different results from what was reasonably expected based on previous actions due to neglecting update order or misapplying old ACLs to new content. To prevent this issue, SpiceDB relies on TrueTime and Spanner's snapshot reads. However, without a TrueTime-like API available, SpiceDB uses alternative backends such as Postgres, CockroachDB, or In-Memory drivers. These alternatives have limitations in preventing the New Enemy problem, particularly with CockroachDB, which can assign transactions inconsistent timestamps for non-overlapping keys. To mitigate this issue, SpiceDB adds mitigations to the CockroachDB driver, including sleeping for a certain time after a write and ensuring that any writes that could result in the New Enemy problem produce overlapping transactions. The project has developed a test framework to demonstrate the efficacy of these mitigations and plans to continue improving and adapting to changes in CockroachDB.