№ 05·0205 · Network architecture2 min read · Section 2 of 6
5.2 Project and asset layer
The starting point of network needs: what types of projects enter, how to express needs in a structured way, and the current pain points of Deal Flow.
Updated
5.2 · Project and asset layer
L1 · Requirements entry level – projects and assets enter the system with real problems.
Without projects and assets entering the system, there will be no real input to subsequent capital, services, distribution and settlement. This layer is the entrance to the needs of the entire network and determines whether WCN has “something to do”. The current Deal Flow of Web3 is highly fragmented—project parties access capital through Telegram groups, meetings, and intermediaries, which is extremely inefficient and severely asymmetrical in information.
hierarchical positionL1 — the requirement entrance of the five-layer architecture
Core functionsProject entry, demand structuring, and pre-deal preparation
Industry pain pointsWeb3 Deal Flow is fragmented, VC projects efficiency < 3%
The core question answered at this level: Why does the network exist?
Only when projects and assets enter the system with real needs can the network have collaborative meaning. Requirements are not abstract traffic, but concrete problems:
Financing needsCapital and structural support are needed - the matching of different financing tools such as seed round, Series A, strategic round, OTC, Token Warrant, etc.
growth demandRequires brand, media, channel and community support - from narrative building to user acquisition, from KOL cooperation to exchange listing.
Service needsIt requires professional service support such as legal affairs, security audit, technology development, and Token economic design.
Asset scenarioRWA assets, on-chain equity, liquidity products and other structured assets that need to be organized, distributed and settled.
Current pain points of Web3 Deal Flow
Information fragmentationThe project team's deck, data, and team information are scattered in Telegram, Email, Google Drive, and various meetings. A VC may receive different versions of the same project from 5 channels at the same time.
Very low conversion rateTop VCs look at 3,000-5,000 projects a year and ultimately invest in 10-15 projects, with a conversion rate of less than 0.5%. A lot of time is wasted on mismatched projects - lack of structured pre-screening.
middleman dependenceThe path from the project side to the capital side is highly dependent on personal relationships and intermediaries. If a good project doesn’t know the “right people”, it may not be able to reach the right investors at all.
No standardized entryDifferent VCs require information in different formats - some require Notion, some require PDF, and some require filling out forms. Project parties spend a lot of time preparing the same information repeatedly.
Data Reference: According to Pitchbook 2024 data, the average cycle time for Crypto VC from first contact to completed investment is 67 days. About 40% of that time is spent on information collection and synchronization—exactly what the WCN project and asset layer are meant to solve.
How to solve WCN: structured entry
When a project enters WCN, standardized entry is completed through Project Intake:
Clearly list the types of resources needed—capital, legal, audit, growth, market making, listings, etc.
Material package
Deck, Tokenomics, technical documents, audit reports, etc. are uploaded at one time, and all capital parties see the same structured information.
Typical project types entering the system
Web3 Protocol / DAppDeFi protocol, NFT platform, GameFi, SocialFi and other application layer products. Financing needs + growth needs are the main factors.
AI + CryptoAI Agent framework, decentralized reasoning, data market, etc. Mainly technical needs + strategic capital needs.
RWA / Asset ProjectReal estate tokenization, bond on-chain, supply chain finance, etc. Mainly compliance needs + capital allocation needs.
infrastructureL1/L2, cross-chain bridge, oracle, DePIN, payment, etc. Technical cooperation + ecological capital demand is the main focus.
The project and asset layer are the starting point of the entire WCN architecture - no real demand enters the system, there are no assignable objects in the capital layer, no executable objects in the service layer, no propagable objects in the distribution layer, and no verifiable objects in the verification layer. It all starts here.