ZKX Wallet
FutureFeatured future Vitality wallet option
Wallet PreviewPreview
Wallet optionsPreview only
Rabby
FutureFuture browser wallet pathway
Internet Wallet
FutureFuture PulseChain wallet pathway
WalletConnect
StagedFuture multi-wallet pathway
Future supported options
FutureAdditional wallet pathways require separate approval
Wallet access pending, provider modal, signature request, address read, balance read, chain read, or transaction path is active in this preview.
Vitality app preview
Static module workspace. Live actions remain approval-gated.
Preview modeOfficial site
Roadmap
The roadmap is a controlled delivery guide.
This route frames staged product progress without promising activation dates, outcomes, token actions, or live infrastructure.
What happens next
Upcoming work should remain grouped by safe frontend, data, infrastructure, and activation gates.
Any wallet, claim, staking, charging, or contract work requires a separate approval gate.
Roadmap copy should explain progress without creating activation assumptions.
Safety boundary
This page is static education only. It does not activate live infrastructure or user actions.
No wallet connectionNo signaturesNo on-chain readsNo balance readsNo treasury readsNo live price or Dexscreener integrationNo claims or rewards activationNo staking or charging activationNo payments or token actions
Continuity path
Keep moving through verified preview routes.
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.
Roadmap depth
Present progress as staged delivery, not promises
This route helps users understand staged development priorities, approval gates, and preview milestones while avoiding guaranteed delivery, launch promises, token outcome claims, or financial expectations.
User question
What does the roadmap explain before features are activated?
Current preview state
Static roadmap education only. The route can communicate sequencing, review gates, and future product areas while no timeline guarantee, feature promise, token outcome, or activation commitment is made.
Product readiness education
Preview journey
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 roadmap education can communicate sequencing, controlled-preview status, review gates, and future product areas.
Why this remains unavailable
The roadmap does not activate features, guarantee delivery dates, promise outcomes, or provide live implementation monitoring.
What must be approved next
Each future capability must complete its own design, security, validation, governance, release, and production approval gates.
Step 1
Available in this previewReview staged delivery
Use the roadmap to distinguish controlled preview, active build, planned work, and intentionally inactive capability.
Step 2
Intentionally unavailableSeparate planning from activation
A roadmap entry does not create a live feature, deadline guarantee, entitlement, or product outcome.
Step 3
Separate approval requiredComplete feature-specific gates
Every future capability requires its own approved scope, implementation, validation, release, and production decision.
Readiness state legend
- Available in this preview
- Static educational information is available. It does not use account, wallet, transaction, or live data.
- Future capability required
- This step depends on product infrastructure that has not yet been built or connected.
- Intentionally unavailable
- This capability remains inactive in the controlled preview.
- Separate approval required
- This capability can only be considered after a separate security, governance, and release approval.
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.
Sequence
Controlled delivery stages
Explain that development moves through preview, validation, approval, launch-readiness, and activation gates.
Clarity
What is not live
Use roadmap depth to distinguish future intent from active functionality across wallet, rewards, claims, charging, treasury, and contracts.
Trust
No delivery guarantee
Avoid dates, guaranteed launches, token outcome claims, or financial expectations unless separately approved.
Safe boundaries
- - No launch date or delivery guarantee is displayed.
- - No token outcome promise is displayed.
- - No financial expectation is displayed.
- - No feature activation is implied.
Continue review
WalletRewardsClaimsProfileRewards/ChargingCharging PositionsAirdropActivityContractsTreasuryEcosystemEcosystem NetworkRoadmapHoldersLiquiditySafetyStatus
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
Follow the controlled-preview pathway
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.
Command route
Start at the dashboard, then move into the ecosystem and route status layers before reviewing preview modules.
Trust route
Use contracts, treasury, and safety pages to understand the static source-of-truth boundary before any future live capability.
Preview route
Review wallet, rewards, claims, and charging as inactive preview modules with informational links only.
Controlled-preview boundary remains unchanged: no wallet connection, no on-chain reads, no contract read execution, no signatures, no balance reads, no treasury reads, and no claims, rewards, staking, charging, payments, token actions, or live data feeds.