If login tokens are stored on a public ledger replay attacks write themselves. Public or private, keeping every login token ever is a horrible audit mechanism and doesn’t scale well. At scale, speed to generate becomes a concern. Not at scale, something lighter is faster.
A normal database scales better than a license blockchain and doesn’t require extra computation to write. Audit logs and hashes prevent extra edits. License files signed by a central authority don’t require a database and the central authority is functionally equivalent albeit less expensive than a blockchain.
I am still interested in a good use for the tech. I have yet to see one that is genuine.
I don’t think you’re using straw man correctly.
You’re naively referring to how consensus should work while completely ignoring both the well-defined attacks I referenced and the reality of large actors in a consensus network. You don’t know what you’re talking about or you don’t understand how the theory works or you’re possibly just being obtuse. No matter what, this is pointless. Good luck.