Wallet PreviewPreview
Wallet optionsPreview only
ZKX Wallet

Featured future Vitality wallet option

Future
Rabby

Future browser wallet pathway

Future
Internet Wallet

Future PulseChain wallet pathway

Future
WalletConnect

Future multi-wallet pathway

Staged
Future supported options

Additional wallet pathways require separate approval

Future

Wallet access pending, provider modal, signature request, address read, balance read, chain read, or transaction path is active in this preview.

Vitality Command Layer

Vitality App dashboard

StagingPreviewPreview modeApp roadmap‑B
Official source

Vitality app preview

Preview modeOfficial site

Contract guidance

Contract information remains static and verification-led.

This route explains where official contract guidance will live without reading chain data, connecting wallets, or performing token actions.

Static guidance

What happens next

Official contract references should remain controlled, reviewed, and easy to verify.
No contract read, token interaction, wallet connection, or transaction path is active.
Users should cross-check official sources before taking any external action.

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.

Static continuity

Static source-of-truth layer

Official contract records, without live reads or wallet actions.

These records make the contract route clearer before any future live registry work. They are static app records only and do not activate wallet connections, chain reads, balances, treasury reads, claims, rewards, staking, charging, payments, approvals, or token actions.

Records

6

Live reads

0

Live config

0

PulseChain mainnet · Chain ID 369

VTY Token

Static reference
Static address / reference
0x3c650A6C6fd6CE29225364529425C188025Db625
Review state
Needs operator final verification
Source basis
  • · Existing static app registry inventory
  • · Existing public dashboard registry inventory
  • · Operator source-of-truth review required before live-read configuration
Live reads: DisabledWallet: Not requiredTransactions: Unavailable

Static token contract record only. This does not activate contract reads, balances, approvals, transfers, claims, rewards, staking, charging, or payments.

PulseChain mainnet · Chain ID 369

VTY / pDAI pair

Static reference
Static address / reference
0x8808a2Ae5c8B35990e32632585150436C6589B8f
Review state
Needs operator final verification
Source basis
  • · Existing static market reference inventory
  • · Existing public dashboard registry inventory
  • · Operator source-of-truth review required before live market data approval
Live reads: DisabledWallet: Not requiredTransactions: Unavailable

Static pair record only. This does not activate pool reads, prices, quotes, market feeds, routing, trading, LP actions, or financial advice.

Future architecture · Not active

VitalityClaimRouter

Pending official activation
Static address / reference
No public address in this static record
Review state
Source scaffold
Source basis
  • · Future claim module label from static official contract metadata
  • · Requires official deployment record before public address display
Live reads: DisabledWallet: Not requiredTransactions: Unavailable

Future module placeholder only. No eligibility lookup, proof generation, claim window, approval, or transaction is active.

Future architecture · Not active

VitalityDistributor

Pending official activation
Static address / reference
No public address in this static record
Review state
Source scaffold
Source basis
  • · Future distributor module label from static official contract metadata
  • · Requires official deployment record before public address display
Live reads: DisabledWallet: Not requiredTransactions: Unavailable

Future module placeholder only. No reward calculation, entitlement, distribution, approval, transfer, APY, or yield display is active.

Policy record · Not a live chain read

TreasuryVaultT1 policy record

Policy only
Static address / reference
No public address in this static record
Review state
Source scaffold
Source basis
  • · Static treasury policy label from official contract metadata
  • · Requires custody, accounting, legal, and public wording review before any read-only transparency work
Live reads: DisabledWallet: Not requiredTransactions: Unavailable

Policy record only. No treasury wallet read, balance display, NAV, backing, redemption, price-support, or value calculation is active.

Policy record · Not a live chain read

TreasuryVaultT2 policy record

Policy only
Static address / reference
No public address in this static record
Review state
Source scaffold
Source basis
  • · Static treasury policy label from official contract metadata
  • · Requires custody, accounting, legal, and public wording review before any read-only transparency work
Live reads: DisabledWallet: Not requiredTransactions: Unavailable

Policy record only. No treasury wallet read, reserve value, NAV, backing, redemption, price-support, or value calculation is active.

Activation boundary: Official contract source-of-truth records are static app records only. They do not configure live-read addresses, providers, wallets, endpoints, balances, treasury reads, or token actions.

Contracts depth

Keep official contract education clear before live interaction

This route explains how users can review official contract information and safety boundaries without enabling contract reads, wallet connections, signatures, token approvals, or transactions.

User question

How should users treat contract information before any live interaction is enabled?

Current preview state

Static education only. Contract references support trust, review, and official-source discipline while no contract read, wallet connection, token approval, or transaction path is active.

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 official-contract education can help users identify approved references and understand verification boundaries.

Why this remains unavailable

No provider, RPC endpoint, executable contract read, wallet interaction, approval, signature, or transaction is connected.

What must be approved next

Approved provider architecture, network policy, contract source-of-truth controls, independent testing, and security review must exist first.

  1. Step 1

    Available in this preview

    Review official references

    Use the static contract source-of-truth information and verification guidance without executing a read.

  2. Step 2

    Intentionally unavailable

    Keep contract execution inactive

    No RPC, provider, contract call, approval, signature, transaction, or token action is available.

  3. Step 3

    Separate approval required

    Approve future read architecture

    Any executable read capability requires approved providers, allowlists, error handling, security testing, 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.

Official source

Contract reference discipline

Frame contract information as official-source guidance users can verify before any future live contract interaction exists.

Readiness

Interaction gates

Clarify that future live contract features require explicit approval gates, visible warnings, and separate technical validation.

Safety

No transaction path

Keep wallet connection, signature, approval, claim, staking, charging, and token movement actions unavailable.

Safe boundaries

  • - No contract read is active.
  • - No wallet connection is active.
  • - No signature or transaction path is active.
  • - No token approval or token movement is active.

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

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.

Trust route

Use contracts, treasury, and safety pages to understand the static source-of-truth boundary before any future live capability.

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.