Market Architecture
Structural layers, execution flow, liquidity interfaces, and control boundaries that define how the PVR market operates.
Overview
Market Architecture defines the structural layers that enable PVR trading across public venues. It explains how trades reach the market, how liquidity is referenced, how execution settles, and how explicit controls gate whether execution is allowed.
The goal is to separate what the market is from what the market policy is. Architecture describes components and flow. Policy describes what is permitted, when markets are open, and how operator-controlled constraints behave.
Scope
This page explains the structural model of the market without collapsing it into token policy or treasury logic.
- How PVR trades flow through wallets, routers, pools, and settlement.
- How liquidity surfaces express depth and price.
- Where control gates intervene in execution.
- Which boundaries separate architecture from tokenomics and game systems.
Core Model
The PVR market is organized as four layers. Each layer has a distinct responsibility and should not be mistaken for another. This separation makes execution easier to reason about and reduces confusion between market mechanics and policy meaning.
- Token Layer: the PVR contract defines transfer behavior, taxes, and transfer-side checks.
- Liquidity Layer: pools and reserves create price expression and available depth.
- Execution Layer: wallets, routers, and routing paths perform swaps and settlement.
- Control Layer: explicit state flags and constraints determine whether execution is allowed and under which conditions.
Layer breakdown
- Token Layer — PVR contract behavior, including transfers, taxes, and restrictions.
- Liquidity Layer — pools and reserves that form price and depth.
- Execution Layer — routing, swapping, and settlement.
- Control Layer — state flags and constraints that gate execution.
Operational Behavior
In a typical DEX flow, a user signs a transaction from a wallet, a router selects a pool or route, and settlement occurs against live liquidity. During settlement, the PVR contract applies any transfer-side checks or tax logic that are in force. If a control condition fails, the transaction reverts rather than partially completing in an AMM context.
Price is not set by the protocol. It emerges from reserve ratios, liquidity depth, arbitrage, and external order flow. That means the protocol can regulate transfer behavior and execution gates, but it cannot decree a live market price. Execution quality is therefore sensitive to slippage settings, pool depth, and real-time ordering pressure such as MEV.
User Wallet ↓ DEX Router ↓ Liquidity Pool / Route ↓ PVR Token Settlement ↓ Final On-Chain Balances
Constraints
- No assumption that the token contract determines market price; price is a market output of liquidity and flow.
- No assumption that liquidity guarantees stability, profitability, or successful execution under all conditions.
- No inclusion of allocation math, vesting administration, subscription mechanics, or gameplay systems as part of market architecture.
- No implication that controls create liquidity or demand; they only gate or shape execution conditions.
Integrity Considerations
Market architecture is only useful when the roles of each layer stay clean. Confusion begins when execution is mistaken for policy, liquidity is mistaken for a promise, or token-side checks are mistaken for price control.
- Boundary clarity: architecture explains components and flow, while market policy explains permissions, states, and declared constraints.
- Execution realism: slippage, price impact, and MEV are normal market realities and should be treated as such.
- Control explicitness: state gates should be visible, minimal, and tied to declared operational posture rather than hidden behavior.
Future Expansion
As the market matures, this architecture can expand toward additional venues, richer routing, more detailed execution analytics, or broader market-infrastructure documentation. Any expansion should preserve the same core discipline: token behavior, liquidity surfaces, execution flow, and control gates remain separate layers with separate meanings.
Summary
- The PVR market operates through four layers: token, liquidity, execution, and control.
- The token contract regulates transfer behavior, but pools and reserves determine live price.
- Execution flows through wallets, routers, and pools, and settles atomically on-chain.
- Architecture defines structure; policy defines what is allowed and when the market is active.