I have drafted probably three pages worth of ideas about this topic. And perhaps none of them summarize what I have been contemplating truly. Nonetheless, my thoughts on identifying bad timestamp actors. These would be described as people who wish to manipulate the order of events and gossip their action happened before another agent’s action. Leaving in question who owns the publication record of this.data?
I personally will have to find a solution to a similar problem, whereas I want an entry to require a set amount of time to be completed, but I don’t want an agent to be able to modify their system clock and bypass the time restraints.
One solution I considered for my above problem was to require a proof of work, like btc or another work based Blockchain. But how do I scale a hashing problem to make actions take a fair amount of time for people with less powerful PCs is a separate topic. This seemed like a decent solution regardless. How do you mitigate DDoS attacks other than by requiring some human action to be required? A metaphor.
It was raised that using a certified time stamping service may work. But perhaps this cost fees and we would like this security to be guaranteed and perhaps free; embedded in the source code.
I cannot be sure, but perhaps if a holochain application was watching for the user to change their timestamp it could identify the bad action and protect itself in some form by informing other agents. Maybe there are some freedoms that aren’t allowed for the security of a network?
I have much more I could rant on this topic. Time will tell whether the problem can be solved. If anyone has any thoughts or rants about how you and I can be certain the time of our publications are preserved and honest/truthy. With all permission; please post below.