globe-pointerSPassport

Overview

SPassport is the digital identity and entry layer of the Sverse ecosystem.

It provides users with a single, persistent identity that allows them to access experiences, own digital assets, and carry their history and reputation across the platform.

SPassport is currently delivered as a Telegram Mini App, optimized for frictionless onboarding and social distribution.

This document follows the buildos.work product development framework:

Vision → Value → User → Use Case → MVP Boundary


1. Vision

A digital ecosystem can only function at scale when identity is unified, portable, and independent of individual applications.

SPassport is not a wallet and not a game account.

It is a digital passport that represents who a user is inside Sverse, regardless of which experience they enter.

Its purpose is to eliminate identity fragmentation and allow users to move freely across the ecosystem without rebuilding their presence each time.


2. Product Role in the Ecosystem

Dimension
Role of SPassport

Identity

Unified user identity

Entry

Primary onboarding gateway

Ownership

Visibility of owned digital assets

Continuity

Persistence across experiences

Growth

Social and referral-based onboarding


3. Target Users

User Type
Description

New Users

First-time participants entering Sverse

Players

Users accessing games or experiences

Casual Creators

Early-stage or non-technical creators

Community Members

Participants engaging without building products


4. Identity Scope

Layer
Capability Provided

Identity

Sverse ID, basic profile

Assets

Read-only view of owned assets

Reputation

Level, badges, activity history

Access

Entry points to supported experiences

Social

Referral and community linkage


5. Core Values and User Cases

Value 1: Unified Digital Identity

Users should not need to recreate themselves for every application or experience.

User Cases

  • Log in once using Telegram

  • Retain the same identity across all Sverse experiences

  • Avoid multiple accounts and fragmented progress


Value 2: Portable Asset Ownership

Assets belong to users, not to individual experiences.

User Cases

  • View all owned assets in one place

  • Carry assets between supported experiences

  • Understand ownership independently from usage


Value 3: Visible Progress and Reputation

Users need to understand who they are becoming inside the ecosystem.

User Cases

  • View Sverse level and achievements

  • Track participation history

  • Receive status indicators or recognition


Value 4: Instant Access to Experiences

Entry into value should be immediate and intuitive.

User Cases

  • Launch experiences directly from SPassport

  • Receive recommendations based on owned assets

  • Join events with minimal interaction


Value 5: Social and Viral Onboarding

Identity should naturally extend into social networks.

User Cases

  • Invite others through Telegram

  • Participate in referral programs

  • Connect to ecosystem communities


6. Core Data Domains

Domain
Primary Data

Identity

Sverse ID, profile

Assets

Ownership references

Reputation

Levels, badges, activity logs

Access

Experience permissions

Social

Referral relationships


7. MVP Boundary

SPassport MVP = Identity + Asset Visibility + Entry

Included

  • Telegram Mini App implementation

  • Automatic Sverse ID generation

  • Basic user profile

  • Owned asset overview

  • Experience entry links

Explicitly Excluded

  • Advanced crypto wallet functionality

  • Marketplace transactions

  • Creator tooling

  • Governance or voting features


8. Success Signals

Metric
Meaning

Activated Users

Users completing SPassport setup

Return Rate

Users revisiting SPassport

Experience Launches

Entries into experiences

Asset Visibility

Users owning at least one asset


9. SPassport in One Sentence

SPassport is the digital identity users carry across Sverse—where they begin, return, and retain everything they own.

Last updated