12.1 · Network MVP
The deliverable is the minimum acceptable business network, not the final architecture diagram in the white paper.
This stage benchmarks Uniswap v1 and the early “single point breakthrough” of Ethereum: it does not build a full-stack chain infrastructure, but only verifies whether “structured deal + node network + auditable results” can continue to occur.
Industry reference
- Uniswap v1: Only ETH/ERC20 single AMM formula, use transaction volume and liquidity to prove the product hypothesis, and then iterate v2/v3 and governance; WCN Phase 1 is the same, first use "transactions and traces" to prove the network value.
- Ethereum Phase 0→1: Consensus and security base first, then sharding; WCN puts "chain and assets" behind, which is equivalent to stabilizing the "business consensus" (who participates, what counts as completed) first.
- Solana application layer first: In the early stage of the ecosystem, specific applications will drive performance requirements; in WCN Phase 1, Deal and node behavior will drive product and risk control needs, rather than chain design driving business in reverse.
Specific deliverables (can be written into milestone documents)
Node admission and tieringDelivery: Entry criteria, role tags (project/capital/service/distribution/region, etc.), violation and exit rules documented. Metrics: Number of active nodes, participation rate by role, repeat participation rate (non-one-time activities).
Deal Room Minimal ProcessDelivery: The shortest path SOP from opportunity entry to stage advancement (such as due diligence/terms/delivery); a single "golden path" Deal type run through. Indicators: Number of deals entering the promotion stage, stage conversion rate, average cycle (by deal type).
Proof Desk and Audit PortalDelivery: Results and evidence field standards, review queue, first version of attribution rules. Indicators: Proof submission rate, review timeliness, challenged/rejected ratio (quality proxy indicator).
early cash flowDelivery: The billing and reconciliation of seat fees, service fees, and transaction-related fees can be run. Indicators: MRR/quarterly recurring revenue prototype, customer unit price distribution, payment collection cycle; at least one type of revenue is non-zero and can be reviewed year-on-year.
Success Metrics (recommended thresholds set by governance/operations)
| Dimensions | Example Metrics | Description |
|---|---|---|
| Network | Multi-role nodes are continuously active | Non-_campaign pulse registration |
| Closed loop | End-to-end deal sample size | Similar deals can be completed repeatedly |
| Quality | Proof completeness rate and review pass rate | Avoid "only narrative without proof" |
| Business | Unit economics are positive or the path is clear | Prototype of CAC/LTV benchmarking SaaS/market place |
Signals for entering the second phase (summary)
PoB has changed from "memorable" to "understandable by third parties": the rules are documented, the sample size is sufficient for error type statistics, and the manual process before Agent access has been stabilized. See [12.4](/wiki/roadmap/12-4-Milestones and Phase Switching Signals) for details.
Main risks at this stage
demand riskDeal Insufficient supply or quality → Network idling. Slow Release: Focus on a single vertical or single Deal type penetration.
Standard is too divergentToo much customization per order → Proof cannot be compared. Release: Enforce minimum field set and templating phase.
premature windingTechnical narrative squeezes product iteration. Release: The chain is only a future option and is not part of the Phase 1 core OKRs.
Compliance and ReputationThe boundaries of financial promotion are blurred. Release: Role boundaries, disclaimers, and review rating prerequisites.
Why it’s better than “one step”
"Mainnet + Token + Full-featured Platform" is launched in the same quarter, which usually results in: expanded security, uncontrollable compliance, and inability to determine whether the failure comes from the product or the infrastructure. Phase 1 compresses failures into diagnosable dimensions (node? Deal? Proof? Billing?), which is consistent with the protocol advocated by Vitalik to reduce coordination costs in stages and Uniswap to absorb complexity through version iteration.
By the end of the first phase, the outside world should be able to answer three questions: who was in the network, what was done, and what was paid—with evidence of the answers.