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
Profile controlled preview
Profile setup remains preview-only.
Review the planned account and preference experience without authentication changes, identity verification, personal-data collection, wallet access, live activity reads, or account mutations.
What happens next
Use this route to understand future profile, preference, progress, and readiness concepts.
No profile write, identity check, wallet read, signature, live activity lookup, or personal-data submission is active.
Continue to wallet preview for the related static account-access pathway.
Safety boundary
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.
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.
Profile preview depth
Define profile value before authentication or wallet identity
This route should explain the future profile layer as user orientation, preferences, and readiness context without activating login, wallet identity, or personal data flows.
User question
What will the profile area help users understand before personalisation is enabled?
Current preview state
Static profile orientation only. The route can explain future profile modules, preferences, activity summaries, and privacy expectations without authentication or wallet identity.
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 profile orientation can explain future preferences, privacy expectations, activity context, and connected product areas.
Why this remains unavailable
Authentication, account creation, wallet identity, personal data collection, preference storage, and profile writes remain inactive.
What must be approved next
Approved identity, consent, privacy, data-retention, authentication, security, and account-recovery designs must exist before personalisation.
Step 1
Available in this previewReview profile purpose
Understand the future profile modules and privacy expectations without creating an account.
Step 2
Intentionally unavailableKeep personal data inactive
No identity, preference, wallet, account, or activity information is collected or stored.
Step 3
Future capability requiredApprove identity and privacy controls
Future personalisation depends on approved consent, authentication, privacy, storage, and recovery infrastructure.
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.
Identity
Future user profile layer
Describe the profile as a future place for preferences, app readiness, activity context, and safety settings once approved identity flows exist.
Privacy
No personal data collection
Make clear that the preview does not collect personal data, create accounts, connect wallets, or store user preferences.
Continuity
Route-to-route context
Connect the profile preview to wallet, rewards, claims, and activity routes as future context surfaces without implying live personalisation.
Safe boundaries
- - No authentication is active.
- - No wallet identity is active.
- - No personal data collection is active.
- - No profile write or preference save is active.
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.