Chapter 5 · Network Architecture
The five-layer architecture gives Web3's multi-party collaboration a system skeleton for the first time.
WCN is not a collection of functions, but a business architecture with clear layers and linkage between top and bottom. The five layers are from demand entrance to value exit. Each layer answers a core question. The output of the previous layer is the input of the next layer. This design is not a theoretical choice, but a structural experience extracted from TradFi’s investment banking division of labor and Internet platform architecture.
5.1 Overview of five-layer architectureWhat questions do the five layers answer, how to connect them in series, and comparison with TradFi and Web2 platform architectures.5.2 Project and asset layerRequirement entry: what types of projects enter, how to express requirements in a structured way, and the current pain points of Web3 Deal Flow.5.3 Capital allocation layerCapital is not just money, but also judgment and allocation capabilities. Comparison with TradFi GP/LP model, Mandate-based Allocation.5.4 Execution and service layerThe critical bridge from connection to delivery. The current situation of Web3 service fragmentation and how Agent can amplify execution capabilities.5.5 Distribution and Liquidity LayerHow the results hit the market. Systematic collaboration among stock exchanges, market makers, media, and KOL, compared with the traditional IPO process.5.6 Verification and Settlement LayerThe closing layer of the architecture: Proof Desk, PoB, Attribution and Settlement, giving all collaborations a trusted endpoint.
The five layers are not parallel modules, but business sequences - projects raise demands → capital receives demands → services promote execution → distribution is sent to the market → value is verified and settled. Once you understand this sequence, you understand the system logic of WCN.