UIID Deep Dive: One Identity You Own, Built to Work Alongside National Digital IDs

A long read on LINKSPREED’s Universal Integrated Identity Decoupled (UIID): how it works, why it exists, why it cannot replace national digital IDs today, and why it still could in the long run.

Estimated reading time: 35–40 minutes

Key takeaways

What it is. UIID is LINKSPREED’s identity layer for Web4. It splits your identity into a protected Core ID and many context-specific Aliases. Your secret stays on your own device, and you sign in with biometrics and cryptography instead of passwords.
Who it is for. Since version 2.8, UIID is not only for people. Organisations, devices and AI agents can hold their own verifiable identities too.
How it relates to national IDs. National digital IDs, such as Germany’s wallet d-you, are the legal root of identity. UIID solves a different problem: how you appear, log in and stay private across the whole web, and how machines get identities at all.
Today. UIID complements national IDs. It cannot replace them, because it has no legal status, no state-backed source of truth and no formal certification.
Over time. UIID has real potential to replace national IDs in daily use, which means becoming the identity people actually use while the state ID shrinks to a proof in the background. That depends on conditions we spell out in Part 8.

The problem: the internet never got an identity layer
What UIID is, and where it came from
How UIID works: the architecture in plain language
UIID for machines: AI agents, devices and organisations
Beyond login: WRAP, single sign-on, mail, addressing and voting
How UIID compares to other identity technologies
National digital IDs: what they are and why they matter
UIID and national IDs: complement, limit and long-term potential
Risks and open questions
What this means for different readers
Roadmap and what to watch
FAQ
Glossary
Sources and links

1. The problem: the internet never got an identity layer

The internet was built to move data. It was never built to answer a simple question: who is on the other end? Every service solved this on its own, so we now live with the results.

Passwords and stolen credentials

Passwords are the oldest solution and still the most common. They are also the weakest. Verizon’s 2025 Data Breach Investigations Report found that credential abuse was the most common way attackers got in, at 22% of breaches. In basic web application attacks, 88% of breaches involved stolen credentials. The FIDO Alliance, the group behind passkeys, puts it more broadly: it cites Verizon figures that 77% of hacking-related breaches involve stolen credentials.

Passwords fail for human reasons. People reuse them, forget them and type them into fake websites. Fixing this does not need better people. It needs a different design.

Identity scattered across silos

Most people have dozens or hundreds of accounts. Each platform keeps its own copy of your identity data. That creates three problems:

Fragmentation. Your data sits in many places you cannot see or control.
Concentrated risk. Every database is a target, and every breach exposes real people.
Tracking. If the same email address or phone number is everywhere, platforms can link your activity across services.

The fake-identity problem

AI has made fake identities cheap. One industry benchmark from a verification vendor reports that deepfake-based fraud grew 2,137% from 2022, and that human reviewers spotted high-quality deepfakes only about a quarter of the time. This is a vendor study, so treat the numbers as indicative. The direction is clear, though: “looks like a real person” is no longer a reliable test.

A new kind of participant: machines that act for us

AI agents now book, buy, write and negotiate on our behalf. LINKSPREED describes how software agents have historically “operated in a legal and technical gray area, relying on shared human credentials or static API keys.” If an agent uses your password, nobody can tell what you did and what it did. If a shared key leaks, everything leaks.

What a good answer would need

Put together, a modern identity layer should:

work without passwords,
keep your data under your control,
stop one platform from tracking you across others,
prove you are a real, unique person when that matters, without revealing who you are,
give machines and organisations identities too, and
work together with legal identity systems instead of pretending they do not exist.

UIID is LINKSPREED’s attempt to meet that list.

2. What UIID is, and where it came from

The name

The most-used expansion on LINKSPREED’s company profile, FAQ and technical articles is Universal Integrated Identity Decoupled. The word decoupled is the key idea: your identity is separated from any single platform. Other LINKSPREED materials use slightly different expansions, including “Universal Internet Identity” in the v2.8 press release and “Universal Identifier” in the Biometric Update profile. A video description also mentions “Unique Immutable Identity”.

The company

LINKSPREED LLC was founded in 2025 and is headquartered in Albuquerque, New Mexico. It was previously known as Linkspreed UG. It describes its mission as building Web4, “a community-based internet”, with products such as TribeMaker for instant community building and Social Networks as a Service. UIID is its identity system. Company materials also list other parts of the ecosystem: VIVON, ARCTIC, HELION, TRIVE, ATRIUM and WYNIX.

From a sketch to a platform: a timeline

When	What happened
January 2025	LINKSPREED publishes a first sketch called UI4, the “Unique Identity model for Web4”. It is described as “still in its early planning stages”, a single, adaptable identity across the Web4 ecosystem.
Autumn 2025	UIID v1 launches. Launch posts describe the two-layer model (Core ID and Aliases), a passwordless flow that combines zero-knowledge proofs with WebAuthn, scopes, mandatory multi-factor authentication for critical actions and audit logs. Shortly after, v1.2 removes mandatory centralised identity checks (KYC) and announces a partnership with Cloudflare.
Later in 2025–26	Optional trust scores and optional KYC are added as modules that platforms and communities can switch on. LINKSPREED announces a goal of supporting the 100 most-used social and banking login providers by 2027.
16 June 2026	v2.8 widens UIID to six entity types, including AI agents, with autonomous agent registration and the Agent Factory.
Mid-2026	v2.8.1 improves the skill.md format for agents. v2.9 adds human-friendly short IDs.
4 August 2026	v2.9.1 launches the new hub at uiid.me with documentation and industry examples.
Summer 2026	v2.9.2 adds a system-adaptive dark mode. LINKSPREED says it is now on v2.10.1.
Autumn 2026	UIID WRAP, the embeddable login button, the identity-addressed networking concept and UIID Mail (beta) are announced, and development of UIID Coins starts.

LINKSPREED keeps a public changelog at uiid.linkspreed.com/changelog.

The bigger picture: UIID as the identity floor of a seven-layer stack

UIID does not stand alone. In 2026, LINKSPREED said it had submitted two papers, one of them to IEEE. The first defines a “seven-layer sovereign-ownership architecture” for Web4, built around cryptographic, time-boxed capability grants. The second maps that architecture to LINKSPREED’s own products, UIID among them. A video on the 100-logins goal also explains how UIID acts as the foundation for storage and communication in this stack.

You do not need to believe in “Web4” to use UIID. But it explains the design: everything that comes later (mail, payments, social networks, addressing) is meant to hang off one identity.

3. How UIID works: the architecture in plain language

3.1 Two layers: Core ID and Aliases

This is the central design idea.

Core ID is “the immutable, sovereign root of you”. It is never shared directly with third-party services. You use it only for your own first-party actions, such as managing the apps you have authorised in your UIID dashboard. Aliases are context-specific identities, “the mask you wear” for social media, shopping or gaming. Each service sees only the Alias you created for it.

LINKSPREED states the goal directly: the split prevents outside platforms from correlating your behaviour across independent services.

An everyday picture. Think of your Core ID as your passport in a safe at home. Your Aliases are name badges you wear at different events. People at the event see your badge. They never need your passport. If one badge is lost or misused, you retire it, and your passport is untouched.

A walk-through.

Alex creates a Core ID on a phone. The secret key is generated on the device and stays there.
Alex joins a gaming community and creates the Alias “nightowl” for it.
Alex later joins a professional network and creates a different Alias for it.
Neither service can tell that the two Aliases belong to the same person, because the link exists only on Alex’s side.
Alex’s Core ID is used only inside Alex’s own dashboard, for example to review which apps have access.

Version 2.9 also gives identities human-friendly short codes instead of long cryptographic strings, so an identity can be typed or read aloud.

3.2 Passwordless by design: keys on your device

UIID uses two technologies together: WebAuthn and zero-knowledge proofs. LINKSPREED says the combination means you prove your identity “using a registered device or a physical security key without ever sending a password or any secret key over the network.”

WebAuthn and passkeys in plain words. WebAuthn is a web standard. It lets your device create a pair of keys for each site: a private key that never leaves the device, and a public key the site stores. When you log in, the site sends a random challenge. Your device signs it after you unlock with a fingerprint, face or PIN, and the site checks the signature. Because the signature is tied to the website’s real address, a fake site cannot reuse it, which is why passkeys are considered phishing-resistant.

The standard is now mature. On 25 August 2026, the W3C published WebAuthn Level 3 as a full Recommendation, the final and most stable stage of its process. Building on this ecosystem gives UIID a solid base.

Where UIID goes beyond a passkey. A passkey proves “this is the same account as last time”. It does not by itself give you a layered identity, aliases, entity types, trust scores or machine identities. That extra layer is what UIID adds on top of the same cryptographic idea.

3.3 Zero-knowledge proofs: proving without showing

A zero-knowledge proof (ZKP) lets you prove a statement is true without revealing the data behind it. LINKSPREED says this allows actions such as age or location verification “without ever disclosing names or full government IDs.”

An analogy LINKSPREED’s own election article uses: proving you hold the key to a house by opening the door, without ever showing the key.

A useful nuance. There are different privacy techniques, and they are not the same:

Selective disclosure (used in the EU wallet’s credential formats SD-JWT VC and mdoc) lets you reveal only some attributes, for example “over 18” instead of a full birth date. It works through salted hashes that the issuer signs.
Zero-knowledge proofs go further. They can also stop different services from correlating your proofs. The EU’s age verification blueprint now defines ZKP as the mandatory presentation method, with plain mdoc presentation as a fallback. It reveals only whether the user meets the age threshold, and visits to different services cannot be correlated.

This matters for the story that follows: the EU itself is moving toward the same cryptographic ideas that UIID is built on.

3.4 Fine-grained control: scopes, multi-factor authentication and audit logs

The v1 design includes detailed permissions called scopes, with examples such as core:write and alias:read:private. It also requires multi-factor authentication for critical operations and provides audit-log endpoints so users can see what happened.

In plain words: an app asks for the minimum access it needs, you see what you granted, and risky actions need an extra check.

3.5 Hardware-anchored, biometric security

UIID identities are secured locally in the device’s security hardware using WebAuthn. LINKSPREED’s argument is that requiring local biometrics makes mass bot networks and throwaway deepfake profiles “economically and technologically impossible.”

That is a strong claim. A fair way to read it: every fake identity needs real hardware and a real biometric, which raises the cost of faking at scale. Whether it makes fakes impossible is something independent testing should confirm. Device farms and stolen devices are the obvious cases to test.

3.6 Bridging the old web: turning logins you already have into sovereign keys

Most people already have a Google, social or banking login. UIID can convert these into decoupled keys. After the system verifies you are a human, the connection to the legacy login is cut, and you receive 100 GB of dedicated Web4 storage. LINKSPREED’s goal is to support the 100 most-used identity endpoints by 2027, so that decentralised identity feels “as convenient as a traditional social login”.

The old login becomes a one-time checkpoint instead of the foundation of your identity.

3.7 Trust without exposure: optional trust scores and optional KYC

Here UIID’s position shifted in an instructive way.

Version 1.2 removed mandatory centralised KYC (Know Your Customer, the identity checks that banks and regulated companies must carry out). LINKSPREED framed this as a truly anonymous, global identity chosen by the user. Later, UIID introduced voluntary trust scores and optional KYC built into the user’s own hardware. A secure “mathematical anchor” in tamper-proof storage lets platforms confirm someone is a real person without seeing a government ID or home address. The system is modular: community admins can switch these layers on to fight botnets and protect private spaces, “without becoming centralized gatekeepers”.

LINKSPREED’s own election article describes the intended model. A one-time registration ties to the Core ID, “a primary, verifiable identity used for high-trust scenarios like banking’s KYC”. The Core ID is then never used to cast the ballot, and zero-knowledge proofs show that a valid registered Core ID exists.

Why this matters for the national-ID question. UIID is designed so that a high-trust anchor can exist when needed, and stays optional and private when not. That is the hook where national digital IDs and UIID can connect, as Part 8 explains in detail.

For developers, UIID offers a REST API and a privacy-first, passwordless single sign-on framework. LINKSPREED positions this against traditional single sign-on, which “centralizes sensitive data, creating major security vulnerabilities and password fatigue”. A separate announcement says building login infrastructure no longer needs “weeks of complex SAML or OAuth setups”.

The embeddable login button goes further. It is a snippet for shop templates, community platforms and custom sites. LINKSPREED says it carries the complete sign-in flow without server-side code while keeping sensitive credentials strictly off the client side. For small sites, this lowers the barrier to adding modern login a great deal.

There is also an open-source side. LINKSPREED’s GitHub hosts the UIID Cookbook, which teaches developers to build Web4 applications with the UIID API v1, and Web4 Lite, an open-source foundation for starting your own Web4 network.

4. UIID for machines: AI agents, devices and organisations

Version 2.8, released on 16 June 2026, is where UIID stops being a human-only system.

4.1 Six entity types

The update defines six distinct entity types, each with its own enrollment flow and icon theme. The announcement names three clearly: Human Individual (decentralised identities for physical people), Organization (companies, non-profits and institutions) and AI Agent (identity roots for LLM-driven entities and workflows). It also refers to hardware devices as holders of identity.

4.2 Autonomous agent birth with skill.md

Agents can register their own UIID accounts using a machine-readable skill.md protocol. Public profiles support OpenClaw-compatible Markdown communication, so agents can advertise what they can do and negotiate handshakes with other nodes. Version 2.8.1 optimised skill.md so agents can navigate protocols using progressive disclosure, meaning they load only the instructions they need, together with zero-knowledge proofs.

4.3 The Agent Factory

Fully decentralised agent creation could become chaos, so LINKSPREED added the Agent Factory, “a centralized control center” for individuals and organisations. From it, creators can issue multi-use provisioning tokens, start new machine processes, and monitor fleet activity, resource use and trust scores in real time.

Note the design choice. The identity of each agent is cryptographic, but the management of a fleet is deliberately centralised in the hands of the responsible owner. That is how accountability works in practice: an agent’s identity can be traced back to the person or organisation that created it.

4.4 Zero-trust provisioning

Static secrets and long-lived access keys are replaced with dynamic, single-use or multi-use authorisation tokens. A stolen token cannot be used to compromise a whole fleet. This matters because leaked secrets are a growing problem in their own right. The 2025 Verizon report shows credential exposure through third parties and infostealer malware feeding the same attack chain.

4.5 Verified access for AI agents: WebMCP

LINKSPREED has also made its Web4 platform accessible to AI agents through Cloudflare’s WebMCP. Instead of scraping screens, agents can discover and call site functions directly. To keep this secure, agents must hold a valid UIID digital passport.

4.6 Why this matters

There is currently no widely accepted way to say “this agent belongs to that company and is allowed to do this”. National digital ID systems are designed for natural and legal persons. That leaves a gap for software and devices, and UIID is built to fill it. We return to this in Part 8, because it is one of the strongest arguments for UIID as a complement.

5.1 UIID WRAP: privacy for sites that do not support UIID

The hardest problem for any new identity system is that most websites will not integrate it for years. UIID WRAP, announced in October 2026, addresses this. It extends privacy-focused identity management “across the entire web”. It detects registration forms, generates isolated aliases and prepares credentials, while the user stays “strictly in charge of every decision”.

In practical terms, WRAP could let you use a fresh Alias on an ordinary website that has never heard of UIID, with you approving each step. The official press release is at blog.linkspreed.com/press/uiid-wrap-announcement/.

5.2 UIID Mail and UIID Coins

Two services are being built on top of the identity layer:

UIID Mail is in beta. LINKSPREED describes it as passwordless, self-sovereign email built on UIID infrastructure.
UIID Coins has entered development. LINKSPREED describes peer-to-peer shared buckets for messages and “immutable, private audit streams” for financial transactions.

Both are early. They show where the project is heading, an identity that also carries communication and value, but they should not be presented as finished products.

5.3 Identity-addressed networking: the boldest idea

Every internet packet today relies on a numeric IP address, which is a location label, not an identity. LINKSPREED argues that address-based networking forces authentication to happen after a connection is established, and struggles with problems such as address exhaustion and NAT. Its alternative is identity-addressed networking: devices, servers and users verify each other cryptographically before a session starts, without a central numbering authority. The related building blocks it names are LNS, the web4:// protocol and the BRIDGE browser.

This is the most ambitious part of the vision. It is best read as a research direction, not a replacement for today’s internet.

5.4 Voting: a concept, not a deployed system

LINKSPREED has also published a concept for secure elections. Eligibility is proved once through the Core ID, and the ballot is cast with zero-knowledge proofs, so the system can confirm “a unique, eligible voter is present, but never who that voter is”. This is a design proposal. Real elections depend on law, auditing and public trust, far beyond a protocol.

6. How UIID compares to other identity technologies

A fair comparison helps readers place UIID. The table is a simplified overview.

	Passwords	“Log in with Google” style	Passkeys (FIDO / WebAuthn)	National eID / EU wallet	W3C DIDs and Verifiable Credentials	UIID
Who controls it	You and the site	A big platform	You (device)	The state, with user control over sharing	The holder	You (device)
Main strength	Familiar	Convenient	Phishing-resistant login	Legal identity	Open standards for portable credentials	Layered, private identity for people, organisations, devices and agents
Cross-site tracking risk	Medium	High	Low (key per site)	Depends on implementation	Low if designed well	Low by design (Aliases)
Legal weight	None	None	None	High	Depends on issuer	None on its own
Machines and agents	Shared secrets	No	Limited	Not designed for it	Possible	Built in (since v2.8)

A few notes on the standards column:

Decentralized Identifiers (DIDs) became a W3C standard in July 2022. They are identifiers that can be created and controlled without a central registry, and they can identify “a person, an organization, a device, a product”. Verifiable Credentials 2.0 became a W3C Recommendation in May 2025. It defines how an issuer makes claims about a subject, a holder presents them, and a verifier checks them cryptographically. In the EU wallet’s technical framework, the two mandatory credential formats are SD-JWT VC and mdoc, while the W3C format is listed as optional and meant for non-qualified attestations only.

Open point for LINKSPREED. In the sources we reviewed, LINKSPREED does not say whether UIID identities and Aliases can be expressed as DIDs and verifiable credentials. Publishing a clear mapping would make UIID much easier to connect to wallets and enterprise systems. That is a recommendation, not a finding.

7. National digital IDs: what they are and why they matter

To see how UIID fits, we first need to understand what national digital IDs actually do.

7.1 The European framework (eIDAS 2.0)

The EU’s Regulation 2024/1183, known as eIDAS 2.0, requires every member state to offer at least one European Digital Identity Wallet. The legal deadline is 24 December 2026. The regulation builds on national systems: digital identities continue to be provided by member states, and the wallet extends their functionality and ensures mutual recognition across borders. Service providers that are legally obliged to identify customers must accept the wallet.

Key rules from the regulation text (Article 5a):

Wallets can be provided directly by a member state, under a mandate from a member state, or independently but recognised by that state.
The source code of the wallet’s app components must be open-source licensed.
Wallets must let users share data selectively, generate pseudonyms and store them encrypted on the device, see a log of all transactions and sign with qualified electronic signatures.
Where no legal identification is required, services must accept identification by pseudonym.

7.2 Germany’s wallet: d-you

Germany’s wallet is called d-you. The state app is due to launch on 2 January 2027. It is free and voluntary, and credentials are stored encrypted only on the phone. The physical ID card stays valid. About 40 partners, including Deutsche Post, Vodafone, Rossmann, the Bundesagentur für Arbeit, the Deutsche Rentenversicherung and the banking associations, plan to offer services at launch, such as age checks, contracts and bank accounts. The app is operated by Common Code, a unit of the Agentur für Sprunginnovationen, and its source code is open.

Coverage of a Bundestag committee hearing on 6 October 2026 adds two points. The first version is expected to offer only the ID function at launch, with the driving licence and other credentials coming later. Experts also asked for improvements to the planned Digital Identities Act.

An important detail for this article. The German government says that alternative wallet providers should be able to have their solutions certified and officially recognised as EUDI wallets in Germany about twelve months after d-you launches. This is the legal door through which a private wallet could eventually enter.

7.3 Why national IDs are strong at what they do

They answer the legal question. “Who is this person under the law?” Only a state can ultimately decide that.
They connect to official registers. Names, dates of birth and addresses come from authoritative records.
They carry legal consequences. Qualified electronic signatures and mandatory acceptance by regulated industries only work with regulated, certified components.
They come with accountability. Certification, supervision, courts and parliaments stand behind them.

7.4 What the German and Estonian experience teaches

Having a national digital ID is not the same as people using it.

Germany introduced the online ID function in 2010. A Max Planck Institute study from October 2024 found that only 35% of adults had activated it, and 6% did not know it existed. Activation requires a trip to a citizens’ office, while in Estonia and Belgium the function is active automatically. The study also points to a lack of use cases. The 2024 eGovernment Monitor found that 22% of people had used the eID, up from 14% the year before. Yet 52% said they use e-government less because they would have to identify themselves online, and 24% had abandoned a digital process for that reason.

Estonia shows what a rich ecosystem can look like. Its national data-exchange layer, X-Road, supports over 3,800 e-services, about 2.2 billion transactions per year, and 78,000 organisations as indirect users. It is also worth noting that, according to Privacy International, Estonia’s e-ID is both designed and operated by a collection of private companies under state oversight.

The lesson: identity infrastructure succeeds when it is useful in daily life, not only when it is legally correct. That is exactly where an everyday identity layer can add value.

7.5 The privacy debate around national wallets

The national wallet is not a finished, uncontested design. Several groups have raised concerns:

The German Federal Data Protection Commissioner asked that users can also use the wallet pseudonymously, so citizens do not reveal more than necessary.
The consumer federation asked for selective disclosure and data-minimising age checks.
IT security researcher Jiska Classen warned about risks on compromised smartphones, noted that large parts of the security architecture were not yet public, and asked for an easy way to lock a wallet after loss or attack, plus clearer liability rules.
In March 2026, European Digital Rights (EDRi) and nine other organisations argued that draft implementing rules weaken the wallet’s untraceability and unlinkability safeguards, add a mandatory processing of facial biometric data and read the pseudonym provisions too narrowly.

These are criticisms of draft rules, and the process is ongoing. They show clearly that privacy-by-design at the layer of everyday use is still an open need. It is the need UIID’s Alias model is built for.

8. UIID and national IDs: complement, limit and long-term potential

This is the heart of the article. We separate three questions:

Why does UIID complement national digital IDs?
Why can UIID not replace them today?
Why does UIID still have the potential to replace them in practice?

8.1 Two different questions

A national ID answers: “Who is this person, legally?”

UIID answers: “Is this the same trusted participant I met before, and can they prove what I need without revealing more?”

Most of what happens online needs the second answer. Joining a forum, commenting, playing a game, downloading a file, using a community platform: none of these needs your legal name. A few things do: opening a bank account, signing a contract, applying for a benefit. Those need the first answer.

	National digital ID / EU wallet (e.g. d-you)	UIID
Root of trust	The state and legal identity	The user’s device and keys
Main purpose	Prove who you legally are	Control how you appear and act across the web
Strongest use	Authorities, banking, contracts, regulated services	Everyday logins, privacy, communities, apps, machines
Who can hold it	Natural and legal persons	Humans, organisations, devices, AI agents
Privacy model	Selective disclosure, pseudonyms required by EU law	Core ID and Aliases, zero-knowledge proofs
Reach	EU first, with mutual recognition between member states	Global by design, and aims to reach sites that have not integrated it (via WRAP)
Status	Launching from the end of 2026	Live, with ongoing releases

8.2 Seven reasons UIID is a complement

Different jobs. As above: legal proof versus everyday identity and privacy. They sit at different layers.
The law itself asks for a separate everyday layer. eIDAS 2.0 requires wallets to be able to create pseudonyms and store them locally, and it requires services to accept pseudonyms when no legal identification is needed. A Core ID with Aliases is a purpose-built version of that idea, with the advantage of working beyond one country’s wallet.
Privacy gaps in the national layer leave room. Civil-society groups and the data protection commissioner warn about untraceability, pseudonyms and over-identification. A layer designed from the start for isolated Aliases and zero-knowledge proofs can reduce the data that ever reaches a service. In effect, it can sit in front of the national wallet.
Machines are outside the legal frame. The regulation talks about natural and legal persons. AI agents, bots and devices need verifiable identities too, and UIID already provides them with accountability back to an owner.
Reach beyond the rollout. Member states are at very different stages of readiness, and the Commission itself has doubted that every country will make the December deadline. UIID is available today, anywhere in the world, and WRAP aims to help even on sites that never integrate it.
Shared technical direction. Both worlds are moving toward device-bound keys, selective disclosure and zero-knowledge proofs. The EU’s age verification blueprint is a good example. That makes technical cooperation realistic.
A hybrid model matches how successful systems already work. Even in Estonia, widely seen as the benchmark, the national e-ID is built and operated with substantial private-sector involvement. The EU explicitly allows wallets from private providers that a member state recognises. The ecosystem is designed to be plural.

8.3 A concrete model: the “anchor” pattern

Here is how the two layers could work together in practice. This is a design pattern, not a statement that every step exists today.

Legal root. A citizen holds d-you, which contains a state-issued identity credential.
Anchor. The citizen links their UIID Core ID to that credential once. The proof is cryptographic and stays local. LINKSPREED’s optional-KYC design, a “mathematical anchor” in tamper-proof hardware, describes exactly this kind of step.
Uniqueness. Research prototypes show it is possible to combine an issuer-signed credential with zero-knowledge proofs and a one-way “nullifier” to enforce one account per person without revealing who the person is.
Aliases carry only what is needed. A forum Alias carries “verified unique human”. A shop Alias carries “over 18”. A bank gets a high-trust, KYC-grade proof. None of them sees the Core ID.
Machines inherit accountability. An AI agent created in the Agent Factory is tied to its owner’s identity, so a service can accept it and know who is responsible.

In this model the state remains the source of truth for “this is a real, unique person”, and UIID becomes the privacy and usability layer on top.

8.4 Worked scenarios

Scenario A: opening a bank account. The bank is legally required to identify the customer, so it must accept the national wallet. UIID cannot replace this step. What UIID can do is hold the resulting verified status as a private attribute, so the customer does not need to repeat the whole process everywhere else.

Scenario B: joining an online community. No legal identity is needed. The community admin wants to avoid bots and does not want to run a database of passports. With UIID, the admin can turn on optional trust or verification layers, and members join with Aliases. Here UIID is already the better fit than any national wallet.

Scenario C: buying age-restricted goods online. The shop needs only “over 18”. Both worlds can deliver this. The EU blueprint uses zero-knowledge proofs to reveal only the age threshold. d-you also plans age verification at launch. UIID can present the same proof through an Alias, so the shop learns nothing else and cannot link the purchase to other activity.

Scenario D: a company deploys 200 AI agents. National wallets are not designed for this. With UIID, the company registers as an Organization, creates agents in the Agent Factory, issues short-lived tokens and monitors their trust scores. The company’s own legal identity can still come from the national or business-wallet layer.

Scenario E: a freelancer working across borders. One person, many clients, several countries. A UIID Core ID with several Aliases (one per client or project) keeps work contexts separate. Where a client legally requires proof of identity, the freelancer presents the national wallet credential.

Scenario F: signing a binding contract. A qualified electronic signature is a regulated trust service within the EU framework. This remains with the national or qualified layer for now.

8.5 Why UIID cannot replace national IDs today

We believe honesty here builds trust.

No legal status. A state-issued ID carries legal weight. UIID alone does not. Services that are legally obliged to identify customers must accept the national wallet, not a private identity.
The source of truth is the state. Member states provide the underlying digital identity. Someone has to confirm that a real person matches a real record. Academic work on self-sovereign identity makes the same point: most such systems derive their legitimacy from traditional institutions such as national ID issuers and KYC providers, which leaves open the question “who verifies the verifier?”. A decentralised identity can be private and user-controlled, but proving that someone is a unique real human usually still depends on an authoritative source.
The identity trilemma. Researchers describe a tension between three goals: strong resistance to fake or duplicate identities (Sybil resistance), self-sovereignty and privacy. UIID aims at all three. The hardware anchor is how it tries to get Sybil resistance without a central registry. Whether that is enough at national scale is not yet proven.
Regulated trust services. Qualified signatures, certification and supervision belong to a regulated framework.
Certification and audit. National wallets come with certification, conformity assessment and public scrutiny, and their security is still being reviewed by experts. UIID needs comparable independent checks before banks and regulators will treat it as an equal.
Registering is not certification. LINKSPREED has registered on Germany’s official EUDI wallet service-provider marketplace. It describes this as a step toward eIDAS 2.0 readiness and toward connecting UIID to European standards, so an identity can cross borders without re-verification. LINKSPREED also says it is investing heavily in making eIDAS 2.0 verification almost free. A directory listing is a positive start, but it is not the same as being a certified wallet.
Inclusion and fallback. National systems must work for everyone, including people without a modern smartphone. d-you keeps analogue services in place. A privately run layer has no such duty.

So “UIID instead of the national ID” is not a realistic claim today, and we do not make it.

8.6 Why UIID still has the potential to replace national IDs

“Replace” can mean two different things:

Legal replacement: the state stops issuing IDs. This is neither likely nor needed.
Practical replacement: UIID becomes the identity people actually use day to day, while the national ID shrinks to a background proof they present rarely.

The second meaning is where the potential lies. This is our assessment, not a forecast:

Convenience wins. If one identity handles logins, privacy, mail, payments and agents, the national wallet becomes something you use occasionally. Germany’s own numbers show how much room there is: only 22% had used the online ID in 2024, and many abandon processes that require it.
Recognition can be earned. The EU already allows wallets provided independently of a member state but recognised by it. Germany plans to open certification to alternative providers about twelve months after d-you’s launch. A certified UIID could carry state-backed credentials itself.
Less data means less risk. If platforms never hold your real identity, there is no honeypot to breach. This is the stated goal of regulators and privacy groups alike.
It scales to new kinds of identity holders. Devices, organisations and agents will need identities in huge numbers. National systems were not built for this, and UIID already treats them as first-class citizens.
It crosses borders without new legislation. National IDs work within legal territories and rely on mutual recognition. A global layer can span them.
The standards are converging. WebAuthn L3 is now a W3C Recommendation, Verifiable Credentials 2.0 is a standard, and the EU is pushing zero-knowledge proofs for age checks. The pieces UIID needs are no longer exotic.

8.7 What has to be true first

Condition	Why it matters
Independent security audits and public technical documentation	Trust must be earned in the open. LINKSPREED mentions “the strictest security audits” for v1, but readers will want the actual reports.
Formal recognition under the EU wallet framework	Legal weight cannot be self-declared.
Open standards and interoperability (DIDs, Verifiable Credentials, OpenID4VP, SD-JWT VC, mdoc)	Avoids lock-in and makes a link to national wallets possible.
A published open-source core	The EU requires wallet app components to be open-source licensed. LINKSPREED already publishes parts on GitHub.
Reliable recovery after a lost or stolen device	A self-owned identity needs a safe way back. Experts ask the same of national wallets.
Careful implementation	Early EU age-verification pilots were bypassed within 48 hours of launch. Researchers called it an implementation flaw, not a flaw in the cryptography.
Clear governance	Parts of UIID, such as the Agent Factory, are described as centralised control centres. The line between “decentralised” and “centrally managed” should be explained.
Clear dependence disclosure	Cloudflare is a named partner. Users should know which infrastructure the system depends on.

8.8 A realistic path in three stages

Now: complement. Use the national wallet for legal acts and regulated services. Use UIID for everyday privacy, logins, communities and machine identity.
Next: connect. UIID joins the EUDI ecosystem as a service layer, and a Core ID can be anchored to a credential from the national wallet.
Later: carry. If UIID is certified, it can present state-backed proofs itself. For many users it becomes the main identity layer, with the national ID as the root behind it.

9. Risks and open questions

A deep dive that only lists strengths is marketing. Here is a candid list.

Device security. Both UIID and national wallets depend on the security of your phone or security key. Experts warn about compromised smartphones. A hardware anchor helps, but cannot solve a fully compromised device.

Recovery. If keys live only on your device, losing the device must not mean losing your identity. The sources we reviewed do not describe UIID’s recovery process in detail. This should be explained clearly.

Biometrics. UIID relies on local biometrics. Local processing is much less problematic than central storage. The EU debate shows how sensitive the topic is: civil-society groups criticised a proposed mandatory facial-biometric processing in the national wallet rules. UIID should state exactly what biometric data is processed, where, and what is optional.

“Anonymous” versus “accountable”. Version 1.2 promised a truly anonymous identity without mandatory KYC. The later optional trust and KYC modules add accountability where it is needed. This is a sensible design, but communication should make clear that anonymity and proof of being a real person are different things, and that platforms can choose which to require.

Centralisation. Decentralised identity still needs some shared services (directories, hosting, the Agent Factory). Being open about which parts are central builds credibility.

Maturity of newer features. WRAP, the embeddable button, identity-addressed networking, UIID Mail and UIID Coins were announced in October 2026 or are still in development. They should be judged on delivery, not on announcements.

Implementation bugs. The EU age app was bypassed within two days of its pilot launch. Strong cryptography does not prevent weak implementation. Open code, bug bounties and third-party audits are the best answer.

Open-source status. The sources show open-source repositories such as the UIID Cookbook and Web4 Lite. Whether the full UIID core is open-source is not clear from what we found.

10. What this means for different readers

For individuals

Create a free Core ID at uiid.me and use Aliases for different parts of your online life.
Keep using your national ID or wallet for official matters. Think of UIID as the layer for everything else.
Protect your device, enable a screen lock and keep a recovery plan.

For developers

Start with the UIID Cookbook on GitHub and the API documentation at uiid.linkspreed.com.
Try the REST API or the embeddable login button for a no-backend integration.
If you build for the EU market, learn the national-wallet standards too (OpenID4VP, SD-JWT VC and mdoc).

For communities and platforms

Use optional trust and verification layers to reduce bots without storing passports.
Decide what you need to know. Most communities need “unique human”, not “legal name”.

For companies

Plan for two layers: a national or business wallet for legal identification, and a privacy-preserving layer for everyday access and for machine identities.
If you run AI agents, think about how each agent is identified and who is accountable for it. The Agent Factory is one answer.

For public-sector readers

UIID and national wallets do not compete in the same layer. Consider how a certified, privacy-preserving everyday identity could take pressure off the national wallet, especially for pseudonymous use, as the data protection commissioner has requested.

11. Roadmap and what to watch

Date	Milestone
24 December 2026	Legal deadline for each EU member state to offer at least one EU Digital Identity Wallet.
2 January 2027	Planned launch of d-you in Germany.
2027	LINKSPREED’s target to support the 100 most-used login providers in UIID.
Around late 2027	Regulated organisations (banks, telecoms, large platforms and others) are expected to start accepting the wallet.
About 12 months after d-you’s launch	Planned opening for certification of alternative wallets in Germany.

What to watch in the UIID project:

Independent audits and published security documentation.
A clear technical mapping to EU wallet formats and W3C standards.
Progress from “registered on the marketplace” toward formal recognition.
The delivery of WRAP, UIID Mail and the embeddable login button.
A transparent recovery and governance model.

12. FAQ

What does UIID stand for? Most often “Universal Integrated Identity Decoupled”, as on the company profile and FAQ. Other materials use slightly different expansions.

Is UIID a replacement for my national ID card or d-you? No. It is an addition. It does not carry legal status on its own.

Could UIID replace national IDs in the future? It has the potential to become the identity people use every day, if it earns recognition, passes audits and connects to the legal systems. That is a long path.

Does UIID store my personal data on a central server? LINKSPREED says your secret is stored only on your device and that the system uses local computation. Details of what is stored where should be checked in the official documentation.

What is the difference between a Core ID and an Alias? The Core ID is the protected root that you do not share with third parties. An Alias is a context-specific identity for one service or purpose.

Do I need a password? No. UIID uses device-bound keys and biometrics through WebAuthn.

What happens if I lose my phone? This is an important open question. Recovery should be explained clearly in the official documentation before you rely on UIID for anything critical.

Is UIID only for humans? No. Since v2.8 it supports organisations, AI agents and devices.

Is zero-knowledge the same as selective disclosure? No. Selective disclosure reveals only chosen attributes. Zero-knowledge proofs can also prove a statement without revealing the data and can prevent correlation.

Is UIID compatible with the EU digital identity wallet? LINKSPREED has registered on Germany’s EUDI wallet service-provider marketplace and describes this as a step toward European standards. Registration is not certification.

How much does it cost? LINKSPREED says you can get a UIID for free at uiid.me. Terms for business use should be confirmed on the website.

13. Glossary

Alias: A context-specific identity derived from your Core ID. Each service sees only its own Alias.
Core ID: The protected root identity in UIID, not shared with third-party services.
DID (Decentralized Identifier): A W3C standard identifier that can be created and controlled without a central registry.
eIDAS 2.0: The EU regulation (2024/1183) that requires member states to offer digital identity wallets.
EUDI Wallet: The European Digital Identity Wallet, a phone app for identity and credentials.
KYC (Know Your Customer): Identity checks that banks and other regulated companies must perform.
mdoc / SD-JWT VC: The two credential formats that EU wallets must handle.
Passkey: A phishing-resistant login based on a key pair stored on your device.
Selective disclosure: Revealing only some attributes of a credential.
Sybil attack: Abusing a system by creating many fake identities.
Verifiable Credential: A digitally signed set of claims by an issuer about a subject.
WebAuthn: The W3C web standard for logging in with device-bound public-key credentials.
Zero-knowledge proof (ZKP): A way to prove a statement is true without revealing the underlying data.

Conclusion

The central idea of UIID is simple. Your identity should belong to you, work across the whole web, reveal only what is needed and extend to the machines that act for you. The central question for the next few years is how that idea meets the state-backed identity systems that are arriving at the same time.

Our answer is: side by side first, and possibly in place of later. Today, a national digital ID answers the legal question and UIID answers the everyday question, so each is stronger with the other. If UIID proves itself through audits, open standards and formal recognition, it can grow from complement into the identity people reach for first.

Read the product details at uiid.me and decide for yourself.

14. Sources and links