# Network Model W3's network architecture draws inspiration from Bittensor's subnet structure, but expands upon it to foster broader ecosystem participation and sales. (And solves some of the issues they have with misalignment around contributions). At launch, approximately 20 key partners will operate individual [subnets](/network-model/network-model/ports.md), requiring them to stake W3 tokens. Historically, identifying individual contributors at scale has proven extremely challenging for projects, especially early on in their life cycle. B2B relationships however, have been much easier to structure in a positive manner. We are leveraging our strong relationships with network partners to create a B2B2C dynamic where we can demand performance directly from our subnet owners while at the same time incentivizing them to bring in the communities that they have spent years building and vetting. These subnet owners are tasked with incentivizing their communities to engage in various roles, validating subnet commitment and driving a B2B2C model. Community participation is crucial, and includes roles such as: * **Knights:** Able to run a basic node or High Availability Node to do work on behalf of the network and/or Subnet. * **Liquidity Pools:** Stake tokens within the Subnet of their choice in order to provide transaction liquidity. * **Sales:** Become a seller of solutions within one or more selected Subnets to drive network and partner usage. * **Developers:** Create recipes and solutions that create value via solving problems. Each of these roles is rigorously defined, outlining system requirements, staking obligations, service level agreements (SLA’s), and incentive structures. This clarity ensures transparency and fairness in value distribution. This B2B2C approach aims to maximize participation and value accrual within the network. By distributing large amounts of the network to these subnet owners and their communities we can jumpstart network engagement, align incentives to bring ongoing value, and create synergies between participants. **Key aspects of our network design include:** * **Distributed Ownership and Long Term Alignment:** We pair significant distribution of the token ownership on day 1 with long term lockups to create healthy relationships with partners and their communities. * **Economic Advantage for Network Partners:** Due to our 1+1+1=5 value creation model, W3’s partners can generate more revenue selling through the network than by operating independently. Since network revenue is tied directly to token ownership, token holders benefit from overall network growth, ensuring intrinsic value accrual. * **Base Layer Economics:** W3’s B2B2C network participation model behaves like a base-layer protocol, meaning its tokenomics and incentive structures resemble those of foundational blockchain infrastructure rather than short-term dApp models. * **Early Adoption & Strategic Token Distribution:** By onboarding high-quality partners looking to be active on Day 1, W3 ensures an immediate and engaged ecosystem. A significant portion of the token supply will be distributed at launch, fueling network expansion while maintaining long-term value capture through staking mechanisms. * **Incentive-Driven Staking & Lockups:** Partners and their communities must stake and commit to long-term token lockups to access revenue opportunities, aligning all participants toward sustainable engagement and minimizing short-term sell pressure. Unstaking will cause participants to lose access to future rewards and revenue generation. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://learn.w3.io/network-model/network-model.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.