UIID v2.20 Introduces Alias Transfers: Hand Over an Alias to Another UIID Without Losing Anything
UIID v2.20 lets owners move an alias, with its data, keys, and challenges, to another UIID as one piece. Both sides must agree, every transfer expires after 24 hours, and 2FA and locks protect the process. Only the owner of an alias can delete it.
Albuquerque, New Mexico — LINKSPREED today announced UIID v2.20. The release adds Alias Transfers, a feature that lets the owner of an alias hand it over to a different UIID. The alias keeps its data, its keys, and its challenges. Nothing has to be rebuilt, re-created, or set up again by the new owner.
Version 2.20 also tightens one related rule: only the owner of an alias can delete it.
The complete list of changes is in the UIID changelog. More about the platform is at uiid.me.
The short version of what is new
- Move an alias to another UIID. The alias keeps its data, keys, and challenges and moves as one piece.
- Both sides must agree. The owner creates a one-time transfer code and the recipient enters it. Or the recipient asks for the alias and the owner approves the request.
- Codes expire in 24 hours. Transfer codes and requests stop working after one day, and a pending transfer can be cancelled at any time.
- The old owner’s access is a choice. When creating a transfer, the owner picks whether their access is removed or whether they stay on as a member.
- Extra protection. If 2FA is turned on, a 2FA code is needed to create, approve, or redeem a transfer. Locks can be set per alias or per account to block transfers.
- Available in the dashboard and the API. Transfers are managed on the new Alias Transfers page in the dashboard, or through the API, whose docs list every endpoint.
- Safer deletion. Only the owner of an alias can delete it.
Background: what LINKSPREED is building
LINKSPREED LLC is a company based in Albuquerque, New Mexico, working on what it calls Web4. In its own words, the idea behind Web4 is digital spaces that adapt to the people using them, with communities as stakeholders rather than just participants.
A central idea in the company’s work is Social Networks as a Service (SNaaS). Traditional software as a service gives organizations an application. SNaaS gives them their own social network, with control over branding, user experience, and data, and without data farming for ads. Communities and organizations can build and run their own spaces instead of renting a place on someone else’s platform.
Around this idea, LINKSPREED has built a growing set of products and initiatives:
- ATRIUM is aimed at organizations that need scalable SNaaS, such as company intranets and internal communities.
- web4:// is an open source protocol, announced by LINKSPREED in March 2026, for a more user-owned way of browsing.
- VIVON is a subsidiary announced in March 2026. Its goal is to bring Web4 access to everyone through mobile data.
- Hardware and edge ideas such as ARCTIC micro-servers and the WYNIX phone aim to let people run their own infrastructure at home.
All of these need one thing underneath them: a way for people, devices, and organizations to prove who they are without handing their identity to a middleman. That is the role of UIID.
Background: what UIID is
UIID is LINKSPREED’s identity layer. It is described publicly as a local-first identity protocol. Identities are created securely on the user’s own device, which removes passwords and central stores of sensitive data. It uses device biometrics and zero-knowledge proofs for private, passwordless sign-in across web and physical platforms.
Three ideas define the approach:
- The user owns the identity. UIID is built so that people stay in control of their digital identity instead of renting it from a platform.
- Aliases protect privacy. An alias lets a person show a separate identity to each service, so one profile cannot be used to track them everywhere. UIID WRAP, announced by LINKSPREED, builds on this. It detects registration forms, generates isolated aliases, and keeps the user in charge of every decision. It also uses secure relay emails and strict origin matching, which makes phishing structurally harder.
- Identity should be portable. LINKSPREED describes a future where people move their profile and data between networks without creating a new account each time.
UIID has also moved quickly. LINKSPREED announced a complete rewrite of the core architecture with UIID v2 on March 30, 2026, built to handle very large numbers of users and identifiers. Version 2.9.1 followed in August 2026, with stability fixes, backend sync improvements, and a rebuilt home at uiid.me. Version 2.20 continues that steady release pace.
Why aliases needed a way to be transferred
An alias in UIID is more than a label. Over time, an alias builds up data, keys, and challenges, and it becomes part of how a person, team, or project works online.
Real life does not stay still. A project passes from one person to another. An employee changes roles. A founder hands a community to a new lead. A business is sold. In each case, the alias should move to a new owner. Until now there was no clean way to do that. The choices were to share access in ways that were never meant for it, or to start over with a new alias and lose the history.
Alias Transfers fixes this directly. The alias moves as one piece, and it keeps everything attached to it. The new owner receives the same alias with the same history, not an empty shell.

How Alias Transfers work
Both sides must agree
The main rule of this release is that nothing moves without consent from both sides. There are two paths:
- The owner starts it. The owner creates a one-time transfer code. The recipient enters the code to take over the alias.
- The recipient starts it. The recipient asks for the alias. The owner approves the request.
An alias cannot be taken from its owner, and it cannot be pushed onto someone who does not want it.
Codes and requests expire after 24 hours
Every transfer code and every transfer request stops working after one day. A code that is never used simply expires, so a forgotten code cannot be used weeks later. The owner can also cancel a pending transfer at any time if they change their mind.
The old owner’s access is a choice
When creating a transfer, the owner decides what happens to their own access:
- Remove access. The previous owner is fully out. This fits a complete handover, such as someone leaving a team.
- Stay on as a member. The previous owner remains part of the alias. This fits a gradual handover, where the earlier owner keeps helping for a while.
Extra protection for a sensitive action
Moving ownership of an alias is a sensitive action, so version 2.20 adds several safeguards:
- 2FA at every step. If 2FA is turned on, a 2FA code is needed to create, approve, or redeem a transfer.
- Locks per alias. A single alias can be locked so it cannot be transferred.
- Locks per account. A whole account can be locked to block transfers.
An alias that should never leave an account can be locked once and stay protected.
Dashboard and API
Transfers can be managed from the new Alias Transfers page in the dashboard. The same functions are available through the API, so developers can build transfers into their own tools and workflows. The API documentation lists every endpoint.
Safer alias deletion
Version 2.20 also changes who can delete an alias. Only the owner can delete it. A member can no longer remove an alias that belongs to someone else. This matters most for shared aliases, and it works well together with transfers because ownership is clear at every moment.

What the impact could be
Alias Transfers is a focused feature, but it changes what people can do with aliases. These are the areas where it is likely to matter most.
For individuals
People change jobs, move on from projects, and clean up their digital lives. With transfers, an alias no longer has to be abandoned or deleted when its purpose changes hands. It can go to the person who will use it next, and nothing is lost on the way. The consent rule and the 24-hour expiry keep the process predictable.
For teams and projects
Shared work usually revolves around one identity, such as a project, a brand, or a community. When a lead changes, the alias can be handed to the new lead. The “stay on as a member” option lets the previous lead stay involved during the changeover. That turns a risky moment into a planned one.
For businesses and organizations
Organizations deal with role changes, departures, and restructuring all the time. Aliases that belong to a role instead of a person need a clean way to change owners. Transfer locks give security teams a clear control, and 2FA protects every step of a handover. Because transfers are also available through the API, companies can connect them to their own onboarding and offboarding processes.
For communities and Social Networks as a Service
LINKSPREED’s wider vision is that communities run their own networks. Communities do not stay in one pair of hands forever, and a community identity may need to pass from founders to new stewards. Alias Transfers gives that handover a safe and defined path. This supports the idea that identity and ownership stay with the people who actually run the space.
For developers and integrators
Everything in the dashboard is also in the API. That means developers can build handover flows into their own products, such as an app that transfers an alias when a customer account is sold or passed on.
For security and trust
Several design choices point in the same direction:
- Both sides must consent, so there are no silent takeovers.
- Codes and requests expire, so old transfers cannot return later.
- 2FA protects creating, approving, and redeeming a transfer.
- Locks give owners a hard stop.
- Deletion is limited to the owner, so a member cannot destroy something they do not own.
Together, these make a sensitive action easier to trust and easier to audit.
For the UIID ecosystem
Version 2.20 also shows where UIID is heading. An identity system matters more when it matches how people really live and work, including handing things over. By treating aliases as something that can change owners safely, UIID moves closer to being a complete foundation for the Web4 vision LINKSPREED describes, where identity stays under the control of the people and communities who use it.
Availability
UIID v2.20 is available now. Read the full list of changes in the UIID changelog, and learn more about UIID and get started at uiid.me.
About UIID
UIID is LINKSPREED’s identity platform. It is built around self-owned identity and aliases, with keys, challenges, optional 2FA, a web dashboard, and an API. It is designed so that users stay in control of their digital identity. More information is available at uiid.me.
About LINKSPREED
LINKSPREED LLC is a technology company based in Albuquerque, New Mexico, working on Web4. Its work includes Social Networks as a Service, the UIID identity platform, the ATRIUM enterprise offering, the web4:// protocol, and the VIVON subsidiary.
Links
- UIID: https://uiid.me
- UIID changelog: https://uiid.me/changelog
Press contact
Please use the contact options on uiid.me.