YNX DEX

Field	Value
Version	1.0.0-candidate
Effective date	2026-07-22
Evidence source commit	`719e1018267ed5a53e6fae5211c5fd8a1503c35c`
Product release	YNX Testnet documentation candidate
Last reviewed	2026-07-22
Canonical	`https://ynxweb4.com/dex`
Title	YNX DEX — Testnet Integration, Liquidity and Wallet Safety
Meta description	Learn the YNX DEX candidate boundaries for contracts, token lists, liquidity, route review, Wallet approval and public evidence.
H1	YNX DEX

Direct answer

YNX DEX is a Testnet integration candidate, not a claim of funded public liquidity or production trading. DEX use requires verified contracts, exact on-chain state, Wallet review, price-impact/slippage controls and a committed receipt.

Contract and token gate

Network metadata and development configurations exist. Public DEX submission requires real wrapped-YNXT, factory, router and multicall addresses, source/ bytecode verification, index start block and public RPC/verifier evidence. The canonical token list must not list undeployed tokens.

Liquidity truth

A pool address does not prove usable liquidity. Liquidity claims require source, observation time, reserves, token identity, price range, depth, fee, volume method, slippage, lock/withdrawal, impermanent-loss risk and evidence ID. Test fixtures and simulated quotes are not public liquidity.

Wallet and Bridge

The user Wallet signs the exact route, inputs, minimum output, deadline, fee and approved contracts. A DEX frontend or AI cannot hold user keys or widen approval. Bridge routes are external dependencies and remain unavailable unless the exact route, contracts, finality, provider and recovery are approved.

Current status

DEX source candidates and local evidence exist separately from the accepted central baseline. Funded pools, central integration, public deployment, independent audit and production signing are not established by this page.

Change log

1.0.0-candidate (2026-07-22): Initial contract, token, liquidity, Wallet,

Bridge, status and risk page.