YNX Products
| 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/products |
| Title | YNX Products — Independent Apps in the YNX Web4 Ecosystem |
| Meta description | Explore independent YNX Web4 product candidates and understand their Wallet, data, asset, platform and release boundaries. |
| H1 | YNX Products |
Direct answer
YNX Web4 is a portfolio of independent products powered by YNX Chain. Shared account identity, YNXT, Trust evidence and design language do not grant shared custody or unrestricted sessions. Each product has its own workflow, scopes, platforms and evidence.
Portfolio
| Product group | Primary purpose | Current public boundary |
|---|
| Wallet | Account custody, signing and permissions | Candidate engineering; production/store states require evidence |
| Pay and Merchant | Intents, invoices, settlement, receipt, refund/dispute | Testnet/local candidates; public value flow is not generalized |
| Explorer and Monitor | Public derived chain views and operator observability | Derived from authoritative sources; freshness and deployment vary |
| Developer | Code, contracts, verification and deployment workflow | Tooling exists; signed desktop/public IDE evidence incomplete |
| Exchange, DEX and Quant | Markets, swaps and strategy workflows | No production custody/liquidity/performance claim |
| Trust and Resource | Evidence/appeal and bounded resource workflows | Protocol/product candidates; authority remains explicit |
| AI | Permissioned drafting and suggestion | Cannot independently execute sensitive actions |
| Cloud, Docs and media | Storage, collaboration and content workflows | Product candidates require durability/rights/provider evidence |
| Social, Search, Browser, Finance, Mail and Calendar | Independent application experiences | Availability and integrations remain component-specific |
Release-state rule
For each product, check source implementation, local tests, installation, central integration, staging, public deployment, hosted download, production signing and store release separately. A newer candidate revision, screenshot or preview package does not prove another state.
Shared safety rules
- Canonical Wallet approval and least privilege.
- No product receives seed or arbitrary withdrawal authority.
- AI proposes but does not autonomously execute.
- Data identifies source, freshness, version and failure.
- Empty/offline/permission/expired/recovery states are real.
- Testnet, simulation, unsigned and production classes stay distinct.
Related pages
Change log
- 1.0.0-candidate (2026-07-22): Initial portfolio, status and shared-safety page.