Whitepaper

A deeper look at how Multiverse works under the hood.

Abstract

Multiverse is an instant messaging and voice/video platform for communities — servers, channels, DMs, calls — built on a conventional, reliable web2 core and layered with optional web3 features: wallet-based sign-in, NFT-gated cosmetics, an end-to-end encrypted Identity Vault, and on-chain payments for specific digital goods. It is developed and operated as a single, official platform.

A utility token for spending on platform cosmetics is planned for a future release; it does not exist today and is not for sale. Nothing in this document is an offer to sell securities, tokens, or any other financial instrument, and nothing here should be read as investment advice. Where this document describes future plans, those are forward-looking statements that may change without notice.

Vision

Crypto-native communities have largely had to choose between two unsatisfying options: a polished, reliable chat product with no meaningful concept of wallet-based identity, or a fully decentralized alternative that treats reliability, moderation, and day-to-day usability as secondary concerns. Multiverse starts from the premise that a community's chat platform doesn't have to force that tradeoff. Wallets can be a first-class identity and payment primitive without requiring full protocol decentralization, and without giving up the uptime and moderation guarantees a real community depends on.

The problem

Mainstream chat platforms treat a user's identity as an email address and a password. There's no native way to prove wallet ownership, gate a role or a cosmetic on holding a specific asset, or settle a payment on-chain — any of that has to be bolted on through bots and third-party integrations that the platform itself doesn't understand or support.

At the same time, chat and messaging systems built as genuinely decentralized protocols tend to under-invest in the parts that make a platform usable at scale: consistent uptime, responsive voice and video, spam and abuse moderation, and a client experience that doesn't require technical sophistication to use. Communities that want both — a platform that works the way they expect a modern chat app to work, and one that treats their wallet as something real — have not had a good option.

Solution overview

Multiverse is a single, professionally operated platform that treats web3 features as an optional layer on top of a conventional web2 core, not a replacement for it. Email and password authentication work exactly as they would on any mainstream platform. Servers, channels, roles, moderation tools, voice and video calls, custom emoji, and search all work the same way regardless of whether a given user or community engages with any of the wallet-based features at all.

On top of that core, users who want it can sign in with a Solana wallet instead of an email and password, unlock cosmetic profile features tied to NFTs they hold, and use a wallet-derived encryption scheme for private messages. Users can buy specific digital goods from the platform — currently vanity server URLs and metaverse land parcels — for a one-time, on-chain SOL payment. These are sold by Multiverse; the platform does not provide a way for communities to sell goods to their own members.

Architecture at a glance

Multiverse's backend is split into small, purpose-built services: a real-time gateway for message routing and presence, an API layer for the application's core domain logic, and a media/voice layer built on LiveKit for calls and screen sharing. Storage defaults to SQLite, with an optional distributed backend for larger deployments. This is standard, well-understood infrastructure — the same category of system any serious messaging product is built on — not a novel consensus protocol or a thin wrapper around a blockchain. The web3 features described below sit alongside this core as additional, optional services; they don't replace or route around it.

Web3 features in detail

Sign-In With Solana (SIWS). Users can authenticate by signing a one-time challenge with a Solana wallet (Phantom, Solflare, Backpack, Coinbase Wallet, and others) instead of using an email and password. The signature is verified server-side against the wallet's public key. A user's private key and seed phrase never leave their wallet and are never transmitted to or stored by Multiverse.

NFT-gated cosmetics. Holding a qualifying NFT can unlock cosmetic profile features — this is a cosmetic-only mechanism. It does not grant governance rights, revenue share, or any claim on Multiverse, and it is not a security.

The cosmetics system currently runs against Solana devnet: cosmetic NFTs are minted on devnet, and cosmetic purchases are verified against devnet, where SOL has no monetary value. Acquiring a cosmetic therefore does not cost real SOL today, and a devnet-minted cosmetic NFT is not a mainnet asset and has no resale value. This is deliberate while the system is being hardened, and it is independent of the land and vanity-URL flows described below, which do settle on mainnet.

Identity Vault. An end-to-end encryption scheme for direct messages in which the encryption key material is derived from a wallet signature rather than issued and held by Multiverse. Because the key is derived from something the user controls, it's portable across sessions and devices in a way a platform-issued credential wouldn't be.

On-chain payments for digital goods. Specific paid features can be purchased with a one-time, on-chain SOL payment, verified by checking the transaction on Solana mainnet. These are per-item purchases, not subscriptions and not investment products. Two exist today:

  • Custom vanity URLs for servers, at a fixed USD price converted to SOL at the time the invoice is created.
  • Land parcels in the Multiverse metaverse — a persistent, shared world in which a parcel owner can build. Parcels are minted as NFTs on mainnet, are capped in supply, and are limited to a small number per account.

Mainnet SOL has real monetary value and on-chain transactions are irreversible. Prices, supply caps, and the set of purchasable goods may change.

Bot platform

Multiverse has a public bot API, letting outside developers build and run bots on the platform in the same spirit as Discord's bot ecosystem: dedicated bot accounts, a permissions model scoped to what a bot is allowed to see and do, and a straightforward way for a community to add a bot to their server. This is a deliberate part of competing with existing chat platforms — a mainstream chat product without a real developer ecosystem around it is missing something communities already expect.

Available today, with no approval process or waitlist: self-serve applications, individually revocable named bot tokens, developer teams, a first-party TypeScript SDK, global slash commands, and a developer portal in the client. The first bot built on the platform is I.R.I.S. (Integrated Robotic Intelligence System), an assistant used during Multiverse's early development.

The platform is early and still moving. Message components and modals are not implemented, there is no sharding surface, and event subscriptions and bot-specific rate-limit tiers are still being designed — so bots written against it should expect additive change. The developer documentation is the authoritative, current statement of what is and isn't supported; this document is not.

Token plans

Multiverse plans to introduce a utility token, issued as a standard SPL token on Solana, in a future release. Its intended use is narrow: spending it on cosmetic items on the platform. Users would be able to acquire it either by purchasing it directly — in SOL or fiat — or by earning modest amounts through ordinary use of the platform; neither mechanism is live today.

The token does not exist yet. It is not available for purchase or exchange anywhere, there is no sale, distribution event, or timeline to announce, and nothing in this document is an offer to sell or a solicitation to buy the token or any other instrument. If and when it launches, it is intended solely as a means of paying for cosmetics — not as an investment, and not as a promise of profit, dividend, revenue share, or governance rights in Multiverse. The design, mechanics, and timing described here may change, or the token may not ship at all.

Operating model

There is only one instance of Multiverse, developed and operated as a single, canonical service. This is closer to how Solana Labs stewards the Solana network, or how Google operates YouTube, than to a protocol anyone can independently stand up. Multiverse does not offer, document, or support running an independent deployment of the platform.

Why the code is public

Multiverse's source code is public on GitHub, licensed under the AGPLv3, with a contributor license agreement (CLA) for external contributions. This is a deliberate choice aimed at a community that is — reasonably — skeptical of new platforms it can't inspect: publishing the code lets outside developers and security researchers read exactly what the platform does, verify claims about how the Identity Vault and wallet authentication work, and contribute directly.

Publishing the code is not an invitation to run a separate, independent copy of Multiverse. Source availability and open contribution are about transparency and trust, not about deployment rights.

Trust, security, and moderation

Multiverse runs a public responsible-disclosure program for security researchers, described in full at /security. Wallet authentication is non-custodial: Multiverse never holds a user's private keys or seed phrase, only a verified public key and signature. Like any platform that hosts user-generated content and media, Multiverse maintains standard content-moderation and legal-compliance infrastructure, including CSAM detection and reporting obligations.

Roadmap

Near-term priorities include native mobile apps, exploratory work on federation between Multiverse communities, expanding the range of cosmetic categories that can be gated by NFT ownership, and building out the metaverse world around the land described above. On the payments side, the set of digital goods that can be purchased on-chain may grow over time, and moving the cosmetics system from devnet onto mainnet is a prerequisite for cosmetics ever costing real SOL. Further out, we plan to introduce the utility token described above. These are directional statements about where the product is headed, not commitments to specific dates or features — they may change as the platform develops.

  • Multiverse has no token today. A utility token is planned for a future release, as described above; nothing in this document is an offer or solicitation to buy or sell securities, tokens, or any other financial instrument.
  • Nothing in this document is investment, legal, or financial advice.
  • Statements about future plans, features, or roadmap items are forward-looking and may change without notice, including whether, when, and how the planned utility token ships.
  • The Identity Vault, NFT-gating mechanism, and on-chain payment flow described here have not been independently audited as of the publication of this document.
  • Payments made in SOL carry the ordinary risks of cryptocurrency: price volatility and transaction irreversibility. Users are responsible for the security of their own wallets.
  • If and when the planned utility token launches, it will not confer profit-sharing, dividends, revenue share, equity, or governance rights in Multiverse, and its price, if any, is not guaranteed or controlled by Multiverse.
  • Company information is available at /company-information. Where anything in this document conflicts with the Terms of Service or Privacy Policy, those documents govern.

Learn more

Choose your language

All translations are currently LLM-generated with minimal human revision. We'd love to get real people to help us localize Multiverse into your language. To do so, email doommedia@proton.me and we'll be happy to accept your contributions.