# PQChain Portal / 门户技术交接 v1

Prepared 2026-10-16. This document describes this portal, not a mainnet launch or an audited production payment system.

## Delivered / 本次交付

- Bilingual Chinese/English protocol, assets, security service, documentation and workspace pages.
- Existing Chinese and English white papers v2.2, copied unchanged.
- Browser-local service request drafts, validation, reload persistence and JSON export. A draft is not an order submitted to an operator.
- Explicitly synthetic source-triage report. No live target was scanned through this portal.
- Optional EIP-1193 wallet account/network reading. No signatures, approvals or transactions.
- USDC on Base and USDT on Ethereum asset catalogue. No merchant address, prices or payment API is configured.

## Protocol facts / 协议事实

Rust PQChain v0.5 is a public-allocation candidate prototype. It implements ML-DSA-87, stake-weighted BFT and authenticated hybrid transport. Recorded operations evidence covers the same 202 Rust tests on Windows and a Linux container. This is not an external audit, independent operator verification or a mainnet activation.

Native asset design: maximum 10,000,000; public initial allocation 7,500,000 (75%); long-term security issuance 2,500,000 (25%); no free team/adviser/foundation allocation. GUI wallet v0.2 remains local-only. Native balances and candidate rewards are not a presently issued market asset.

EVM Watch Scan is a personal AI-assisted Python prototype for deployment discovery, source retrieval and rule triage. Its recorded 15 offline/mock tests are distinct from the protocol tests. Rule matches require manual review; there is no guarantee of confirmed vulnerabilities or bounty proceeds.

## External stablecoins / 外部稳定币

This is a proposed initial network selection, not a claim that either payment rail is enabled.

| Asset | Network | Chain ID | Decimals | Official token contract |
| --- | --- | --- | --- | --- |
| USDC | Base | 8453 | 6 | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| USDT | Ethereum | 1 | 6 | 0xdAC17F958D2ee523a2206206994597C13D831ec7 |

Issuer sources, checked for this portal:

- Circle: https://developers.circle.com/stablecoins/usdc-contract-addresses
- Tether: https://tether.to/en/supported-protocols/

These are token contract addresses, NOT merchant receiving addresses. External payments do not inherit PQChain cryptography. There is no bridge, native stablecoin minting or guaranteed redemption implemented here.

## Enable paid service / 正式收款前的接入工作

1. Operator confirms a service scope, actual price, payment asset/network, merchant-controlled receiving address, terms and refund policy. Do not infer these from a browser draft.
2. Implement an authenticated server-side order/quote endpoint. The server owns the order ID, asset contract, chain ID, integer amount, recipient, expiry, service scope and payment allocation. Never trust client prices or a user-supplied “paid” flag. Six-decimal stablecoin amounts must use integer base units.
3. Add a read-only receipt verifier against trusted RPC. Verify chain ID, successful receipt, canonical block hash, selected token's Transfer log, receiving address and exact base units. Confirmations/reorg policy must be chosen for each network. A transaction hash, wallet connection or screenshot is not payment proof. Reject replayed transaction/log assignments and expired/conflicting quotes; use atomic database transitions and idempotency keys.
4. On verified settlement only, enqueue an isolated authorized scan job. Resolve source provenance; limit allowed target chains, CPU, memory, input size and execution time. Do not run uploaded compiler/build scripts in the web process. Do not fetch arbitrary user URLs or execute source with host credentials. Keep RPC and explorer API keys server-side.
5. Persist durable orders/reports, authenticated customer access, operator review, cancellation/refund handling and an audit trail. Signed wallet challenges need nonce/domain/chain/expiry binding. Connecting an account alone is not identity authentication.
6. Test payment mismatches, failed receipts, reorgs, reused receipts, duplicate callbacks, concurrent claims, unauthorized report reads and interrupted jobs before enabling checkout.

The static portal deliberately fails closed. `paymentAvailability()` never enables checkout. Supplying a receiving address or turning on a UI flag is insufficient; the adapter must be replaced with the reviewed server integration above. Client code never holds merchant secrets.

## Future own stablecoin / 自有稳定币预留

Keep a separate asset/network adapter and issuer policy. There is currently no issuer, reserve proof, redemption mechanism, mint/burn contract, ticker or peg promise. A future asset needs its own technical, operational and jurisdiction-specific assessment. Do not present it as issued or guaranteed at par.

## Data / 数据

Drafts live only in this browser under `pqchain.portal.drafts.v1`, up to 20. They contain target address, requested scope and preferred settlement asset. They are not uploaded. Users should avoid entering secrets or undisclosed sensitive findings. Export JSON before clearing browser data. No analytics or third-party trackers are included.