Moss Book
What Moss Is
Moss gives the user a Runtime first, then brings apps into that environment.
What Moss Is
From a user perspective, Moss is not about jumping between many separate dApps. It gives you a Moss Wallet first, then lets apps enter that wallet environment.
The most important thing in Moss is not one isolated page. It is the Runtime itself. You connect your existing wallet, create a Moss Wallet, install apps from Store, and then continue using them inside the Runtime.
That means apps are not treated as external websites first. They become part of what the account can do. Assets, permissions, payments, and app entry points all sit around the same account context.
That matters because Web3 has not really lacked more entry points. It has lacked a continuous, stateful user environment.
Moss Runtime
The app runtime. Wallet, assets, apps, and settings all start here.
Store
The place where apps are discovered, installed, and brought back into the wallet.
Product Loop
Connect a wallet and create a Moss Wallet
Users start from an existing wallet, then create a Moss Wallet as the runtime environment.
Install an app in Store
Users discover an app in Store and bind that installation to the current account.
Return to the Runtime
The installed app appears back inside the Runtime instead of staying in the store page.
Keep using the same Runtime
Assets, permissions, payments, and app entry points continue accumulating inside the same Moss Wallet.
The key reading
Moss is not about stuffing more web links into a wallet. It is about building an account environment that can install apps and keep growing over time.
Core Concepts
- Moss Wallet: the smart wallet you actually use inside Moss.
- Moss Runtime: the app runtime. You enter the shared runtime first, not a standalone dApp first.
- Store: the discovery and installation surface for apps.
- Install: the state that binds an app to your account.
- Enable: the wallet-side step that makes an installed app actually usable.