Current static capability
Static wallet orientation, official-source guidance, and pre-connection safety education are available in this preview.
Wallet authentication is disabled for this environment. No wallet provider is requested and no signature is requested.
Vitality app preview
Static module workspace. Live actions remain approval-gated.
Wallet controlled preview
Review the planned wallet experience without connecting an account, requesting a signature, reading an address or balance, creating a provider, or accessing live chain data.
Static controlled preview only. No wallet connection, RPC provider, live on-chain or contract read, balance or treasury read, signature, claim, reward, staking, charging, payment, or token action is active.
Continuity path
This route remains static and safe. Use the continuity links to return to the app command surface, compare module context, and verify status before assuming any feature is active.
Wallet preview depth
This route should help users understand what the future wallet area is for, what will remain review-only, and which actions are intentionally unavailable until explicit approval.
User question
What will I be able to review here before any wallet connection is enabled?
Current preview state
Static orientation only. The screen can explain connection readiness, supported-wallet education, and safety checks without reading addresses, balances, signatures, or chain state.
Product readiness education
This is a static product sequence. It explains what exists now, why live capability remains unavailable, and what must be approved before any future activation.
Current static capability
Static wallet orientation, official-source guidance, and pre-connection safety education are available in this preview.
Why this remains unavailable
Wallet connection, address reads, balance reads, signatures, transactions, and chain state remain intentionally inactive, so no live wallet result is produced.
What must be approved next
A separately approved wallet architecture, supported-network policy, security review, and release gate must exist before any connection capability is considered.
Step 1
Available in this previewRead the static purpose, official-source, and safety guidance without connecting a wallet.
Step 2
Intentionally unavailableNo address, balance, signature, transaction, provider, or chain request is available.
Step 3
Separate approval requiredAny future wallet activation requires separately approved architecture, testing, warnings, and release controls.
Readiness state legend
No user-specific result
This sequence describes product readiness only. It does not evaluate you, your wallet, an account, eligibility, entitlement, allocation, or claim status.
No live result is produced and no personal evaluation is performed.
Orientation
Explain that the wallet area will eventually help users review connection status, token-related surfaces, and safety prompts from one controlled place.
Readiness
Show static checks for browser wallet preparation, official-source verification, and risk-language boundaries without activating a connection.
Safety
Keep the route clear that no wallet connection, signature request, balance read, transaction, or chain read is currently active.
Safe boundaries
Continue review
These links stay inside the static controlled-preview layer and do not activate wallet, claim, reward, staking, charging, payment, treasury, or token actions.
25H route continuity polish
These pathway groups help users move through the static app preview without implying any live wallet, chain, balance, treasury, claim, reward, staking, charging, payment, or token action.
Start at the dashboard, then move into the ecosystem and route status layers before reviewing preview modules.
Use contracts, treasury, and safety pages to understand the static source-of-truth boundary before any future live capability.
Review wallet, rewards, claims, and charging as inactive preview modules with informational links only.