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
Safety centre
Safety boundaries come before activation.
This route gives users a clear safety-first orientation before any wallet, claim, reward, staking, charging, or token functionality is considered.
What happens next
Users should never paste seed phrases, private keys, API keys, or credentials into the app.
Any live wallet or transaction feature must include explicit user-safety copy and approval gates.
Current app routes remain static education and navigation surfaces.
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.
Safety depth
Make safety boundaries visible before activation
This route should make controlled-preview boundaries easier to understand across wallet, contracts, treasury, claims, rewards, charging, staking, payments, and token actions.
User question
What safety boundaries apply before features are activated?
Current preview state
Static safety education only. The route can explain what is inactive, what needs approval, and how future activation should be reviewed without enabling any live action.
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 safety education can explain inactive capabilities, approval gates, source verification, and user-protection expectations.
Why this remains unavailable
The safety route does not monitor a wallet, inspect an account, scan transactions, provide automated protection, or guarantee security.
What must be approved next
Any future monitoring or protective service requires approved data access, threat models, privacy controls, operational ownership, testing, and release approval.
Step 1
Available in this previewReview current boundaries
Use the safety route to confirm which capabilities remain inactive and which approvals would be required later.
Step 2
Intentionally unavailableKeep automated monitoring inactive
No wallet, account, transaction, threat, incident, or live-security monitoring is connected.
Step 3
Future capability requiredApprove future protective services
Future monitoring requires defined threat models, consent, privacy, data controls, operations, testing, and release governance.
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.
Boundary
Inactive by default
Clarify that preview pages are static unless a future sprint explicitly activates a feature through approved gates.
Review
Approval before activation
State that wallet, contract, treasury, reward, claim, charging, staking, payment, and token actions require separate review.
Trust
Plain-language warnings
Keep user-facing safety copy direct, visible, and repeated near any future activation surface.
Safe boundaries
- - No wallet connection is active.
- - No contract or treasury read is active.
- - No claim, reward, staking, or charging action is active.
- - No payment or token action 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.