10.1 · Who can join
Admission depends on "what can be delivered" and "what is willing to bear", not the number of fans and slogans.
WCN nodes are institutional-level participants—VCs, professional service providers, regional and ecological partners—who must bring in verifiable resources and accept traces and reviews. The model is close to the superposition of YPO (recommendation + annual fee + regulations), Bloomberg Terminal (contract subject + purpose compliance), and licensed exchange members (qualified investors and market-making obligations): it is not “registration is a member.”
Comparison with the three types of traditional access
| Analogous objects | Common points | Implications for WCN |
|---|---|---|
| YPO / High-end Trade Association | Recommendation system, background verification, ongoing membership dues and code of conduct | Node seats are "relationship assets" and need to maintain reputation and output |
| Bloomberg Terminal | B2B contracts, usage restrictions, per-seat billing | System access and data/workflow permissions and subject binding |
| Exchange membership/market making agreement | Eligibility threshold, margin or performance obligations, terminable qualifications | Symmetrical authority and responsibilities, downgrade or removal if standards are not met |
Access points by node type
The following standards are directional thresholds, which are subject to the current network policies and legal provisions; the review side usually requires verifiable materials (copy of license, fund filing, case desensitization, team LinkedIn/official website consistency, etc.).
Capital node (VC/family office/strategic investment)Example of hard threshold: Discloseable management scale or single check range (such as angel $100k–$2M, growth stage $2M–$20M, depending on the strategy); at least 2–3 citeable investments or lead records in the past 24 months; designated investment committee or partner as the responsible person within the system. Soft threshold: Track tags, geographical coverage, and follow-up/lead investment preferences are written into the Capital Profile for L2 matching.
Service nodes (law firms, auditing, security, technology, brand growth)Hard Threshold Examples: License to practice or equivalent qualification; Discloseable delivery case (contract or SOW desensitization); Fixed SLA (response hours, delivery milestone template). Rejected items: No entity, no Professional Indemnity guarantee (depending on business line requirements), refusal to enter the Task acceptance process.
Distribution and liquidity nodes (media, KOL, exchanges, market making)Examples of hard thresholds: audience or transaction level range (such as coverage, average daily depth, quantitative results of historical campaigns); compliance disclosure capabilities (advertising labels, jurisdictional restrictions). Boundary: The distribution behavior must be attributable to the WCN Task, and empty promises of "only listing but not performing" are prohibited.
Regional / Ecological PartnerExamples of hard thresholds: local entities or licensed representatives; list of accessible institutions and conference/event capacity; bilingual delivery capabilities (if cross-border coverage). Obligation: Usually bound to the exclusive or semi-exclusive seat limit of the geographical or vertical track (for example, the number of master nodes in a single jurisdiction is limited) to avoid internal competition from diluting PoB.
Project side nodeHard Threshold Example: Verifiable product stage (mainnet/testnet/revenue); complete financing or token structure documentation; clear list of requirements (capital, services, exchange listing, market making). Note: The project side is more of a demand-side entrance, and seats are often bound to specific deals or assets, rather than unlimited generalized permissions.
Agent/technical operation nodeExamples of hard thresholds: API stability, data residency and privacy terms, human-machine collaboration SOP; auditable automation logs. Boundary: Agent output requires human node endorsement before it can enter the high-sensitivity settlement path.
Who is not suitable to apply
Even if the following entities complete the wallet connection or fill out the form, it does not constitute effective access: ① Unable to prove resource sources and delivery capabilities; ② Only seeking traffic exposure or secondary hype, with no intention to participate in the Deal/Task closed loop; ③ Rejecting the evidence package, rejecting KPI or review; ④ Conflict with sanctioned jurisdictions or high-risk industry lists (subject to compliance review).
The bottom four (common across types)
Resources can be brought inAt least one of capital, delivery capacity, distribution or regional network is quantifiable, quotable, and callable within the system.
Self-consistent roleIn the L1–L5 architecture, the main responsibility levels (demand side, capital side, execution side, distribution side or verification side) are clearly defined to avoid “all-round occupancy”.
Accept the rulesTrace collaboration, permission boundaries, Conflict disclosure and upgrade paths - similar to exchange risk control email chains, are the norm rather than the exception.
The relationship can be renewedAcceptance seats are non-permanent: renewal is subject to output and compliance status, similar to renewal review of annual membership fees and conduct terms.
The only valid criteria: what verifiable increments you can inject into the network, and what auditable obligations you are willing to cede.