Getting Started with UIID by LINKSPREED: A Complete Beginner's Guide to Your Web4 Identity

1. What Is UIID, in Plain English?

UIID is a decentralized digital identity system built by LINKSPREED (Linkspreed UG, based in Friedberg, Germany). The acronym is used in two closely related ways in LINKSPREED’s own material — Universal Integrated Identity Decoupled and Unique Immutable Identity. Both names point at the same core idea:

One identity that belongs to you, stored on your device, that you can use everywhere — without ever handing your personal data to the services you log into.

Today’s web has an identity crisis: dozens of accounts, password fatigue, and your personal information scattered across corporate databases you don’t control. UIID flips this. Instead of requesting an account from a platform, you own the identity and grant the platform permission to talk to it.

LINKSPREED positions UIID v1 not as an app but as foundational infrastructure — what they call the “starting gun for Web4”: a web where users have sovereignty, interoperability is the default, and trust comes from cryptography rather than corporate authorities.

Why beginners should care

Old way (Web2 accounts)	UIID way (Web4 identity)
One account per platform	One identity, many disposable aliases
Passwords stored in a company database	No passwords exist at all
Company holds your personal data	Data stays in a vault on your device
Deleting an account = dark patterns	Delete an alias = instant, irrevocable cut-off
Platform is the admin	You are the admin

2. The Core Concepts You Need to Understand First

Read this section before you click “create”. Understanding these five concepts makes the whole setup flow obvious.

2.1 The Core ID — your root identity

The Core ID is the immutable, sovereign “root of you”. LINKSPREED describes it as “the bedrock of your digital self” and “the unmoving backbone of your digital existence”.

Key properties:

It is permanent — it is not meant to be rotated or replaced.
It is never shared directly with third-party services.
It is used only for first-party actions you perform yourself, such as managing authorized applications inside your UIID Dashboard.

Think of it as the master key you never let out of your sight.

2.2 Aliases — the masks you wear

An Alias is a flexible, context-specific, disposable identity. It’s “the mask you wear” when you log into a social network, buy something, or join a gaming platform.

Each service only ever sees a specific alias you created for it.
Different services cannot cross-correlate your behavior, because they never see the same identifier.
Aliases are also what enables Single Alias Login — one public username you can carry across LINKSPREED’s networks.
Delete an alias → the connection is severed instantly and irrevocably. You don’t ask the company for permission and you don’t navigate their deletion maze.

This two-layer split (Core ID + Aliases) is called the dual-layer split identity architecture and it’s the single most important idea in UIID.

2.3 Zero-Knowledge Proofs (ZKP) and Zero-Knowledge Signatures (ZKS)

Zero-Knowledge cryptography lets you prove something is true without revealing the underlying data.

Practical examples:

Prove you are over 18 without revealing your birth date or name.
Prove you are in a certain country/region without revealing your address.
Prove you are a verified human without revealing who you are.
Prove you own a UIID and an alias without exposing any private data.

Even where a one-time KYC (identity verification) is performed on the Core ID, that KYC is immediately decoupled from your daily alias activity — so your anonymous activity cannot be traced back to your legal identity.

2.4 Truly passwordless (ZKP + WebAuthn)

Most “passwordless” systems just hide a password behind a fingerprint. UIID v1 architects the system so that passwords simply don’t exist.

Authentication combines Zero-Knowledge Proofs with the WebAuthn standard (the same standard behind passkeys and hardware security keys).
You authenticate with a registered device or a physical security key.
No password and no secret key is ever sent over the network. The service receives mathematical proof that you possess the secret — nothing more.
This structurally eliminates password-database breaches and most phishing attacks.

Internally this is a challenge/response mechanism rather than a shared secret.

2.5 The Identity Vault and the zero-data honeypot

Your data lives in an Identity Vault on your own device, not on a company server.

For companies integrating UIID this is called a zero-data-honeypot design: because they never hold your sensitive personal data, there is nothing worth stealing and dramatically less compliance liability. LINKSPREED calls this shift “mathematical compliance” — you comply because the data was never collected, not because of a policy promise.

3. Getting Started: Creating Your UIID Step by Step

Everything starts at https://uiid.me. LINKSPREED also publishes a video walkthrough: How to Set Up a UIID Easily! (Step-by-Step Guide).

A note on exact wording: LINKSPREED iterates quickly on the onboarding UI, and the public documentation doesn’t spell out every button label. The sequence below reflects the documented architecture and the standard flow; if a label on screen differs slightly, follow the on-screen wizard — the concepts below still map 1:1.

Step 1 — Open uiid.me and start ID generation

Go to https://uiid.me and choose to create a new identity.

What happens technically: your Core ID is generated together with a cryptographic key pair. The secret material is generated and stored on your device, not on a server.

Do this on a device you own and trust — ideally your primary phone or laptop, not a public or shared computer.

Step 2 — Secure it with a passphrase / PIN

Next you protect the identity locally. This is your passphrase (sometimes surfaced as a PIN for quick actions).

Important mental model: this passphrase is not a login password sent to a server. It is the local key that unlocks your vault and authorizes cryptographic operations on your device. There is no server-side password database to breach, which is exactly the point.

Passphrase best practices for beginners:

Use a long passphrase, not a short complex password — e.g. four or five unrelated words plus a number/symbol.
Never reuse a passphrase you use anywhere else.
Write it down on paper and store it physically (a safe, a document folder). Paper is not hackable.
If you use a password manager, store it there and keep the paper backup.
Understand the trade-off of self-sovereignty: there is no support hotline that can “reset” a key it never had. That’s the price — and the benefit — of nobody else holding your identity.

The same PIN concept reappears later at the permission level: sensitive alias data (alias:read:private) can be protected with a PIN prompt during the consent flow, giving you granular, per-alias control.

Step 3 — Link an email address (optional)

Email linking is optional by design, and that is philosophically deliberate: a UIID does not need an email address to exist. Requiring one would reintroduce exactly the kind of central, correlatable identifier UIID is built to eliminate.

Reasons to link an email anyway:

Recovery and account-notification convenience.
Security alerts (e.g. a new device registering against your identity).
Bridging into legacy Web2 systems that still expect an email contact channel — UIID explicitly bridges legacy Web2 services.

Reasons to skip it:

Maximum anonymity. An email is a strong cross-service correlator.
You prefer to rely purely on device-based recovery and your .uiid backup.

Middle path (recommended for most beginners): link a dedicated email address used only for UIID. You get the recovery and alerting benefits without linking your identity to the mailbox you use everywhere else.

Now you register how you will authenticate. Options in the UIID model include:

Platform authenticator / biometrics — fingerprint or face recognition on your phone or laptop.
Roaming authenticator / hardware security key — a physical key such as a FIDO2/USB security key.
The UIID mobile app as your identity device (see section 6).
PIN / passphrase confirmation for sensitive operations.

The single most important beginner tip in this entire article: register at least TWO login methods. One device plus one hardware key, or two devices. A self-sovereign identity with exactly one authenticator is one lost phone away from being gone.

Step 5 — Back up your .uiid file

The .uiid file is LINKSPREED’s file format that acts as your local digital container for verified credentials. It uses Zero-Knowledge Proofs so your private data stays on your device instead of in a corporate database.

Treat it as the portable, encrypted embodiment of your identity:

Export/save it as soon as your identity is created.
Store it on at least two offline media (e.g. two encrypted USB sticks in two physical locations).
Optionally store an encrypted copy in a cloud vault — but only encrypted, and never together with the passphrase.
Never email it to yourself in plaintext, never put it in a shared drive, never post it in a chat.

Because it is a file, it also gives you existential portability — your identity is not locked into any single vendor’s servers.

Step 6 — (Optional) Verify as a human

Human verification unlocks additional ecosystem benefits — LINKSPREED mentions human-verified users getting access to secure private infrastructure plus 100 GB of free Web4 storage.

Crucially, verification does not cost you your anonymity: the one-time KYC binds to the Core ID and is then decoupled from every alias you use day to day.

4. What You Can Set Up After Creation

Once your identity exists, the UIID Dashboard becomes your control room. Here’s everything worth configuring.

4.1 Create and organize aliases

This is where the real power lives. Suggested beginner strategy — one alias per trust context:

Alias purpose	Example	Why separate
Public / professional	`yourname.public`	Meant to be recognizable
Social & communities	`nightowl`	Social behavior stays isolated
Shopping & commerce	`shop-2026`	Purchase history can’t be joined to social
Throwaway / testing	`tmp-signup`	Delete the moment it’s abused

Rules of thumb:

Never reuse one alias across unrelated services — that would recreate exactly the cross-correlation you’re trying to escape.
Aliases are disposable on purpose. Deleting one is a legitimate, expected action, not a last resort.
Keep your Core ID out of every third-party interaction. If something asks for it directly, that’s a red flag.

4.2 Manage authorized applications (“Act of Sovereignty”)

Registering a new application, or de-authorizing an old one, is a first-party action performed exclusively by you in the Dashboard. A developer cannot force a connection — they can only request one, which you approve or deny. LINKSPREED calls this the user’s “Act of Sovereignty” (Hoheitsakt des Nutzers).

Set up a routine: review your authorized-apps list quarterly and revoke anything you no longer use.

4.3 Configure permissions (scopes) and MFA rules

UIID uses scopes — granular permissions an application may request. The documented ones include:

Scope	What it means	Protection
`core:write`	Write access to your Core ID — a critical permission	Automatically triggers a mandatory MFA challenge
`alias:read:private`	Read sensitive alias data	Can be protected with a PIN prompt during the consent flow, per alias
`audit:read`	Read your audit log	Gives verifiable transparency

Beginner habit: when a consent screen appears, read the scopes. A simple newsletter app asking for core:write has no business doing so.

4.4 Turn on the audit log

The audit:read scope lets you track in detail which application accessed the Core ID or one of its Aliases, when, and for what purpose.

This is a genuine inversion of the status quo: normally the platform audits you. Here you audit the platforms. Check it after every new integration.

4.5 Register additional devices and recovery paths

Add a second device as an authenticator.
Add a hardware security key.
Confirm your .uiid backup still opens (test it once — an untested backup is a hope, not a backup).
Decide whether to link the optional email (section 3.3).

4.6 Claim your Web4 storage

Human-verified users get access to 100 GB of free Web4 storage, on infrastructure LINKSPREED describes as a 1 PB cloud across a decentralized node network.

4.7 Explore LNS and the web4:// protocol

Beyond identity, LINKSPREED runs the Linkspreed Name Service (LNS) and the Web4 Bridge, enabling the web4:// protocol and universal TLDs — personalized or community-governed domain extensions instead of traditional restricted domains.

Together with the .uiid file, this makes the shift from the Read-Write-Own era to a Read-Write-Own-Automate era — a protocol-native browsing experience where you hold the keys.

For everyday users

Single Alias Login means one public alias/username works across LINKSPREED’s social networks — with ZKP proving ownership of your UIID and alias without exposing private data. LINKSPREED reports 160+ social networks in its ecosystem, and web4.community lets anyone spin up their own network.

For companies

LINKSPREED has announced UIID SSO for enterprise authentication: plug-and-play APIs, biometric security, passwordless login, and a zero-data-honeypot design that eliminates compliance liabilities. For engineering teams, the pitch is that you build apps without managing user PII at all.

6. The UIID Mobile App

There’s an official Android app: UIID, package com.linkspreed.web4.uiid, published by Linkspreed UG (haftungsbeschränkt).

What it does, per the official listing:

Secure storage — personal details in a high-security digital vault that stays on your phone.
Private verification — prove things about yourself (age, location) without sharing your name or full ID.
Safe sign-ins — log into decentralized apps and services without traditional passwords.
Digital signatures — sign documents using your phone’s biometric security (fingerprint/face).
Identity protection — Zero-Knowledge verification to third parties without handing over data.

The listing also states: no data shared with third parties, data encrypted in transit, and deletion can be requested.

For beginners this is the easiest on-ramp: the phone becomes your authenticator, and biometrics replace passwords entirely.

7. A Realistic 20-Minute Starter Checklist

Open https://uiid.me on a trusted device.
Generate your Core ID.
Set a strong, unique passphrase; write it on paper and store it physically.
Register your first login method (biometrics / passkey).
Register a second login method (second device or hardware key). Do not skip this.
Export and back up your .uiid file to two offline locations.
Decide on optional email linking (dedicated address recommended).
Install the UIID mobile app.
Create your first 2–3 aliases by trust context.
Connect one service using an alias and watch the consent/scope screen carefully.
Open the audit log and confirm you can see that access.
(Optional) Complete human verification to unlock 100 GB Web4 storage.
Calendar a quarterly reminder to review authorized apps.

8. Common Beginner Mistakes

Mistake	Why it hurts	Fix
Only one authenticator registered	Lost device = lost identity	Register 2+ methods on day one
No `.uiid` backup	Nothing to restore from	Export immediately, store offline ×2
Reusing one alias everywhere	Recreates cross-service tracking	One alias per trust context
Sharing the Core ID with a service	Defeats the entire architecture	Core ID is first-party only
Approving scopes without reading	You may grant `core:write` needlessly	Read every consent screen
Storing passphrase next to the `.uiid` file	One breach compromises both	Separate them physically
Treating alias deletion as drastic	Aliases are designed to be disposable	Delete freely when trust ends

9. For Developers: Where to Go Next

If you want to integrate UIID rather than just use it:

Developer portal: https://uiid.linkspreed.com
Full API documentation: https://uiid.linkspreed.com/api-docs
UIID Cookbook (open source): github.com/Web4-Organisation/UIID-Cookbook — “Learn how to write Web4 applications with the UIID API v1 and give a decentralized ID to your users”
Web4 Lite (open-source starter): github.com/Web4-Organisation/Web4-Lite — an open-source foundation to kickstart your own Web4 network
LINKSPREED on GitHub: github.com/linkspreed
Build a social network: https://web4.community
Contact: [email protected] / [email protected]

The developer value proposition: no PII to store, no honeypot to defend, no password database to breach.

10. Further Reading & Watching

Written

The Starting Gun Has Fired: 5 Takeaways from the UIID v1 Launch — the best written overview of Core ID, aliases, scopes and sovereignty: dev.to/web4
LINKSPREEDN ecosystem overview (SNaaS, TRIVE Vertex/Origin, home nodes): linkspreedn.com

Video

LINKSPREED’s official channel: youtube.com/@linkspreed

How to Set Up a UIID Easily! (Step-by-Step Guide) — start here
UIID v1 Deep Dive — Core ID, Aliases, and ZKP Security for Web4
Zero-Knowledge Proofs and UIID Explained: Single Alias Login
Stop Being Tracked! Linkspreed UIID & The Future of Decentralized IdP
How to be ANONYMOUS Online (Even with KYC!)
The .uiid, LNS, and Web4 Bridge Guide: Mastering the web4:// Protocol
UIID SSO Announcement: Simplifying Enterprise Authentication
The Complete UIID Developer Guide

Conclusion

UIID asks you to accept one trade and gives you a lot in return. The trade: you become responsible for your own keys — your passphrase, your registered devices, your .uiid backup. In return you get an identity no company can delete, sell, leak, or hold hostage.

The mental shift is best captured by LINKSPREED’s own framing: you move from being the product to being the platform administrator of your own digital life. Or, as they put it:

“Your Data, Your Rules. Period.”

Generate your ID, set a passphrase you’ll never lose, register a second authenticator, back up your .uiid file — and start with one alias.

https://uiid.me