Documentation
Quick start
Use the browser, claim a handle, and check publishing options.
Before you start
Use Sideverse in a current desktop or mobile browser. You do not need a native app to use communities, events, shared-cost records, or profile blocks.
Open Sign in if you already have an account. New entry depends on this registry's admission settings. When invitations are required, use your invitation and complete the steps shown. Email verification and password-reset email need a working mail provider.
1. Claim your handle
In the workspace, select the Side that will own the name, then open Claim a handle. The browser service holds that Side's encrypted signing key and signs the claim. A compatible external client can instead submit its own signed claim through the API.
Handles use lowercase letters, digits, and hyphens, with up to 64 characters. A handle cannot start or end with a hyphen. Reserved and already claimed names are unavailable.
ok @alice
ok @cafe-de-flore
bad @CafeDeFlore (uppercase)
bad @-alice (leading hyphen)
bad @alice- (trailing hyphen)
A handle belongs to one Side. Check the displayed Side before you claim it.
2. Use your workspace
- Discover: find events and communities available to the selected Side.
- Communities: open your rooms, read the membership terms, and manage the information you share in each community.
- Events: create or open an event, answer its invitation, view photos, and record shared costs when you have access.
- Your Sides: manage separate identities under your account.
- Account settings: review security, sessions, exports, and account details.
To change your public profile, open a handle and choose Edit blocks. Saved blocks appear on that profile. These profile blocks are separate from signed page publications.
3. Publish a signed page
Signed page publishing uses a compatible client or the API. There is no browser composer for signed page bundles in this release.
The publisher needs the signing key for the handle and must create the
wire format described in the API reference. A successful
publication has a public address at /{handle}/{slug}. Publishing again
under the same handle and slug replaces the stored version.
Browser Sides and externally held keys have different custody. Do not assume that an external client can use a browser Side's hosted key.
4. Check native availability
Desktop and mobile apps are not available yet. Use Sideverse in the browser. Device sign-in is an optional path for compatible clients; ordinary browser sign-in remains available.
What's next
- Protocol — names, signed pages, and verification.
- API reference — request and response formats.
- FAQ — key custody and publishing limits.