DEX Integration

Overview

DEX integration describes the external trading interface through which PVR becomes tradable. Execution occurs through decentralized exchange infrastructure such as AMM routers and liquidity pools, while settlement behavior is ultimately enforced by the PVR token contract during transfer execution.

The key boundary is simple: the protocol defines token-side rules, but the pool defines price. DEX infrastructure is therefore an execution interface, not a policy override surface. Routers coordinate swaps, pools provide price and reserves, and the token contract applies any relevant transfer-side rules during settlement.

Scope

This page explains how the market-facing swap path works and what its boundaries are.

• AMM execution flow across user wallet, router, pool, and token settlement.
• Supported environment assumptions such as EVM compatibility and primary BSC posture.
• Wallet compatibility, slippage behavior, and execution sensitivity.
• Controlled launch posture and the relationship between DEX access and status controls.

Core Model

PVERSE follows a standard AMM-style integration model. Users sign transactions from wallets, routers coordinate execution against pools, and token transfers settle atomically under token-side rules. This keeps execution infrastructure and policy surfaces separate and easier to audit.

• Wallet-initiated execution: users sign swaps from EVM-compatible wallets.
• Router-coordinated pathing: routers compute paths and expected output amounts subject to user-defined slippage.
• Pool-based price formation: price emerges from reserve ratios and live trade flow, not from protocol decree.
• Token-side enforcement: taxes, gates, or safety constraints are enforced by the PVR contract during settlement, not by the router itself.

User Wallet
  ↓ (sign transaction)
DEX Router
  ↓ (calls pool)
Liquidity Pool (AMM)
  ↓ (settlement transfers)
PVR Token Contract

Operational Behavior

A user signs a swap transaction with slippage parameters from a supported wallet. The router receives the transaction, determines the pool or path, and calls into AMM liquidity. The pool updates its reserves, and settlement occurs through token transfers. If the token contract enforces taxes, gates, or other checks, those rules are evaluated at settlement time.

Execution is sensitive to real-time market conditions including liquidity depth, trade size, order flow volatility, and block-level ordering pressure such as MEV. Swaps typically remain atomic: either the full transaction succeeds under all applicable constraints, or it reverts. Users therefore still need to set slippage carefully even when the token-side rules are stable.

Constraints

• No promise of price stability, liquidity depth, or guaranteed execution quality.
• No assumption that routers override token rules; token-side policy remains authoritative during settlement.
• No implication that allocation, vesting, treasury, or reserves are defined by DEX execution itself.
• No assumption that trading is always enabled; launch posture and market access may remain gated by separate status controls.

Integrity Considerations

DEX integration is only clear when users can distinguish market mechanics from token policy. The protocol should document where swaps occur, what the token enforces, and which parts of execution are controlled by the market environment rather than by the protocol itself.

• Boundary clarity: routers coordinate execution, pools define price, and the token contract enforces transfer-side rules.
• Launch discipline: liquidity seeding and market activation should remain tied to explicit status and control surfaces.
• Wallet predictability: standard EVM wallet compatibility improves accessibility, but users still carry slippage and gas responsibility.

Future Expansion

As market infrastructure evolves, DEX integration can expand toward more venues, richer routing paths, additional pool types, or deeper execution analytics. Any expansion should preserve the same core discipline: price remains a pool outcome, token rules remain token-side, and market activation stays tied to explicit operational controls rather than undocumented assumptions.

Summary

• PVR becomes tradable through AMM DEX infrastructure composed of wallets, routers, pools, and token settlement.
• Routers coordinate execution, pools define price, and the token contract enforces settlement-side rules.
• Swaps are sensitive to liquidity depth, slippage settings, and real-time block conditions such as MEV.
• DEX access is an execution interface, not a replacement for token policy, launch controls, or status surfaces.