SWSS Unified App
Signing In with SWSS IVL
Pre-launch
Section
SWSS Unified App
Product documentation
Type
Guide
Technical reference
Summary
How to sign in to the SWSS Unified App through SWSS IVL, which domain to check before you authenticate, and what a signature authorises.
SWSS Unified App

The single application through which a member holds, moves and participates across the SWSS ecosystem — one verified identity, one portfolio, and every product settling on the same layer rather than a separate account per product.

Open SWSS App →These guides describe the application as a member uses it.
Article Content

The SWSS Unified App does not operate its own login. Authentication belongs to the SWSS Identity Verification Layer, and the application asks IVL who you are rather than deciding for itself.

The practical consequence for a member is that there is no application password to manage, and no separate account per SWSS product. The architectural consequence is more important: the application never holds the material that proves who you are, so there is no application credential store to compromise.

Signing In, Step by Step

  1. Open the application and begin. There is no username and password form. The application presents the connection options available to you, because it is not the thing deciding who you are.
  2. Choose the SWSS Global Wallet. This is the wallet operated by SWSS IVL, and it requires no prior wallet setup: it is the route for a member who holds no wallet of their own. A member who already uses a self-custody wallet may connect that instead; both arrive at the same place.
  3. Check the address bar before you enter anything. Authentication happens on ivl.swss.io. That domain, exactly. This is the one step worth slowing down for: see the warning below.
  4. Authenticate with SWSS IVL. Your identity is established there, on IVL's own page. Nothing you enter is seen by the application.
  5. Return to the application, signed in. You are returned automatically. The application receives confirmation of who you are and no credential of any kind.
The domain is the thing to check, and it is the only thing that protects step 4

Because identity is handled outside the application, a page that looks like the identity step is the obvious way to attack this design. Two rules defeat it. Authentication is only ever on ivl.swss.io, and an approval is only ever at ivl.swss.io/approve: a page reached any other way is not SWSS, however closely it resembles this one. And a sign-in you did not start is not yours: if a prompt arrives without you opening the application, close it. SWSS will never ask you for recovery material, on any domain.

If Signing In Does Not Complete

The flow crosses from the application to IVL and back, so a failure is usually at the boundary rather than in either side. Begin again from the application rather than from a link, a bookmark of the identity page, or a browser tab left open from a previous attempt, a return that has nowhere to return to is the most common cause. If it still does not complete, your verified status is unaffected: it is a credential held by IVL and is not lost by a sign-in that failed.

What a Signature Means

Throughout the application, actions of consequence are confirmed by signing rather than by clicking. This is worth understanding rather than clicking through, because the distinction is what protects you.

A signatureWhat it is
Authorises one specific thingA signature covers the action described in front of you. It is not a standing permission and does not authorise a future action
Is produced by you, not by SWSSIVL signs what you have approved. It does not originate an action and cannot approve one on your behalf
Is evidence afterwardsBecause consent is a signature rather than a stored flag, what you approved and when is verifiable later: by you as well as by the Foundation
Read what you are signing

A signing prompt describes the action it authorises. Any prompt that does not match what you were doing should be rejected, and the same is true of any prompt that reaches you outside the application. SWSS will never ask you for recovery material, and no member of SWSS staff can act on your holdings on your behalf, that authority is yours and exists nowhere else. See Key Custody and Protection.

Why Identity Sits Outside the Application

IVL authenticates you and signs what you approve. It holds no balance, stakes nothing and moves nothing. Everything your holdings do is the SWSS Unified App's, exercised by you.

That division is what makes a compromise bounded: authority over your holdings does not exist in the identity layer, so it cannot be taken there. The same principle governs every boundary in the ecosystem: see SWSS Ecosystem Security.

Signing In Again

A session does not last indefinitely, and authority is confirmed on each request rather than assumed for as long as a session exists. Signing in again is the same flow as the first time and does not repeat verification: your verified status is a credential held by IVL, not a state held by the application.