Source Known Identifiers: A Three-Tier Identity System for Distributed Applications
This paper introduces Source Known Identifiers (SKIDs), a novel three-tier identity system that unifies compact database storage, chronological sortability, origin metadata, zero-lookup verifiability, and confidentiality to address the limitations of existing identifier schemes in distributed applications.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are running a massive, global library where millions of books are being written, read, and moved between different branches every second. In this library, every single book needs a unique ID tag.
The problem is that existing ID systems are like trying to use the same tag for three very different jobs at once, and they fail at all of them:
- The Database Tag: Needs to be tiny and sorted by time so the librarian can find books instantly.
- The Trusted Internal Tag: Needs to prove who wrote the book and what kind of book it is, without asking the librarian to check a list.
- The Public Tag: Needs to be a secret code so strangers can't guess how many books exist or who wrote them.
Current solutions force you to choose: either you have a tiny tag that leaks secrets, or a secret tag that is huge and slow to sort.
Enter "Source Known Identifiers" (SKIDs).
Think of SKIDs not as three different tags, but as one magical identity card that changes its appearance depending on who is looking at it. It's like a chameleon that is a tiny, sorted number for the librarian, a verified badge for the staff, and a scrambled secret code for the public.
Here is how the three "tiers" of this system work, using simple analogies:
Tier 1: The "Speedy Number" (The SKID)
Who sees it: The Database (The Librarian).
What it is: A tiny, 8-byte number.
The Analogy: Imagine a conveyor belt in a factory. Every item gets a number stamped on it as it comes down the line.
- Why it's great: It's incredibly small (saving space) and it's stamped in perfect time order. The librarian doesn't need to shuffle through a pile; they just look at the end of the belt to find the newest books.
- The Secret Sauce: It's not just a random number. It's a "smart" number that secretly contains the time it was made, which factory branch made it, and a counter. But to the database, it's just a fast, sortable number.
Tier 2: The "Verified Badge" (The SKEID)
Who sees it: Trusted Internal Systems (The Staff).
What it is: A 128-bit ID that looks like a standard UUID (like a standard library barcode) but has hidden layers.
The Analogy: Now, the librarian hands the book to a staff member. The staff member needs to know: "Is this book real? Did it come from the right factory? Is it a cookbook or a novel?"
- The Magic: The staff member doesn't need to call the librarian to check. The ID itself has a digital seal (a cryptographic signature) baked right into it.
- How it works: The staff member looks at the ID, checks the seal, and instantly knows, "Yes, this is a real cookbook from Factory Branch 5, made at 2:00 PM." If the seal is broken or the factory code is wrong, they know it's a fake immediately. No phone calls, no database lookups.
Tier 3: The "Secret Code" (The Secure SKEID)
Who sees it: The Public (The Strangers).
What it is: The same 128-bit ID, but completely scrambled using a super-strong lock (AES-256 encryption).
The Analogy: A stranger walks up to the counter and asks for the book's ID. The staff member takes the "Verified Badge" and shoves it into a magic shredder that turns it into a random-looking string of gibberish.
- The Result: The stranger sees a code that looks like
x9f-2a-8b.... They can type it into their computer to find the book, but they cannot guess:- When it was made.
- Which factory made it.
- What kind of book it is.
- How many books exist.
- The Safety: Even if a hacker tries to guess a code, the system has a "trap." If they guess a code that looks like a real badge, the system checks the math. If the math doesn't match the secret key, the system rejects it. It's like a lock that only opens if you have the specific key and the right shape.
Why is this a big deal?
- It's Fast: Because the "Speedy Number" is just a math calculation (no random number generation), it's 10 times faster than current standard methods.
- It Saves Space: The database only stores the tiny 8-byte number. The big, complex 16-byte "Verified Badge" is only created when needed, saving massive amounts of storage space and making the database run smoother.
- It's Secure: It uses a "Defense-in-Depth" strategy. To hack it, a criminal would have to break the encryption, forge the digital seal, guess the factory code, and guess the book type all at once. The odds are so low it's practically impossible.
- It's Future-Proof: The system is designed to last for over 17,000 years. It has a "time machine" feature (called Epochs) that allows it to reset and start a new cycle without running out of numbers, ensuring it won't expire in our lifetime.
The Bottom Line
The SKID system is like a universal translator for digital identity. It speaks "Database" (fast and small), "Staff" (verified and detailed), and "Public" (secret and safe) all at the same time. It solves the age-old problem of trying to have a fast, secure, and private ID system without having to choose between them.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.