Route structure
Public, auth, user, and admin routes are separated so teams can reason about access boundaries.
Dev Portal
Developer notes for wallet builders
Understand the application areas that support accounts, coins, wallet actions, staking, swaps, notifications, and admin operations.
Routes
Services
Views
Overview
Designed around clear decisions
Service classes
Crypto and user-coin services centralize common asset and wallet behavior.
Blade views
User and admin screens are split into focused Blade files for easier maintenance.
Workflow
Move from interest to action
Each public page gives visitors enough context to understand the feature, then sends account-specific actions into authenticated wallet areas.
1
Explore
Start with a focused overview that explains what the page helps users do.
2
Review
Compare the important details before opening an account flow or taking a wallet action.
3
Continue
Move into login or registration when the next step requires an authenticated wallet area.
Do I need an account to continue?
You can browse public pages freely. Wallet actions, account settings, and transaction tools require login.
Can I manage multiple assets?
Yes. The wallet area is built around multi-asset visibility, supported coin pages, and guided transaction flows.