following this advice here https://discord.com/channels/844600078504951838/844600078948630559/964185568059740260 in order to get a usable zedtoken for calls to

LookupResources

. if we want to prevent concurrent updates from causing a race condition where an older zedtoken could potentially be written last we either need to partition those concurrent writes around the scope of that universal zedtoken which makes scaling up very hard, or we need to be able to do a check-and-set operation that determines if a newer zedtoken has already been written