Why create test coin when mutable data exists? They would be no different than a mutable data object that is transferred between users. The moniker safecoin in this case is just that, a label. No point in testing something in conditions that don’t reflect its various functions.
Again, you can create something EXACTLY like safecoin by setting that as the name of any mutable data object. Use it as token for test goods as you would the true coin. Implementing TEST safecoin is multifaceted on the other hand as you would need farming in place along with the resource and value algorithm.
Otherwise its no different from any other mutable data object. So I believe there’s little point in coding those other algorithms when Data-chains must be in place to properly test farming and resource value.
The goal is perfection. Test coin would be of very little productive analytical value unless it can be tweaked dynamically by devs while they are in use. Else devs will just say well data chains will fix this or that when problems inevitably occur in a knowingly lossy network. It’s like putting fuel in a tank full of holes then telling us to drive knowing we wont get beyond the first block. When the driver complains or failure occurs as expected the driver has no choice but to wait for a proper gas tank to be put in place before successfully driving the vehicle.
Alternatively if a proper tank were in place (data chains) and loss or failure to occurs it would be both surprising and more meaningful. Tweaks can then be applied with the expectation that the feature will begin working as intended. As it is now safecoin failures would be obvious with nothing we could do until data chains are in place. Like you stated earlier: