WCNWeb3 Capital Network
№ 06·0706 · Node system1 min read · Section 7 of 9

6.7 Track Partner

One Track Partner per track: the cross-geography global representative of a vertical such as AI, RWA, or DePIN.

Updated
6.7 · Track Partner

One track, one partner. The Track Partner is the cross-geography global representative.

The Track Partner is the partner tier organized by vertical rather than geography. WCN admits one Track Partner per track, with 20–25 seats across the network at USD 50,000 to 300,000 each. The seat is the cross-geography global representative of its track, connecting its nodes across countries and cities.

ScopeOne Track Partner per track, representing the vertical across geographies
Cap and price20–25 seats, USD 50,000–300,000
Relationship to geographyOrthogonal — a track edge connects nodes across countries and cities

What the Track Partner holds

A Track Partner is the partner-tier seat for one vertical — for example AI, RWA, or DePIN. The network admits one per track, so the role is exclusive within its vertical. Unlike the Country and City Partners, the Track Partner is defined by subject rather than place. It represents its track across geographies and connects its nodes wherever they sit.

The tier holds 20 to 25 seats across the network. The price runs from USD 50,000 to 300,000. As a partner tier, the seat binds rights to the same duties — resource introduction, business advancement, evidence submission, and compliance.

One partner per trackA single accountable partner represents the vertical, so its terminology, diligence, and standards have one owner.
Cross-geography reachThe seat connects the track's nodes across countries and cities, above the geographic tiers.
Shared track standardsDiligence lists, evidence fields, and compliance paths can be templated within the track to lower the cost of each loop.
Bound to one NFTRights and duties travel with the credential on ERC-721 plus ERC-6551, with the partner's account and record.
The Track Partner adds a second axis to the structure. A node carries its geographic tier and, where relevant, its track — so an RWA node in one country and an RWA node in another connect on the track edge first.

How a track organizes its nodes

A track concentrates projects, capital, services, and distribution around one set of terms and milestones. Each example below illustrates the focus a Track Partner coordinates.

AIModel vendors, application teams, compute aggregators, and enterprise buyers; the focus is API economics, data licensing, and B2B contract structures.
RWALicensed asset managers, trust counsel, rating and custody, and secondary market-making; the focus is subscription documents, off-chain rights, and onchain distribution.
DePINDevice makers, mapping alliances, and telecom partners; the focus is hardware SLAs, geographic coverage, and token-emission audits.
Payments, stablecoins, and securityMoney-service businesses, bank channels, onchain risk control, and bug-bounty platforms; the focus is fund-flow monitoring, travel-rule compliance, and incident response.

A track often crosses borders before a city fills in. AI and open-source capital are highly global, so the track edge thickens first. The Track Partner coordinates that vertical, while Country and City Partners anchor it to specific markets.

← Previous6.6 City PartnerNext →6.8 Rights bound to responsibility