"when there is no utxo ... in the data"
But the data that inkan is trying to handle *does* have "utxo." There are two competing artifacts that each is cryptographically valid by itself:
1. A revocat...
Yes but they don't fork andbjoin. They are individual and remain so. The consensis not just to stop doubre spend it is to store and validate the DAG. The chain issues new utxos every ten minutes. Inkan issues them for humans. it cannot prove they are human and this would be the only kind of validity check. Inkan needs a notary not an accountant. The leak and revocation are inherently a race you cannot eliminate.
1