Run LiteVerse across dashboard, browser, mobile, and CLI.
LiteVerse gives one account a consistent way to manage nodes, services, rewards, and live activity. These docs explain the public network model, the signed-in dashboard, and each node surface.
Choose the guide that matches what you want to run.
Begin with the overview, then move into the dashboard, browser node, mobile node, CLI node, or integration pages.
Getting started
Create or open a LiteVerse account, choose the first node, and confirm the live setup.
GuideDashboard
Manage account state, linked nodes, rewards, history, settings, and pairing.
GuideBrowser node
Start LiteVerse from a browser with guest access, account sign-in, controls, and logs.
GuideMobile node
Run the Android node with native sign-in, device readings, and account sync.
GuideCLI node
Operate LiteVerse from Windows, macOS, Linux, servers, or VPS environments.
GuideSDKs, widgets, examples
Use the repository packages and examples that mirror the live product model.
One account controls private nodes and reads public network state.
LiteVerse is the account and node control layer. InterLayer is the first live service in Testnet Alpha, and InterClaw is the next listed service.
What LiteVerse connects
Where data comes from
A clean setup uses one account and then adds devices.
Basic flow
Open the dashboard or browser node.
The dashboard is best for account control. The browser node is the fastest live start.
Sign in with Google, email/password, wallet, or guest mode where available.
Use the same account method wherever possible so sessions stay connected.
Pair mobile or CLI from the same account.
Pairing keeps extra devices under the same LiteVerse account.
Use logs, rewards, and node state to confirm sync.
Live screens confirm whether the node is running, paused, syncing, or disconnected.