this post was submitted on 19 Jun 2026
94 points (91.2% liked)

Asklemmy

54666 readers
986 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] thesmokingman@programming.dev 1 points 2 days ago

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.