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
Claim controlled preview
Claim access remains preview-only.
Review the planned claim pathway without wallet connection, eligibility lookup, allocation lookup, contract execution, signatures, transactions, distributions, or token movement.
What happens next
Use this route to understand the steps and safety information a future approved claim flow would require.
No campaign, eligibility result, allocation, claim button, signature request, transaction, or distribution is active.
Continue to airdrop readiness for related static preparation and boundary information.
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.
Claim preview depth
Keep claim education clearly inactive and review-only
This route should prepare the future claim experience without exposing any claim button, entitlement result, eligibility read, wallet read, or token action.
User question
What would a future claim flow need to explain before any action exists?
Current preview state
Static claim education only. The route can explain future review stages, safety requirements, and approval gates while keeping all claim actions unavailable.
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 claim education can describe a future review sequence, official-source checks, and safety boundaries.
Why this remains unavailable
No campaign, wallet lookup, allocation lookup, proof check, claim status, signature, transaction, or token movement is connected.
What must be approved next
An approved campaign policy, verified data source, secure claim architecture, independent validation, and release approval must exist first.
Step 1
Available in this previewReview the future sequence
Understand the proposed verification, review, safety, and final-action stages without activating them.
Step 2
Intentionally unavailableKeep claim results inactive
No eligibility, allocation, entitlement, claimable amount, proof, or transaction result is produced.
Step 3
Separate approval requiredRequire a separate release gate
Any future claim capability requires approved policy, data, contracts, security evidence, and release controls.
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.
Future flow
Claim review stages
Outline a future sequence such as source verification, eligibility review, safety confirmation, and final action gate without enabling any step.
Status
No claim state
Avoid displaying pending, approved, rejected, claimable, available, or countdown states until a real approved backend and policy gate exists.
Safety
No token movement
Keep this route free of claim buttons, transaction prompts, signatures, wallet reads, balances, or token transfer logic.
Safe boundaries
- - No claim action is active.
- - No claim eligibility lookup is active.
- - No claimable amount is displayed.
- - No token movement 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.