PVERSE
REFERENCE

FAQ

Short answers to common questions. If an answer needs depth, it points to the canonical page instead of duplicating the full rulebook.

Published: February 17, 2026
Updated: March 24, 2026
Section: REFERENCE
FAQ rule
Each answer stays short and points to the canonical doc when more depth is needed. FAQ is a clarification surface, not a second manual.

How should I use this FAQ?

Use it to remove misunderstandings quickly. If you want the full rules, exact policy, or implementation detail, follow the links to canonical pages. This keeps Docs consistent, searchable, and forward-only.

Reference Overview Starter Index Index (By Topic) Definitions Status (Snapshot) Changelog Index

Reading order

What is the fastest way to understand PVERSE?
  1. Start Here for the shortest onboarding path
  2. Docs Overview for the docs structure
  3. Docs Map for the full navigation tree
  4. Definitions for shared vocabulary
  5. Status for live or snapshot signals, not canonical rules
Where do the real rules live?
Canonical rules live in primary documentation lanes such as Whitepaper, Foundation, Infrastructure, Game Systems, Token, Market, Affiliate, and Security. Status pages show measurements or snapshots, not rule authority. Use Definitions when a term affects behavior.
What is the difference between Docs and Status?
Docs define intended system behavior. Status shows what the platform currently reports or has observed. If there is a mismatch, Docs and SSOT describe intended truth, while Status is operational evidence to investigate. See Status (Snapshot).

Docs structure and boundaries

What is REFERENCE for?
REFERENCE is the map: entry points, indexes, definitions, snapshots, and changelog pointers. It helps you find the canonical page faster. Start at Reference Overview.
What is the difference between Definitions and Glossary?
Definitions are normative and precise. Glossary is navigational and may include aliases, shorthand, or likely synonyms. If a term changes system behavior, it belongs in Definitions.
What does forward-only mean in Docs?
It means we avoid retroactive rewriting that changes historical meaning. Changes are published as changes through snapshots, changelog entries, and versioned policy updates. See Docs Changelog.
Is everything in Docs immutable?
No. Documentation can evolve, but changes should be attributable and auditable. Canonical links should remain stable where possible, and historical assumptions should be preserved through forward-only publishing.

SSOT and determinism

What is SSOT and why does it matter?
SSOT means Single Source of Truth. It is the authoritative configuration layer for rules, rates, thresholds, pricing snapshots, eligibility boundaries, and distributions. Docs describe the contract; SSOT is the executable truth.
Can SSOT change after users rely on it?
SSOT can evolve, but changes should be versioned, announced, and applied forward-only. The platform should not silently rewrite prior economic meaning or historical snapshots.
Where do pricing snapshots belong?
Pricing snapshots belong in infrastructure and service-behavior documentation because they describe how value was locked, when, and by which source. They are not just marketing text or general status decoration.

Participation and programs

What is the difference between Genesis and Founders?
They are distinct participation categories with different allocation rules, timing, and lifecycle constraints. Use the canonical participation and policy pages for exact interpretation.
Can I trade immediately after participation?
Not necessarily. Market activation is policy-driven and may use explicit manual enable steps or staged activation. Participation is not a promise of immediate liquidity unless canonical rules say so.
What does credit applied mean?
It means the system recognized value and applied it to the correct accounting bucket. It does not automatically mean tradable, withdrawable, or freely transferable unless the relevant program rules explicitly say that it is.

Affiliate and partner program

What is the Affiliate lane for?
Affiliate is the canonical home for referral codes, attribution, commission logic, settlements, withdrawals, campaigns, partner policies, leaderboard logic, and anti-abuse controls. Start at Affiliate Overview.
Does a referral click guarantee commission?
No. A click is not the same as attribution, and attribution is not the same as a settled commission. Commission depends on the documented attribution and settlement rules. See Attribution and Commission Model.
When does affiliate value become withdrawable?
Not at click time and not necessarily at raw attribution time. Withdrawability depends on the settlement state, withdrawal rules, thresholds, and the canonical payout policy. See Settlements and Withdrawals.
Can affiliate rules change retroactively?
Canonical affiliate rules should follow the same forward-only publishing discipline as the rest of the docs. Changes may affect future flows, but should not silently rewrite already-settled historical meaning.

Infrastructure and safety

Do I need an account to use PVERSE?
Many flows are wallet-based. If an account layer exists, it is usually a convenience or access layer rather than a replacement for deterministic ownership evidence. See Account Recovery.
How does the platform handle outages or partial failures?
Systems are expected to degrade safely: queue, retry with backoff, preserve evidence, and avoid double-apply. Operators rely on explicit runbooks. See Operations Runbooks.
What prevents double counting of deposits or events?
Idempotency keys, forward-only ledgers, deterministic status transitions, and replay-safe application rules help prevent duplicate credit. If a reorg or duplicate event appears, the system reconciles without double-apply.
Is there observability?
Yes. Structured logs, metrics, and traceability across request, commit, chain evidence, and settlement are required for reliability. See Observability.
What are reliability limits?
Reliability limits are explicit boundaries around finality assumptions, provider behavior, rate limits, operational constraints, and known non-guarantees. See Reliability Limits.
How do updates get shipped without breaking users?
By keeping interfaces stable where possible, publishing changes, and rolling out forward-only policy updates with safe defaults and changelog visibility. See Changelog.

Security and privacy

Does PVERSE store private keys?
No. Wallet private keys are not stored by PVERSE. If an account system exists, it should not replace wallet-side control with centralized secret custody.
Can support recover funds for me?
Recovery depends on the documented recovery policy and what the platform actually controls. Most on-chain assets remain controlled by the user wallet unless canonical rules state otherwise.
Does the platform guarantee privacy or anonymity?
The platform can minimize data collection, but on-chain activity is public by nature. Stronger claims should be described carefully in terms of data minimization, scope, and explicit system boundaries.

Support and troubleshooting

I am stuck. Where should I look first?
  1. Check Status for outages or degraded systems.
  2. Use Index (By Topic) to find the right lane.
  3. Confirm the exact terms in Definitions.
  4. If the issue is operational, read Runbooks.
Can FAQ include very long answers?
No. If an answer needs real depth, it belongs on a dedicated canonical page. FAQ should stay compact and link out.
How should a new FAQ item be added?
Add it only if the question repeats and is causing confusion. If it is really a how-to or a policy explanation, create or update the canonical doc first and then add a short FAQ entry that links to it.
Maintenance
Keep FAQ compact. Prefer links to canonical docs. If a question becomes obsolete, remove it here and maintain the canonical doc instead.