Route the inquiry before the conversation.
WCN uses reviewed intake because the wrong first step can create compliance, privacy, or attribution risk. Choose the path that matches your role and the responsibility you can carry.
Choose the right next action.
The contact layer is intentionally narrow. It separates applicants, partners, institutional conversations, and readers before any private information is exchanged.
Apply as a node
For operators ready to declare scope, jurisdiction, resources, evidence history, and boundaries.
Begin reviewed intakePartner with WCN
For capital relationships, projects, service providers, institutions, media, and regional operators.
Choose partner pathInvestor brief
For institutions that need stage, risk, public evidence, system maturity, and data-room request boundaries.
Review investor briefDeveloper interest
For builders who want proof-workflow context without assuming a live public API, SDK, sandbox, or GitHub surface.
Read developer boundaryPress and media
For journalists and researchers who need approved claims, fact sheets, and a safe public citation path.
Open newsroomCommunity participation
For contributors who want to share region, research, translation, development, or distribution intent.
Read community boundaryGeneral inquiry
For readers who need the public record before sending anything private.
Read before contactingReviewed inquiry form
Use the form only after choosing the closest route. The submission creates a routing reference; it does not create investment access, token rights, automatic node admission, or permission to send private material.
Public channel boundary
Before you send anything private.
Do not submit client names, contracts, wallet data, KYC material, or confidential deal terms through public channels.