# Welcome to W3.io

### **The Intelligence Layer Web3 Has Been Missing.**<br>

Blockchains have an intelligence problem, and it’s holding back the entire industry. Transactions are too rigid, smart contracts are too basic, and Web3 lacks the ability to reason, verify, and execute complex logic autonomously. If these issues are not addressed, promising use cases such as on-chain AI, RWAs and so many others will never scale to their full potential.

W3.io is the critical intelligence layer that enables the entire Web3 industry to build solutions that matter.  By providing out-of-the box intelligence and seamless two-way business automation for complex on-chain workflows, W3 allows you to do things better on-chain than off-chain.  Our platform empowers our growing ecosystem and its developers to build faster; eliminating the need for expensive integrations or infrastructure.

Backed by a network of 60+ top-tier partners and a a world-class team of experts in AI, cryptography, and decentralized systems, w3.io is setting the foundation for the next evolution of Web3.

*It’s time for Web3 to evolve. W3.io is making it happen.*

<div align="left"><figure><picture><source srcset="/files/WrSC7xeg7E2AmvdoNelv" media="(prefers-color-scheme: dark)"><img src="/files/1rCVPeamzmzTJydpH4rR" alt="" width="375"></picture><figcaption></figcaption></figure></div>

### Jump right in:


# W3's Special Sauce

## Goal: To host the largest decentralized salesforce in all of web3.&#x20;

**W3 is unique** because of four key elements: &#x20;

* A platform that makes **programmable intelligence scalable** by providing a seamless bridge between off-chain compute resources and on-chain execution.&#x20;
* W3 allows organizations to maintain their existing processes while participating in common workflows, creating a **standards layer required for complex multi-party transactions**
* A network design that **incentivizes ecosystem value creation** **and adoption** at every level by all community participants.
* The first of its kind ecosystem-focused revenue model that will attract an **army of builders and sellers** to the platform looking for adoption and revenues.


# FAQ

**What is impossible without W3.io?**&#x20;

*Problem:* Blockchains have yet to scale because so far everyone has required organizations to calibrate business processes identically for each partner to participate, which makes scaling complex multi-party transactions impossible. &#x20;

*Solution:* W3 allows organizations to maintain their existing processes while participating in common workflows, creating a standards layer required for complex multi-party transactions (i.e. onchain AI and RWAs).

\
**What else can W3 do that can’t be done anywhere else?** &#x20;

W3 is unique because of five key elements:

* A platform that makes programmable intelligence scalable by providing a seamless bridge between off-chain compute resources and on-chain execution.
* A network design that incentivizes ecosystem value creation and adoption at every level by all community participants.
* A token model designed for crypto winter resiliency that drives long term lockups, where network revenues will flow to token owners.
* The first of its kind ecosystem-focused revenue model that will attract an army of builders and sellers to the platform looking for adoption and revenues.

**What is W3’s competitive positioning?**&#x20;

W3 is structured as an industry consortium consisting of Web3’s top off-chain compute projects and L1/L2 ecosystems.  In Web2 our direct competitors are the large cloud providers (AWS, GCP, Azure, etc).  Since we are a neutral entity that’s organizational purpose is to increase the total addressable market for Web3 compute and blockchain ecosystems, we currently have no direct or indirect competitors in Web3. &#x20;

While W3 does orchestration, it is only a small fraction of the platform’s capabilities.  Orchestration only connects disparate pieces of technology and is not a catalyst for driving wide scale adoption or Web3 scalability.  Given our positioning as a true decentralized full stack cloud, we think we are well positioned to capture a massive TAM and outperform other Web 3 infrastructure projects.&#x20;

**How does the platform work?**&#x20;

W3’s programmable intelligence refers to systems that combine programmability (logic, control, decision rules) with intelligence (adaptivity, reasoning, learning, and/or generative capabilities). These systems can act autonomously, adapt to context, and be explicitly controlled or customized through code or logic. While we will also have a drag and drop front end, W3 goes well beyond Zapier’s capabilities in that we provide developers with an interoperable set of infrastructure and services that they can use to build out business or IT functionality that is customizable and adaptable. &#x20;

One major reason that we can have a more flexible backend infrastructure than Zapier is that the conditional logic that powers our workflows will reside in the smart contracts themselves. As such, developers can customize their logic at the smart contract level while having the ability to configure off-chain resources in a wide range of different configurations.&#x20;

**Are you focused on specific use cases?  Examples?** &#x20;

Our initial focus will primarily be on on-chain AI, Identity and Compliance, Payment Solutions and RWAs use cases due to W3’s strong value proposition for these solution types.  However, we are also prioritizing high potential use cases with Web2 organizations looking for a better, cheaper, faster, tech stack in order to demonstrate the revenue flywheel effects for our community. &#x20;

<br>


# W3's Data Room

This section addresses common questions about our platform, features, integrations, and usage. Whether you’re a developer, partner, or just exploring, you’ll find quick answers to help you get started

**Welcome to the W3.io Data Room!** &#x20;

This is your one-stop-shop for all relevant documents, videos, and frequently asked questions to support your due diligence process.

* Background Information
* Videos
* Frequently Asked Questions

<br>


# Background Information

**W3.io Overview**

Investor Deck

<https://docsend.com/view/s7bnjddjp8v5wn7b>\
Password: letscook

**W3.io Cookbook**

An overview of why to cook with W3, frequently used recipes, and details on how recipes work.

<https://docsend.com/view/59c7yckjae6rte24>\
Password: letscook

**Protocol Technological Overview**\
<https://docsend.com/view/9kxwyten773vxfg8>

**W3's Network & Token Economy Overview**

A high-level description of how W3 will handle incentives and tokenomics to ensure the sustainability of the network.

<https://docsend.com/view/5ssb9at9sp5rpxet>\
Password: letscook

**W3 Solution Spotlight - Payments**

A brief description on what we are doing to advance and automate payment processing, inclusive of our initial pilot with IrelandPay as well as our fast follow opportunities. &#x20;

<https://docsend.com/view/62u24t5cxast43qz>\
Password: letscook<br>


# Videos

**Platform Overview Demo**&#x20;

{% embed url="<https://vimeo.com/1071190914/e705ca4afa>" %}
W3.io UI Demo
{% endembed %}

**Creatorland Testimonial**

{% embed url="<https://vimeo.com/1073702772/6c35a16ef4>" %}


# Programmable Intelligence

Blockchains today are powerful but not very smart. They rely on rigid smart contracts that can only follow preset rules and basic oracles that simply bring outside data onto the blockchain without verifying or acting on it. This makes blockchains passive and limited. They can store and execute transactions, but they can’t adapt, think, or automate complex decisions on their own.

To truly unlock the next era of Web3 and gain mass adoption, blockchains need programmable intelligence—they must be able to reason, verify, and execute complex logic autonomously without relying on centralized intermediaries.\
\
W3.io is spearheading **PIE (Programmable Intelligence Economy)** a new movement within Web3 focused on making blockchains smarter, more programmable, and capable of handling complex decision-making and execution. 



By increasing the intelligence of blockchains, PIE doesn’t just enhance existing capabilities — it expands the total addressable market (TAM) for all of Web3, making the "pie" bigger for everyone.

<figure><img src="/files/x5hysGQEy30lLpQzObWA" alt=""><figcaption></figcaption></figure>

### **PIe enables innovations such as:**

* **Multi-Agentic Workflows**&#x20;
  * Autonomous AI agents collaborating, executing, and optimizing tasks across decentralized networks without human intervention.
* **RWA (Real World Assets)**
  * Tokenized real-world assets with smart, programmable automation for seamless on-chain management and verification.
* **AI-Powered Smart Contracts**
  * Self-learning, adaptive contracts that process real-world data, optimize execution, and evolve autonomously.
* **Intelligent Intents**
  * Programable intents that enable automation and complex use cases between and within ecosystems.&#x20;
* **Decentralized Data Sharing**
  * Open, trustless data flows where users control, share, and monetize information while optimizing and customization\ <br>


# Prodigy Networks

Prodigy Networks enable blockchains that can
 Think. Adapt. Act.

**Prodigy Networks**—next-generation decentralized networks that go beyond traditional oracles. Unlike basic data feeds, ***Prodigy Networks don’t just relay information—they process, verify, and trigger intelligent automation across blockchains and off-chain systems.*** Prodigy Networks usher in the next generation of decentralized applications that can autonomously respond to real-world events, execute cross-chain adaptive logic, and power AI-driven smart contracts.

<figure><img src="/files/2Vfjr51V5xnimfljYq4w" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Basic Ledger

Just stores transactions (Bitcoin model).
{% endstep %}

{% step %}

### Smart Contracts

Executes pre-set rules but can’t adapt.
{% endstep %}

{% step %}

### Oracles

Provides outside data but lacks decision-making.
{% endstep %}

{% step %}

### Prodigy Networks

Autonomous, self-executing logic that reasons, verifies, and adapts.
{% endstep %}
{% endstepper %}

<figure><img src="/files/JMscaK6xgXCTKiWkq29w" alt=""><figcaption></figcaption></figure>


# Massive TAM

## TL;DR

To date, working off-chain or with web2 has been easier than building on-chain.  W3.io has the capabilities today to easily transition web3 native applications off of web2 into higher value on-chain web3 alternatives. \
\
W3 gives developers the ability to make blockchains smarter, more programmable, and capable of handling complex decision-making and execution, unlocking the ability for on-chain AI to scale to its full potential.   W3 is set to challenge Public Cloud providers by providing easier to manage, more composable, more decentralized, and more intelligent solutions for end users.&#x20;

Soon, w3 will disrupt the mechanisms and analog vehicles that have enabled the Public Cloud providers to drive trillions in revenues over the past decade with on-chain integrations, automation, verifiability, and payments into a seamless end to end experience running on crypto rails. &#x20;

**Total Addressable Market: +$200B/year**

## Breakdown

## Web3 Today

## Web3-native companies currently spend $500M–$1B annually on centralized IT services—W3 unlocks this spend for decentralized alternatives.

How we capture the market (0-9 Months):

* W3 gives our entire community the tools to quickly build intelligent solutions that solve real world problems. &#x20;
* W3 enables partners as well as our entire community to sell integrated packages of services repeatedly to multiple customers and verticals. &#x20;
* Bundling expands the TAM for each partner, each solution, and w3 itself. *For example: A data protocol can now bundle with compute, storage, or compliance services.*

## Web3 AI Today&#x20;

## The target obtainable market for web3 AI in 2025 is estimated at $5-10B annually. &#x20;

How we capture the market (0 - 24 Months):

* W3 pioneers solutions in Multi-Agent AI workflows that scale (example: Creatorland & GAIA) that can be quickly resold to other end users and verticals to establish beachheads.&#x20;
* W3 demonstrates to partners how w3 scales Web3 AI solutions as well as drives revenue to ensure complex AI workflows are built on and go-to-market via our platform with real world examples. &#x20;
* Leverage end user beachheads to bring ecosystem-built AI solutions to web3 friendly decision makers for cross sell. &#x20;

## Annual Revenue from All Public Cloud Providers from MSA's (Master Service Agreements) &#x20;

**$150B - $200B per year** from MSA-driven contracts across the cloud industry. &#x20;

How we capture the market (12-36 Months):

* Remain the leader in web3 MSA equivalence that enable w3'c ecosystem to drive revenues to all participants with automated payments, procurement through the building of intelligent solutions.
* Collaborate with Global System Integrators (EY, Deloitte, Accenture, BCG) on how to run strategy engagements around community solutions on w3. &#x20;
* Go full decentralized salesforce that activates the entire industry to drive the best of breed solutions into the market. &#x20;

When w3.io achieves its goal of becoming the largest decentralized sales community in the industry with the ability to achieve fully integrated, verifiable, and autonomous solutions complete with waterfall billing and built-in procurement and legal agreements, the traditional MSA model will become a dinosaur. &#x20;


# Platform Overview

W3.io's Platform & UI will provide features and tools for users to maximize platform utility for value creation.&#x20;

* Blockchains have yet to scale because so far everyone has required organizations to calibrate business processes identically for each partner to participate, which makes scaling complex multi-party transactions impossible.  W3 allows organizations to **maintain their existing processes while participating in common workflows,** creating a standards layer required for complex multi-party transactions (i.e. onchain AI and RWAs)    &#x20;
* W3 **expands trustlessness** to encapsulate the entire workflow, making verifiability of solutions possible (versus only verifying one ingredient in isolation).
* Today, end users have the burden of managing the complexity of multiple products in order to achieve outcome.  W3 provides a **single-pane of glass for solution/recipe creations and management** with waterfall billing and instantaneous payment settlements as usage/revenue comes through the platform.&#x20;


# Protocol Architecture

### What is W3.io?

W3.io is a decentralized coordination network that bridges blockchain's on-chain execution capabilities with off-chain computational power. While Oracles focus on verifiable data feeds (2D), W3.io enables verifiable workflows that coordinate complex multi-step processes across decentralized infrastructure (3D).

Unlike traditional blockchains, W3.io is not an L1. Instead, we operate a specialized network of nodes that act as intelligent coordinators, executing "recipes" (workflows) that combine multiple "ingredients" (network partners' services) into complete business solutions.

#### Key Differentiators:

* **Programmable Intelligence**: Smart contract systems that can "think, adapt, and act" through AI-driven logic
* **Cross-Chain Coordination**: Native interoperability across multiple blockchain networks
* **Verifiable Workflows**: End-to-end cryptographic verification of complex multi-party processes
* **Partner Ecosystem**: 60+ integrated decentralized compute and middleware providers

W3.io's Prodigy Network represents a paradigm shift in blockchain infrastructure, creating what we call **"programmable intelligence" — a seamless bridge between off-chain compute resources and on-chain execution.** Our architecture enables unprecedented flexibility where complex adaptive logic can flow seamlessly between off-chain data sources, intelligent computation, and on-chain execution.

<figure><img src="/files/X6xARKKQNjdu8WliVRBR" alt=""><figcaption><p>W3.io Protocol Architecture Diagram</p></figcaption></figure>

1. **Off-Chain Compute**\
   \
   At the top tier, our extensive network of over 60+ decentralized compute partners provides specialized services ranging from AI inference to data verification. Unlike traditional approaches that rely on centralized services (costing web3 projects approximately $180 million annually), our architecture leverages decentralized alternatives that maintain the core ethos of web3 while providing enhanced capabilities.

   These partners represent the best-in-class for their respective specialties, carefully selected based on their commitment to decentralization and their ability to solve specific business problems. By integrating them directly into our protocol, we demonstrate the same trust in decentralized solutions that we advocate to our customers.<br>
2. **Knights Layer**

\
   \
   The middle tier consists of our Knights network — decentralized nodes that execute W3.io recipes. These nodes operate based on a uniform core code structured as an event-driven finite state machine, optimized for efficiency and reliability.\
   \
   Knights come in three varieties to accommodate diverse computing resources:

   * **High Availability Nodes**: Equipped with advanced compute resources including TEEs, GPUs, and high-performance CPUs, targeting 99.999% uptime.
   * **Normal Nodes**: Similar to desktop computers with consistent but occasionally interrupted connectivity.
   * **Community Nodes**: Devices with intermittent availability that can contribute during periods of non-use.

   Unlike other systems that require costly specialized hardware, W3.io lowers barriers to entry, allowing individuals to contribute with existing devices, while still accommodating professional node operators. All nodes, regardless of category, participate as consensus peers within the network, executing the ingredients assigned to them.<br>
3. **Blockchains**

\
   \
   The foundation tier connects to multiple L1/L2 networks, allowing smart contracts to be executed on the customer's blockchain of choice. This native cross-chain compatibility ensures that W3.io can interact with any blockchain ecosystem, providing flexibility and future-proofing for our customers.

**How The Layers Interact**

When a recipe is triggered (shown by the red path in the diagram), the Knights network orchestrates the entire workflow:

1. The recipe file defines the business process to be executed.
2. Knights coordinate to execute each step in the recipe.
3. When off-chain computation is needed, Knights securely interface with the appropriate compute partners.
4. When on-chain actions are required, Knights interact with the specified blockchains.
5. Throughout execution, all operations are logged and cryptographically verified.

This architecture solves the critical challenges identified in our whitepaper:

* **Reducing dependence on centralized services** by creating a decentralized alternative.
* **Simplifying technical integration** by orchestrating complex workflows across multiple providers.
* **Addressing business challenges** by providing a unified framework with established partnerships and single pane of glass payments.

#### Verification and Consensus

Every recipe execution follows this verification flow:

1. **Trigger Detection**: Multiple nodes detect and verify the triggering event
2. **Consensus Formation**: Selected nodes reach agreement on execution parameters
3. **Step-by-Step Logging**: Each ingredient execution is hashed and logged
4. **Merkle Tree Aggregation**: Completion hashes are aggregated into Merkle trees
5. **On-Chain Recording**: Merkle roots are recorded on customer's preferred blockchain
6. **Persistent Storage**: Full logs stored on decentralized storage for long-term verification

#### Consensus without an L1

Our unique challenge: achieving consensus about work completion and rewards without building a full blockchain.

**Solution**: Recipe-level consensus with distributed execution

* Each recipe runs on a subset of nodes based on consensus requirements
* Nodes participate in consensus for their assigned recipes
* Results are cryptographically verified and recorded on customer's preferred chain
* Network maintains coordination state without global blockchain overhead


# Ingredients

Each one of our [Network Partners](/ecosystem/network-partners) can be used as an ingredient in a recipe.

An Ingredient is an official W3.io off-chain compute partner who has made their specialized capabilities available via the W3.io platform for inclusion in recipes and solutions. These ingredients form the building blocks of complex business processes, providing specialized functions ranging from AI computation to data storage and verification. <br>

<div align="left"><figure><img src="/files/RVJzYNsFU4b4ifxinbBd" alt="" width="563"><figcaption></figcaption></figure></div>

### What Ingredients Provide

Ingredients represent specific tasks or operations that can be executed as part of a recipe. They are modular, reusable components that can:

* Execute functions such as accessing databases, performing calculations, or interacting with blockchains.
* Add or modify variables within a recipe's variable pool to maintain state.
* Generate verifiable logs for integrity and traceability.
* Be simple (performing a single task) or compound (consisting of multiple sub-ingredients).

### Becoming an Ingredient Partner

Projects looking to become W3.io ingredients should:

1. Offer a decentralized solution that fills a specific need within the web3 ecosystem.
2. Provide robust APIs or integration points that can be utilized by our Knights network.
3. Commit to maintaining service quality and reliability.
4. Work collaboratively with W3.io to ensure their solution integrates effectively.

W3.io does not charge partners for participation in our network. Rather, we focus on creating mutual value through ecosystem development and increased exposure.

### Benefits for Developers

By utilizing W3.io ingredients, developers can:

* Access specialized capabilities without managing individual relationships with numerous providers.
* Reduce integration complexity through our standardized interface.
* Build complex solutions from verified, reliable components.
* Benefit from W3.io's unified payment system rather than juggling multiple payment mechanisms.
* Leverage the collective expertise of our carefully selected network partners.
* Build end-to-end solutions faster!

### Benefits for Ingredient Partners

As an ingredient in the W3.io ecosystem, partners gain:

* Expanded exposure to new customers through the W3.io platform.
* Additional revenue streams from usage within recipes and solutions.
* Collaborative opportunities with complementary network partners.
* Simplified customer acquisition through W3.io's unified platform.

### Technical Architecture

**Ingredients** are modular, reusable components that represent specific tasks:

* Database queries, AI inference, blockchain transactions, identity verification
* Each ingredient generates verifiable logs and maintains recipe state
* Can be simple (single task) or compound (multiple sub-ingredients)

**Special Trigger Ingredients** serve as entry points to recipes:

* Schedule-based triggers (time elapsed)
* Blockchain event triggers (transaction occurred)
* API call triggers (external system notification)
* Email receipt triggers (message received)


# Recipes

Recipes are structured workflows composed of multiple ingredients orchestrated into verifiable, executable business processes. They represent the computational backbone of the W3.io ecosystem, transforming disparate blockchain and off-chain services into cohesive solutions that address real-world challenges. &#x20;

<div align="left"><figure><img src="/files/55ikuakgANzcMFrnfm6U" alt="" width="375"><figcaption></figcaption></figure></div>

### Anatomy of a Recipe

Each recipe is comprised of several key components:

* **Trigger**: Every recipe begins with a trigger—a specific event that initiates the workflow. This could be a blockchain transaction, a time-based event, an external API call, or any other defined condition. Triggers are the entry points that determine when and how a recipe executes.
* **Variable Pool**: A dynamic data storage mechanism that enables ingredients to share and modify information throughout the recipe's execution. This maintains state across the workflow and ensures data consistency.
* **Workflow Steps**: A carefully sequenced series of operations where each ingredient processes data and passes results to subsequent steps. The sequence can include conditional logic, loops, and parallel processing paths.
* **Failure Handling**: Built-in mechanisms to manage errors or exceptions that may occur during execution, including logging errors, retrying steps, or executing alternative workflows.

### How Recipes Work

When a trigger event occurs, the W3.io Knights network activates the corresponding recipe. Knights coordinate to execute each step in the workflow, interfacing with the appropriate ingredients as defined in the recipe. Throughout execution, all operations are cryptographically logged and verified to ensure integrity and traceability.

Recipes can range from simple two-step processes to complex workflows with dozens of operations across multiple chains and services. The adaptive logic within recipes can respond to changing conditions, making them suitable for a wide range of business applications.

### Creating Recipes

Recipes can be created through:

1. **Visual Interface**: Our intuitive drag-and-drop interface allows business users to design workflows without writing code.
2. **Command Line Interface (CLI)**: Power users can script and automate recipe creation through our CLI.
3. **API**: Programmatic creation and management of recipes for integration with existing systems.

All recipes are stored in a standardized format that ensures portability and version control, making it easy to iterate and improve them over time.

### Verification and Trust

One of the core principles of W3.io recipes is verifiability. Each step in a recipe generates cryptographic proofs that the operation was executed correctly. These proofs are aggregated into a Merkle tree and can be anchored to any blockchain, creating an immutable record of execution.

This verification system ensures that even when working with multiple off-chain providers, the entire process maintains the trust and transparency that blockchain technology promises.

### Benefits of Recipes

* **Reusability**: Once created, recipes can be reused across multiple business processes.
* **Composability**: Recipes can be combined or nested within larger workflows.
* **Adaptability**: Easily modified to accommodate changing business requirements.
* **Transparency**: Complete visibility into every step of execution.
* **Efficiency**: Automated orchestration reduces manual intervention and potential errors.

Recipes are the connective tissue that binds together the diverse capabilities of our ingredient partners, transforming individual services into powerful, integrated solutions that bridge the gap between blockchain's promise and practical business applications.

### Recipe Architecture

**Recipes** are structured workflows composed of multiple ingredients, defining complete business processes triggered by specific events.

Each recipe includes:

* **Trigger**: Initiates execution based on events
* **Variable Pool**: Provides dynamic data storage for ingredient communication
* **Workflow Steps**: Ordered sequence where each ingredient processes data
* **Failure Handling**: Mechanisms for error management and alternative workflows

### Example: Multi-Party Asset Rebalancing

Trigger: Market condition change detected\
├── Step 1: Identity verification (Privado ID)\
├── Step 2: Compliance verification (Cube3)\
├── Step 3: Portfolio analysis (Space & Time)\
├── Step 4: Trade order generation (Yelay)\
└── Step 5: Cross-chain execution (LayerZero)\
Result: Verifiable on-chain record of entire workflow

### Developer Experience

**Current State**: Command-line interface and YAML for recipe creation and deployment

**Future Roadmap**: Enhanced developer tooling planned:

* **Recipe Creation**: Target < 1 day using planned visual interface
* **Ingredient Integration**: Pre-built integrations to reduce/eliminate custom development
* **Testing & Deployment**: Planned sandbox environment with real partner integrations
* **Monitoring**:  Real-time dashboards for workflow execution and performance


# Solutions

Solutions are 1 or more recipes configured into an end user’s IT environment. In short, a recipe (or combination of recipes) graduates to being a solution when the necessary customizations happen for it to go live in an end users’ IT environment.

<div align="left"><figure><img src="/files/jwKookKFszmNsZqDhON0" alt="" width="563"><figcaption></figcaption></figure></div>

### What Makes a Solution

A solution is a complete end-to-end application that:

* Integrates one or more W3.io recipes to handle complex workflows.
* Includes customer-facing components such as web interfaces, mobile apps, or APIs.
* Connects with existing business systems through integration points.
* Addresses specific industry use cases or business challenges.
* Can be deployed, managed, and monitored as a unified product.

Solutions transform the technical capabilities of recipes into practical business tools that organizations can readily adopt and use to solve real-world problems.

### Technical Advantages

| Capability               | Traditional Integration     | Current Oracles   | W3.io                 |
| ------------------------ | --------------------------- | ----------------- | --------------------- |
| Data Feeds               | Manual API calls            | ✅ Automated       | ✅ Automated           |
| Complex Workflows        | Not possible                | ❌ Limited         | ✅ Full support        |
| Multi-Party Coordination | Requires separate contracts | ❌ No coordination | ✅ Native coordination |
| AI/ML Integration        | Custom implementation       | ❌ No support      | ✅ Simple              |
| Cross-Chain Operations   | Bridge manually             | ❌ Limited CCIP    | ✅ Native support      |
| Verification Scope       | Per transaction             | Data only         | ✅ End-to-end workflow |

### The Power of W3.io Solutions

W3.io solutions go beyond simple applications by addressing multiple complex technical and business challenges:

* **Single-Pane of Glass Management**: Solution owners gain a unified dashboard to monitor customers, track usage, manage payments, identify bottlenecks, and optimize performance—all from one central interface.
* **Autonomous & Verifiable Event-Driven Workflows**: Solutions incorporate active listening capabilities that trigger workflows based on real-world events, enabling automated responses to changing conditions while maintaining cryptographic verifiability.
* **Waterfall Payments**: The W3.io platform manages the entire payment flow—from the solution seller to the solution owner to all ingredient partners—ensuring everyone is paid via stablecoins based on predetermined wholesale rates.
* **Compliance & Procurement**: All ingredient partners are validated for eligibility, compliance, pricing, security, and quality assurance, with all necessary legal documentation made available to developers building recipes and solutions.

### Integration Value Proposition

Instead of integrating 5 services individually (14 weeks, $60k+ cost), developers access our entire ecosystem:

* **Pre-built Integrations**: 60+ partners integrated and tested over time
* **Single API Access**: One integration provides access to the full decentralized stack
* **Unified Payments**: Single payment flow handles all partner compensation
* **Shared Security Model**: Consistent security and verification across all services

### Solution White-Labeling and Distribution

By default, W3.io solutions are designed to be white-labeled, allowing network participants to either:

1. **Sell Existing Solutions**: Market and distribute pre-built solutions to their own customer base under their own brand.
2. **Customize Solutions**: Modify existing solutions to meet specific client needs.
3. **Build New Solutions**: Create entirely new solutions leveraging the W3.io platform and ingredient network.

This approach creates a vibrant marketplace where solution builders can focus on creating value while resellers can focus on customer relationships and market access.

### Solution Components

A typical W3.io solution package includes:

* **Recipe Collection**: The core workflows that power the solution's functionality.
* **User Interfaces**: Web portals, mobile applications, or other interfaces for end users.
* **Deployment Templates**: Standardized configurations for quick implementation.
* **Branding Assets**: Customizable elements for white-labeling.


# How it Works

### End-to-End Execution Flow

When a recipe is deployed on the W3.io network, here's exactly what happens:

**1. Event Detection**

Multiple nodes monitor for the recipe's trigger event:

* **Blockchain events**: Transaction confirmed, block mined
* **Time-based events**: Schedule elapsed, deadline reached
* **External events**: API call received, price threshold crossed
* **Data events**: Database updated, file uploaded

**2. Node Selection & Consensus**

The network automatically selects nodes to execute the recipe:

* **Consensus formation**: Selected nodes agree on execution parameters
* **Resource allocation**: Nodes with required capabilities are chosen
* **Load balancing**: Work distributed across available nodes
* **Verification setup**: Backup nodes assigned for verification

**3. Recipe Execution**

Nodes execute ingredients in sequence:

* **Variable pool initialization**: Shared data storage created
* **Step-by-step processing**: Each ingredient processes and passes data
* **Real-time logging**: Every action hashed and recorded
* **Error handling**: Failed steps trigger alternative workflows or rollbacks

**4. Cross-Chain Coordination**

For multi-chain recipes:

* **State synchronization**: Consistent data across all chains
* **Atomic operations**: All chains succeed or all fail together
* **Message passing**: Secure communication between chain-specific nodes
* **Verification aggregation**: Results combined from all participating chains

**5. Verification & Recording**

Results are cryptographically verified:

* **Merkle tree construction**: All execution hashes aggregated
* **Consensus validation**: Nodes agree on final results
* **On-chain recording**: Merkle root stored on preferred blockchain
* **Decentralized storage**: Full execution logs preserved long-term

### Example: Cross-Chain RWA Swap

Let's trace a real RWA trading recipe execution:

**Trigger**: CitiBank user wants to swap $100 Digital Gold for $100 Digital Silver with JPMorgan user

**Execution Flow**:

🔔 Event Detected\
└─ User initiates RWA swap request\
│\
▼\
🔐 Identity & Compliance\
└─ Privado ID verifies both users\
└─ Cube3 screens for sanctions/compliance\
│\
▼\
💎 Asset Verification\
└─ Space & Time validates Digital Gold ownership\
└─ Confirms Digital Silver availability\
│\
▼\
🔒 Cross-Chain Asset Locking\
└─ Digital Gold locked on CitiBank chain\
└─ Digital Silver locked on JPMorgan chain\
│\
▼\
⚡ Atomic Swap Execution\
└─ Simultaneous asset transfer\
└─ Space & Time records transaction proof\
│\
▼\
✅ Trade Complete\
└─ Users receive swapped assets\
└─ Cryptographic proof stored on-chain

**Result**: Cryptographically verifiable proof that $100 Digital Gold from CitiBank's private chain was atomically swapped for $100 Digital Silver from JPMorgan's private chain, with full identity verification, compliance screening, and cross-chain coordination.

### Intelligence in Action

Unlike static smart contracts that can only follow pre-programmed rules, W3.io recipes think and adapt during execution:

**Traditional Smart Contract Approach**

**The Problem**: Rigid, binary responses

* ❌ If condition not met → Execution fails
* ❌ If service unavailable → Hard stop
* ❌ One execution path for all scenarios

**W3.io Intelligent Recipe Approach**

**The Solution**: Adaptive, context-aware execution

**Example: Cross-Chain Asset Transfer During Network Congestion**

**Traditional Smart Contract:**

* Attempts to execute on Ethereum
* Gas fees are 200 gwei (extremely high)
* Result: Transaction fails or costs $500 in gas
* Process stops completely

**W3.io Recipe:**

* Detects high gas fees on Ethereum (200 gwei)
* Recipe adapts execution strategy:
  * Route through Polygon for lower fees
  * Bridge to destination chain
  * Complete transfer with 95% cost savings
* Execution succeeds with alternative path

**Traditional Approach:** Fixed execution path → failure when conditions aren't ideal

**W3.io Approach:** Dynamic execution path → adapts to network conditions in real-time

**Key Difference:**

W3.io recipes can evaluate multiple execution strategies and automatically select the optimal path based on current network conditions, rather than blindly following a single predetermined route.

**The Result**: Higher success rates and more cost-effective execution across varying network conditions.

### Network Coordination

The node network operates as a distributed system:

**Node Communication**

* **LibP2P networking**: Decentralized peer-to-peer communication
* **Event propagation**: Triggers broadcast across relevant nodes
* **State sharing**: Nodes synchronize recipe execution state
* **Result aggregation**: Multiple nodes contribute to final verification

**Task Distribution**

* **Recipe assignment**: Network automatically assigns recipes to capable nodes
* **Load balancing**: Work distributed based on node capacity and performance
* **Redundancy**: Critical operations executed by multiple nodes for reliability

### Verifiability Throughout

Every step is cryptographically verifiable:

**Execution Proof**

Each ingredient execution creates:

* **Input hash**: Cryptographic fingerprint of input data
* **Process hash**: Hash of the specific operation performed
* **Output hash**: Cryptographic fingerprint of results
* **Timestamp**: When the operation occurred
* **Node signature**: Which node performed the work

**Aggregated Proof**

Recipe completion generates:

* **Merkle tree**: All execution hashes combined into single proof
* **Consensus signatures**: Multiple nodes attest to correctness
* **On-chain record**: Immutable proof stored on blockchain
* **Verification data**: Anyone can verify the execution happened correctly

**Long-term Auditability**

* **Permanent storage**: Full execution logs on decentralized storage
* **Replay capability**: Entire recipe execution can be replayed and verified
* **Compliance reporting**: Automated generation of audit trails
* **Dispute resolution**: Cryptographic proofs resolve any execution disputes

### Network Effects

As the network grows, it becomes more powerful:

**More Ingredients = More Possibilities**

* **Composability**: New ingredients combine with existing ones
* **Innovation**: Novel recipes emerge from ingredient combinations
* **Specialization**: Ingredients optimized for specific use cases
* **Standards**: Common patterns emerge and become reusable templates

**More Nodes = Better Performance**

* **Better reliability**: More redundancy and failover options
* **Geographic distribution**: Nodes worldwide reduce latency
* **Specialized hardware**: Different nodes optimized for different workloads

**More Recipes = Network Intelligence**

* **Pattern recognition**: Network can learn optimal execution strategies
* **Performance optimization**: Historical data can improves future execution
* **Resource allocation**: Better matching of recipes to node capabilities
* **Cost efficiency**: Network automatically finds most cost-effective execution paths


# Cookbook

The W3 Cookbook is a strategic and technical guide developed by W3.io, presenting a modular library of perpetually growing “recipes”—composable blueprints that integrate services from various Web3 partners to create verifiable, scalable, and compliant blockchain-powered applications.

**Read the Cookbook**

[Link to Cookbook](https://docsend.com/view/i2euhvw7b2qbbrx5) / Password: **letscook**

## The Joy of Cooking

Why do you want to cook?  Cooking is designed to create the fastest path to value for developers in the industry. Not only do we make the development of intelligent apps simple, w3 also provide you a pathway to monetization that can be supported by our entire ecosystem. &#x20;

*W3 is confident that once you cook in our kitchen, you’ll never go anywhere else.*&#x20;

**Why Solutions Are Essential**

Solutions are the mechanism for driving utility, usage, and ultimately revenues for you, your L1 of choice, and the entire w3 ecosystem.&#x20;

* **Solution Payment*****:*** Solutions owners receive a predetermined margin as their service is used by the end user in USDC as well as a w3 token incentive.&#x20;
* **Ingredient Paymen*****t:*** The ingredients of each solution are paid in USDC based on their pricing model and usage.

**The Network Effects of Solutions - Your Own Salesforce**&#x20;

What Solutions ultimately enable is a dramatic increase in the number of individuals and organizations with a vested interest in selling your solution.

* **Ingredient Sellers*****:*** If a w3 Ingredient is included in your solution, they now have a vested interest in selling it.  If they sell it, they can earn the sales incentive on the front end while still earning based on solution usage.&#x20;
* **L1 Amplification*****:*** L1s are also incentivized to promote solutions that settle to their chain to their followers, driving organic pipeline growth.  &#x20;
* **The Ultimate Value*****:*** When a w3 Ingredient builds a recipe, builds a solution, and then sells it, it creates a windfall of revenue; the sales incentive, the solution margin, and their service usage all in perpetuity.  Where else does this exist?&#x20;

**Conclusion:** In every discussion with our network partners to date, we have yet to find a scenario where they would prefer to build or sell on their own versus through w3.   Cooking with w3 is more than just programmable intelligence and ease of development, it's about a path to perpetual monthly recurring revenue.&#x20;

W3's goal is to have the largest decentralized salesforce in the industry.


# Identity and Compliance

Web3, with its decentralized and blockchain-based nature, holds the potential to revolutionize how enterprises handle identity and compliance.

Identity solutions provide enhanced identity management through Self-Sovereign Identity (SSI), Decentralized Identifiers (DIDs), Zero-Knowledge Proofs (ZKPs). Improved compliance and security can be achieved through Immutable Records, Smart Contracts, Decentralization and cryptographic techniques.

By leveraging decentralized technologies, enterprises can build trust with their customers, streamline operations, and mitigate risks. However, it's essential to navigate the regulatory landscape and address technical challenges to fully realize the benefits of this emerging technology.&#x20;

W3.io facilitates the adoption of these technologies through its verifiable workflows (Recipes), tying together the best identity and compliance solutions to create a sum greater than its parts.


# Interoperable Identity

This recipe allows users to seamlessly integrate identity solutions into a larger trustless process while maintaining auditability and compliance requirements.

**Partners**

<div align="left"><figure><img src="/files/HL3Q7ifkA7mJDeAQrg1f" alt=""><figcaption></figcaption></figure></div>

* **Innerworks**: Validates initial user requests and provides user authentication.&#x20;
* **Trident3**: Manages identity requirement verification between platforms.&#x20;
* **Privado ID**: Provides secure credentialing and identity verification services.
* **Space & Time**: Coordinates the identity verification process and handles on-chain record keeping.&#x20;

**Example Use Case**\
\
An IRA retirement provider project (ETZ) is using Privado ID to verify users credentials and wants to interact with Franklin Templeton’s (FT) Benji platform which uses its own credentialing process. In this instance a ETZ user initiates a request to use USDC from its IRA to purchase Benji.

**Benefits**

* Seamless integration between different identity verification systems
* Maintains regulatory compliance across platforms
* Provides complete audit trail of identity verification
* Enables secure cross-platform transactions
* Preserves user privacy while ensuring compliance

**Sequence**

{% stepper %}
{% step %}
ETZ user initiates request - (assume user balances are verified).

{% endstep %}

{% step %}
Innerworks validates that the request comes from a known user.

{% endstep %}

{% step %}
Innerworks sends that validation to SxT.

{% endstep %}

{% step %}
SxT triggers a request asking Trident3 for FT’s Identity Requirements.

{% endstep %}

{% step %}
Trident3 sends the FT requirements to SxT and SxT verifies it has received them.

{% endstep %}

{% step %}
SxT triggers a request for Privado ID to provide the required credentialing.

{% endstep %}

{% step %}
Privado ID sends the required credentials to Trident3.

{% endstep %}

{% step %}
Trident 3 sends the required credentials to FT.

{% endstep %}

{% step %}
A summary of all of these actions, along with the verifications is batched and put on chain.

{% endstep %}

{% step %}
The ETZ user can now purchase Benji.

{% endstep %}
{% endstepper %}


# Enterprise Grade Compliance

This recipe allows users to meet compliance requirements by verifying the asset balances on both public and private chains while also checking relevant whitelists and blacklists.

**Partners**

<div align="left"><figure><img src="/files/nUUSgHCwoSfXzUjoPe71" alt=""><figcaption></figcaption></figure></div>

* **Cube3**: Manages compliance screening through whitelist/blacklist verification.
* **Jiritsu**: Validates underlying asset reserves using ZK MPC Cloud Core Technology.&#x20;

**Example Use Case**\
\
Diamond Standard wants to partner with JP Morgan (JPM) to enable the purchase of its Diamond Standard Coin (DSC) by JPM customers through the use of smart contracts. JPM needs to verify the underlying Diamond reserves along with ensuring that the seller of the DSC is compliant.

**Benefits**

* Automated compliance verification across multiple chains
* Real-time validation of underlying assets and reserves
* Comprehensive whitelist/blacklist screening
* Secure smart contract execution based on compliance checks

**Sequence**

{% stepper %}
{% step %}
JPM triggers a request from one of its users to purchase DSC from a different JPM user.

{% endstep %}

{% step %}
A smart contract is initiated,which sends a trigger to W3.

{% endstep %}

{% step %}
W3.io sends a request to Jiritsu to have it validate the underlying\
Diamond Reserves.

{% endstep %}

{% step %}
Jiritsu’s ZK MPC Cloud Core Technology verifies the underlying reserves and sends a message back to W3, yes/no.

{% endstep %}

{% step %}
If yes, W3.io sends a message to Cube3 to check the users for compliance.
{% endstep %}

{% step %}
Cube3 checks the users against its whitelists/blacklists and\
sends a message back to W3.io, yes/no.

{% endstep %}

{% step %}
W3.io batches the information and puts in on-chain.

{% endstep %}

{% step %}
The smart contract receives the on-chain data and either executes or doesn’t.

{% endstep %}
{% endstepper %}


# Real World Assets

RWA initiatives are poised to revolutionize the future of finance by transforming the way assets are created, traded, and managed. Tokenization simplifies complex financial transactions, reduces intermediaries, and democratizes investment opportunities, allowing individuals and institutions to engage in markets that were previously out of reach. By facilitating RWA use cases, ecosystems have the opportunity to engage with its enterprise user segment to create industry leading levels of liquidity, transparency, and accessibility.


# Multi-party Asset Rebalancing

This recipe allows Portfolio managers to automatically rebalance RWA’s according to predetermined formulas.

**Partners**

<div align="left"><figure><img src="/files/Xh0CGY1DNW9kqosohtNI" alt=""><figcaption></figcaption></figure></div>

* **Trident3**: Manages identity requirement verification between platforms.&#x20;
* **Space and Time**: Portfolio Model Storage and Performance Analytics.
* **Yelay**: Multi-chain Order Management and Trade Execution.
* **Innerworks**: Transaction Validation and Portfolio Reconciliation.
* **Privado ID**: Regulatory Compliance and Identity Management.

**Example Use Case**\
\
JP Morgan’s portfolio managers enable their customers to\
automatically rebalance RWA’s based off predetermined models.

**Benefits**

* Multi-layer verification and validation across all participating entities ensures secure cross-party transactions
* Real-time compliance checks and identity verification across multiple parties and jurisdictions
* Streamlined multi-party settlement process reduces operational overhead and settlement time
* Every step of the multi-party process is recorded on-chain with cryptographic proofs
* Easily add new parties and assets while maintaining security and performance

**Sequence**

{% stepper %}
{% step %}
An event triggers the rebalancing process. This could be a periodic review, a market condition change, or a manual action by the portfolio manager.

{% endstep %}

{% step %}
Identity Recipe - A version of the previously outlined Identity Recipe is used to re-verify the user's identity to ensure ongoing compliance with regulatory requirements. A successful result is batched, put on-chain, and a trigger for the rebalancing to continue is initiated.

{% endstep %}

{% step %}
A query is sent to SxT to identify the pre-defined characteristics of the rebalancing model.

{% endstep %}

{% step %}
SxT sends information about the rebalancing model to Yelay.

{% endstep %}

{% step %}
Yelay determines the respective buy/sell orders necessary to rebalance the account.

{% endstep %}

{% step %}
Yelay creates the trade orders specifying the assets to be bought or sold, the quantities, and the target prices, this information is then sent to SxT.

{% endstep %}

{% step %}
Yelay simultaneously submits the trade orders to the blockchain using smart contracts.

{% endstep %}

{% step %}
The smart contracts execute the buy/sell orders.

{% endstep %}

{% step %}
W3.io confirms that the trades have been executed successfully, batches the trade details, and puts them on-chain.

{% endstep %}

{% step %}
W3.io sends notifications to the portfolio manager and the investor about the completed trades and any changes to the portfolio.

{% endstep %}
{% endstepper %}


# Cross-chain Asset Interoperability

This allows users to operate as a clearinghouse for cross-chain assets interoperability across private and public chains.

**Partners**&#x20;

<div align="left"><figure><img src="/files/3OULzSaKChM7XlsKrKTh" alt=""><figcaption></figcaption></figure></div>

* **Layerzero**: Provides cross-chain messaging and communication infrastructure.
* **Space and Time**: Manages proof of SQL database, transaction logging, and orchestrates asset swap requests.&#x20;
* **Jiritsu**: Validates and verifies asset ownership on private blockchains.
* **Trident3**: Handles cross-chain asset verification and protocol compliance.
* **Yelay**: Manages asset locking and security mechanisms.&#x20;
* **Innerworks**: Coordinates identity verification processes across chains.
* **Privado ID**:  Provides secure identity verification and compliance solutions.

**Example Use Case**\
\
Citibank (CB) and JP Morgan (JPM) have both minted RWA’s on their private hyperledger based instances. Citi’s is a representation of gold and JP Morgan’s is a representation of silver. Both banks have userbases who own their respective assets. These users have accounts and have been verified, but only within one of the two banks.

**Benefits**

* Secure cross-chain asset transfers between private banking networks
* Automated identity verification and compliance checkins
* Real-time transaction logging with on-chain proof storage
* Synchronized asset locking across multiple chains
* End-to-end transaction verification and proof mechanisms

**Sequence**

{% stepper %}
{% step %}
A CB user (user 1) owns $100 worth of RWA gold (Dgold) and wants to buy RWA silver (Dsilver) with it.

{% endstep %}

{% step %}
Identity Recipe A version of the previously outlined Identity Recipe is used to verify the user s identity to ensure ongoing compliance with regulatory requirements. A successful result is batched and put on chain.

{% endstep %}

{% step %}
ID solution sends back an approved/ not approved message. Not approved comes with information detailing what else is needed.

{% endstep %}

{% step %}
User achieves approval this is sent to Space and Time (S\&T) and\
logged in the proof of SQL database.

{% endstep %}

{% step %}
S\&T sends a message to CB saying user 1 is approved and requests information about the assets involved.

{% endstep %}

{% step %}
CB sends to S\&T a request to swap $100 of Dgold for $100 of Silver.

{% endstep %}

{% step %}
S\&T logs the request and messages Jiritsu asking for proof of $100 of Dgold.

{% endstep %}

{% step %}
Jiritsu checks to see if user 1 has $100 of Dgold on the CB private blockchain.

{% endstep %}

{% step %}
Jiritsu sends S\&T a yes/no answer to the request for proof, which is logged.

{% endstep %}

{% step %}
If yes, then S\&T sends a message to JPM asking to swap $100 of Dgold for $100 of Dsilver which includes the necessary ID info so JPM can query for ID.
{% endstep %}

{% step %}
If JPM has a counterparty with $100 of Dsilver it triggers a request for ID on user 1 from the Identity Solution.

{% endstep %}

{% step %}
The Identity Solution sends user 1 information to JPM.

{% endstep %}

{% step %}
If user 1 ID info is approved, JPM sends User 2 information to the Identity Solution along with an approval record to S\&T.

{% endstep %}

{% step %}
The Identity Solution sends back an approved/ not approved message. Not approved comes with information detailing what else is needed.

{% endstep %}

{% step %}
User achieves approved - this is sent to Space and Time (S\&T) and logged in the proof of sequel database.

{% endstep %}

{% step %}
S\&T sends a message to JPM saying user 2 is approved and requests information about the assets involved.

{% endstep %}

{% step %}
JPM sends to S\&T a request to swap $100 of Dsilver for the $100 of Dgold.

{% endstep %}

{% step %}
S\&T logs the request and messages Jiritsu asking for proof of $100 Dsilver.

{% endstep %}

{% step %}
Jiritsu checks to see if user 2 has $100 of Dsilver on the JPM private blockchain.

{% endstep %}

{% step %}
Jiritsu send S\&T a yes/no answer to the request for proof, which is logged.

{% endstep %}

{% step %}
If yes, S\&T sends a message asking both CB and JPM to lock the\
requisite assets.

{% endstep %}

{% step %}
CB and JPM both send back proof of lock to S\&T.

{% endstep %}

{% step %}
S\&T records the asset locks along with the Identity of the owners.

{% endstep %}

{% step %}
S\&T hashes the records of the transactions and stores them on-chain.

{% endstep %}
{% endstepper %}


# Gaming

We believe that the mission to be the one-stop-shop platform for building and scaling mainstream-ready web3 games is an important one. As gamers ourselves we want a future where the games we play integrate digital assets, trustlessness, and better game economies. Our verifiable workflow protocol makes gameflow management easy. In the following recipes, see how we leverage our 40+ Network partners to bring additional functionality to gaming ecosystems.


# Transferring In-Game Assets On-Chain

This recipe provides a standardized process for securely transferring in-game assets, using a verifiable workflow that maintains integrity across both the gaming and blockchain environments.

**Partners**

<div align="left"><figure><img src="/files/kKDRkNUzXqoDUaTuj9mL" alt=""><figcaption></figcaption></figure></div>

* **iDOS**: Manages identity verification and credentials throughout the gaming transaction process.&#x20;
* **Cube3**: Provides security services and fraud prevention checks for all asset transfers.&#x20;
* **Privado ID**: Provides secure credentialing and identity verification services.
* **Space and Time**: Maintains game state storage and ensures synchronization between game world and blockchain.

**Example Use Case**\
\
When a player forges a new item in the game, the system verifies the transaction, handles the token payments, creates the appropriate NFT, and updates both the game world and blockchain records while maintaining security and verifiability throughout the process.

**Benefits**

* End-to-end transaction verification through comprehensive hashing
* Secure handling of both fungible and non-fungible tokens
* Seamless synchronization between game state and blockchain
* Immutable proof of ownership and transaction history

**Overview of Steps**\
\
When a player forges a new item in the game, a series of orchestrated steps are triggered to ensure the process is smooth, secure, and verifiable.&#x20;

**Sequence**<br>

Trigger: The forging event kicks off the recipe.

{% stepper %}
{% step %}
Verify: The event is verified through our decentralized network to ensure it’s legitimate.

{% endstep %}

{% step %}
Security: Additional security checks are performed to prevent fraud and ensure compliance.&#x20;

{% endstep %}

{% step %}
ERC-20 Token Handling: The cost of the item is verified as paid.

{% endstep %}

{% step %}
ERC-721 Transfer: The new item (an ERC-721 token) is created and transferred to the player's wallet.

{% endstep %}

{% step %}
Update Game World: The item is added to the player's inventory in the game.&#x20;

{% endstep %}

{% step %}
Hash Data: All relevant data is hashed in sequence to maintain integrity and provide a verifiable record.&#x20;

{% endstep %}

{% step %}
Merkle Tree Aggregation: The hashed data is aggregated into a Merkle tree structure for efficient verification.&#x20;

{% endstep %}

{% step %}
Record on Blockchain: The event is recorded on the blockchain, providing a transparent and immutable record of execution.&#x20;
{% endstep %}
{% endstepper %}

Verifiability: Throughout this process, every action (on-chain or off-chain) is hashed and logged, ensuring that each step can be verified. This builds trust and transparency, letting players know their transactions are secure and tamper-proof.


# Game Balance for NFT Assets

One example of that additional functionality is an analytics platform that leverages several of our partners (and would involve many of our recipes):

**Partners**

<div align="left"><figure><img src="/files/fSyYfoPh3X1UBVswT3rI" alt=""><figcaption></figcaption></figure></div>

* **Space & Time**: Ability to capture user telemetry.&#x20;
* **Covalent**: On-chain Indexin.&#x20;
* **Trident3**: User ID Passport.
* **Cube3**: Security Services.

**Example Use Case**\
\
A competitive gaming platform uses this analytics system to track NFT based character performance after each match. When a match completes, the system aggregates player performance data, updates NFT metadata for achievement milestones, checks player wallet reputations, and provides real-time analytics through admin and player dashboards, including how the NFT assets affect game balance.

**Benefits**

By combining these partners into an analytics platform, we can give games the ability to mesh in-game telemetry with on-chain activity, allowing for discovery around things like:

* NFT Trade Volume
* NFT Collections total value or changes in value
* NFT Asset In-Game performance
* Ownership data - EG: what are the top 3 similar NFT’s across users
* Transactional Data. NFT retention or attrition. EG: what did users buy after they bought or sold the NFT?
* Leaderboards matched with Token or NFT ownership
* Player whitelist/blacklists based on geography or toxicity
* Reward program participation matched to in-game behavior

**Sequence For Metrics Update**

Trigger: Match Completion initiates the analytics update via API.

{% stepper %}
{% step %}
Space and Time query for match data (players, NFT usage, performance).&#x20;

{% endstep %}

{% step %}
Covalent indexers queried for current match’s NFTs blockchain state.&#x20;

{% endstep %}

{% step %}
Player identities obtained through Trident 3's DID profiles.&#x20;

{% endstep %}

{% step %}
Player wallet addresses vetted through Cube3's reputation service -flagged if bad actor.&#x20;
{% endstep %}

{% step %}
W3.io aggregates the partner data into a normalized analytics package.

{% endstep %}

{% step %}
Space and Time provided analytics package to update player/NFT performance metrics.&#x20;

{% endstep %}

{% step %}
If achievement milestones are reached, NFT metadata is updated on IPFS/Filecoin.&#x20;

Dashboards: Players and game admins see updated player and NFT performance metrics in their respective dashboards.&#x20;
{% endstep %}
{% endstepper %}


# Restaking

Web3 aims to grow dramatically in scale and capability. To achieve this growth, many different services need to work with groups of validators (people/entities who help secure the network). Right now, each service tends to work independently, but we need more collaboration and shared solutions as the ecosystem expands.


# Restaking Analytics

There's no standard way to track and report how well validators are performing their duties. By creating and encouraging the use of a common method to measure and share this performance data, we can help services that rely on validators work more effectively and reliably.

**Partners**&#x20;

<div align="left"><figure><img src="/files/JlmA4EBPZdEvW4JJiqHZ" alt=""><figcaption></figcaption></figure></div>

* **Space & Time**: We can leverage Space and Time’s proof of SQL to store the rule sets governing rewards and penalties (for example: all transactions need to be processed in under X seconds).&#x20;
* **Lava**: We can use Lava Network to connect to blockchains in order to pull down the data we need about Operator actions.&#x20;
* **Cube3**: We can use Cube3 to get data about Operators in order to ensure interactions with whitelisted/blacklisted entities are occurring properly.

**Example Use Case**\
\
An Operator Set triggers a slashing event for an underperforming operator who failed to process transactions within the required time window. The system automatically aggregates the rule violations, pulls relevant blockchain data, checks the operator's reputation, and provides a comprehensive analytics package to a security provider like EigenLayer for transparent decision-making.

**Benefits**<br>

* Transparent rule enforcement through verified SQL-based governance
* Real-time monitoring of operator actions and performance metrics
* Automated compliance checking through reputation tracking
* Immutable on-chain record of all operator evaluations

**Sequence For Slashing Notification**

Trigger: An Operator Set triggers the slashing of an Operator.

{% stepper %}
{% step %}
Space and Time (SxT) aggregates the appropriate rules governing that event.

{% endstep %}

{% step %}
Lava Network pulls the appropriate on-chain information about the event and shares it with SxT.&#x20;
{% endstep %}

{% step %}
Cube3's vets Operator reputations - flagged if bad actor or on whitelist/blacklist.

{% endstep %}

{% step %}
W3.io aggregates the partner data into a normalized analytics package.&#x20;

{% endstep %}

{% step %}
Space and Time provided analytics package and updates Operator information.&#x20;

{% endstep %}

{% step %}
W3.io batches the analytics package along with the validated series of transactions and puts it on-chain.&#x20;

{% endstep %}

{% step %}
EigenLayer can pull all of the information from on-chain whenever needed.&#x20;

{% endstep %}
{% endstepper %}


# Node Network

The W3.io Prodigy Network is powered by a decentralized infrastructure of nodes that execute recipes, verify computations, and maintain the integrity of the system. Unlike traditional blockchain networks focused solely on consensus, our node network is optimized for computational tasks while ensuring verifiability and security.

This distributed network of compute resources forms the backbone of W3.io's ability to bridge on-chain and off-chain worlds, enabling complex business processes to execute with blockchain-level trust but without blockchain-level limitations.

The node network is designed to be inclusive, allowing various types of hardware to participate based on their capabilities, while maintaining the robust security and verifiability that web3 applications demand.

### Node Architecture

Each node operates using uniform core code, functioning as event-driven finite state machines optimized to minimize computational overhead not directly related to customer recipes.

**Core Components of a Node:**

* **LibP2P Networking Stack**: Facilitates robust decentralized connectivity
* **Core State Machine**: Manages node operations based on incoming events
* **Configuration System**: Flexible system tailored to hardware specifications
* **Metrics System**: Built-in performance monitoring and network participation tracking
* **Plugins**: Extensible functionality for hardware resources and new capabilities
* **Recipe Ingredients**: Storage and management of ingredients for recipe execution

### Node Types and Participation

**High Availability Nodes**: 99.999% uptime with advanced compute resources (TEEs, large capacity disks, high-performance CPUs)

**Normal Nodes**: Desktop-class computers with consistent online presence, occasional connectivity interruptions expected

**Community Nodes**: Intermittent connectivity devices (laptops, smartphones) contributing during non-use periods

All nodes participate as consensus peers, executing assigned tasks and contributing to network computational power and reliability.


# Knights

Knights are the core operational units within the W3.io network, serving as the decentralized execution layer for recipes. Each Knight contributes computing power to facilitate customer-defined business processes while maintaining cryptographic verification of all operations.

<figure><img src="/files/BZDjDCXNGzPp5tjAa4lG" alt=""><figcaption></figcaption></figure>

### Knight Participation

Knight Operators uphold the security of W3.io, earning rewards for decentralized verification and execution of recipe components. Starting from the testnet launch, anyone can rent or own a Knight, making it easier than ever to help scale programmable intelligence on Web3.

This democratic approach to node operation distinguishes W3.io from other systems that require costly specialized hardware or significant capital investment. By lowering barriers to entry, we ensure a more diverse, resilient network while creating economic opportunities for participants worldwide.

### Core Functions

Knights perform several critical functions within the network:

* **Recipe Execution**: Running the ingredients that make up recipes in response to triggers.
* **Consensus Participation**: Working with other Knights to verify the correctness of operations.
* **State Management**: Maintaining the state of variables within recipes during execution.
* **Verifiability**: Generating cryptographic proofs that operations were performed correctly.
* **Distributed Task Queue**: Participating in the decentralized task queue that distributes workloads.

### Technical Architecture

Each Knight operates based on a uniform core code implemented in Rust, structured as an event-driven finite state machine. This architecture is optimized for efficiency, security, and reliability, with components including:

* **LibP2P Networking Stack**: Facilitates node-to-node communication across the network.
* **Core State Machine**: Manages operations based on incoming events.
* **Configuration System**: Adapts to the hardware specifications of the node.
* **Metrics System**: Monitors performance and participation in the network.
* **Plugins**: Extends functionality based on available hardware resources.

### Knights Network

The Knights Network forms a mesh of interconnected nodes that collectively execute recipes. As shown in the diagram, when a recipe is deployed to the network:

1. The recipe file (depicted as a red document) is distributed to the network.
2. Relevant Knights form consensus groups to execute different parts of the recipe.
3. As execution progresses, verification occurs at each step (shown as checkmark icons).
4. Token rewards (depicted as dollar signs) are distributed to Knights based on their contributions.

This process ensures that complex workflows can be executed in a decentralized, verifiable manner while maintaining the performance characteristics needed for business applications.


# High Availability Nodes

High Availability (HA) Nodes represent the premium tier of Knights within the W3.io network, designed to offer enterprise-grade reliability with a target of 99.999% uptime ("five nines"). These nodes form the backbone of mission-critical operations where consistency and dependability are paramount.

#### Enhanced Capabilities

HA Nodes are equipped with advanced compute resources that may include:

* **Trusted Execution Environments (TEEs)**: Isolated execution spaces that protect sensitive computations.
* **Substantial Storage**: For handling large datasets and maintaining historical records.
* **High-Performance CPUs**: For rapid processing of complex computational tasks.
* **Redundant Systems**: To ensure continuity of service even during hardware failures.

#### Role in the Network

HA Nodes play several specialized roles within the W3.io ecosystem:

* **Critical Task Execution**: Handling the most sensitive or time-critical operations.
* **Secure Key Management**: Storing and managing cryptographic keys for transaction signing.
* **Automated Transaction Signing**: Performing fully automated, secure transaction signing.
* **Network Stability**: Providing a stable foundation for the entire Knights network.

#### Security Considerations

Security is paramount for HA Nodes, which incorporate multiple layers of protection:

* **Physical Security**: Deployment in secure data centers with controlled access.
* **Network Security**: Advanced firewalls and intrusion detection systems.
* **Cryptographic Security**: Robust key management and encryption protocols.
* **Audit Logging**: Comprehensive logging of all activities for accountability.

By providing this premium tier of service, HA Nodes ensure that even the most demanding enterprise applications can rely on the W3.io network for mission-critical operations, bridging the gap between traditional IT reliability expectations and the benefits of decentralized architecture.


# 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).&#x20;

At launch, approximately 20 key partners will operate individual [subnets](/network-model/network-model/ports), requiring them to stake W3 tokens.&#x20;

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.&#x20;

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.&#x20;

**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.


# Ports

From Day 1, W3’s model is designed to support strong token price fundamentals and sustainability by ensuring that the majority of distributed tokens are locked in structured staking, while demand for tokens continues to grow through network participation requirements.

Staking plays a crucial role in securing the network, driving adoption, and aligning incentives across all participants. Subnets and their communities rely on a staking mechanism that underpins network functionality and rewards active contributors.

To support long-term sustainability, W3 employs an ongoing emissions strategy:

* **Annual Rewards:** A significant amount of tokens will be distributed annually to subnet operators (and their communities), encouraging long-term participation and continual network expansion.  Critically, these rewards will be performance based, avoiding some of the issues other models have faced.
* **Long Term Scaling:** Over time, the number of subnets will increase, raising the amount of tokens required as stake, reinforcing network stability and growth.
* **Standards and Guidelines:** Subnet operators will have predefined guardrails on how much of their allocated tokens must be distributed to community participants, ensuring continuous engagement and incentive alignment.

Increased Demand: As more subnets are created, token demand naturally increases as does value creation, driving price appreciation through higher staking requirements.


# Token Model

A token model designed for crypto winter resiliency that drives long term lockups, where network revenues will flow to token owners.

W3.io introduces a next-generation token model that seamlessly integrates network revenue, staking incentives, and value creation towards long-term alignment. Unlike traditional token systems that rely on speculative demand, W3.io has designed a model where token ownership directly correlates with real world economic participation and transactions. By embedding programmable mechanics into value distribution, W3 ensures that partners, builders, and the community are rewarded proportionally to their contributions, sustaining a self-reinforcing growth cycle.

* **Network Revenue maps to Token Ownership:**  By incentivizing large amounts of the token supply to be locked up by participants doing jobs on behalf of the network we create a model where network revenue will flow to a large percentage of the token owners.
* **Dual Incentivization of Rewards and Revenue:** We will use native token rewards to jumpstart involvement and reward early participation while at the same time building towards long term revenue flows using stablecoins.
* **Significant Community Ownership:** We anticipate that 65-70% of the token supply will be distributed to network owners and their communities over time.  Roughly 20-25% will be assigned on day 1, giving the community a very significant stake.
* **Long Term Mindset:**  We will require significant lockup commitments for staking as well as a slow release schedule for the initial distribution.
* **Sell Disincentives & Redistribution:** If a partner or participant decides to sell their tokens during the initial holding time period, they forfeit the remainder of their initial stake, which is redistributed to long-term holders. This reinforces long-term holding behavior and rewards those who stay committed to the ecosystem.
* **Sustained Price Growth Mechanics:** A combination of staking requirements, subnet expansion, and redistribution of forfeited stakes ensures continuous demand for W3 tokens while limiting sell-side pressure, supporting upward price movement at launch and beyond.


# Network Economics

Efficient Network Revenue Distribution and Sustainable Tokenomics

W3.io is structured to support real economic transactions. By prioritizing revenue generation through actual usage, W3 aligns incentives among all network participants. Network members are compensated based on their contributions to ecosystem growth initially through token rewards and then eventually through the distribution of revenue.

To maintain a seamless and predictable economic model, W3.io has:

* **Simplified Payments:** Payments and revenue flows are handled in stablecoins or fiat, ensuring financial predictability for businesses and partners.
* **Programmable Distribution:** Automated payment waterfalls simplify payouts, ensuring that partners, subnet operators, and contributors receive their earnings efficiently.
* **Sales Incentives:** Partners are empowered to generate revenue by selling solutions within the W3 ecosystem rather than through fragmented independent channels, reinforcing network value.
* **Minimized Sell-Side Pressure:** Staking requirements, network lockups, and redistribution of forfeited stakes reduce the number of tokens available for sale, creating scarcity and driving demand.
* **Organic Buy Pressure:** Partners and participants must acquire tokens to stake and unlock revenue opportunities creating a continuous demand which supports price stability and appreciation.

By structuring revenue distribution this way, W3.io removes unnecessary inefficiencies while ensuring long-term economic alignment between all stakeholders.


# Ecosystem Overview

W3.io is an industry consortium consisting of Web 3’s top off-chain compute projects and L1/L2 ecosystems. W3.io’s long-term objective is to increase the total addressable market for Web 3 compute and blockchain ecosystems by operating a full stack and community governed decentralized AWS equivalent. &#x20;

In addition to the community, the W3.io ecosystem has three primary segments: &#x20;

1. [Network partners ](/ecosystem/network-partners)
2. Governance Board (TBA)&#x20;
3. End users (TBA)


# Network Partners

A W3 Network Partner is a leading infrastructure or service provider whose technology is integrated into W3.io’s modular ecosystem as a reusable [ingredient](/tech-design/ingredients). These partners enable verifiable workflows—called [recipes](/recipes)—that address complex, cross-chain, enterprise-grade challenges such as identity verification, compliance, data storage, asset interoperability, AI compute, and more.

## Why Become a W3 Network Partner

Joining the W3 Network offers clear and compelling benefits to infrastructure providers across the decentralized ecosystem. W3 expands your Total Addressable Market (TAM) and opens new customer acquisition channels that aren’t possible through isolated, direct-to-market efforts.

**Core Value Proposition**

Network Partners gain the ability to interoperate with other decentralized services, increasing composability and enabling bundled solutions that deliver more value to end users.

Many core services in Web3—like decentralized AI agents, GPU compute, and ZK-based validators for AI—are not currently interoperable. W3 makes this integration possible. When these resources can be composed together, every player in the stack benefits.

**Economic Incentives for Network Partners**

* No Channel Fees for Decentralized Compute Providers
  * Compute providers earn the same margins through W3 as they would selling directly.
  * We eliminate disincentives and make protocol-based delivery economically neutral (or better).
* Access to Bundled Service Opportunities
  * W3 enables partners to sell integrated packages of services.
  * Web3-native companies currently spend $500M–$1B annually on centralized IT services—W3 unlocks this spend for decentralized alternatives.
  * Bundling expands the TAM for each partner. *For example: A data protocol can now bundle with compute, storage, or compliance services.*
  * Edge and base compute can combine to serve broader enterprise needs.
* W3 Grows the Market with Strategic Support
  * *Treasury Subsidies*: W3 will use its treasury to subsidize usage of decentralized compute services.
  * *Segment Advocacy*: We actively promote the benefits of decentralized infrastructure across the broader IT and enterprise landscape.
  * *Ecosystem Activation*: W3 demonstrates the real-world viability of decentralized stacks by building and showcasing production-grade applications.

*W3 doesn’t just connect services—we connect opportunity.*


# Core Initial Network Partners

While W3.io is structured as a neutrual industry utility, we will partner with core partners initially to demonstrate the viability of our model. The table below highlights the partners that are currently partnering most closely with on the initial reference implementations. &#x20;

<table data-header-hidden><thead><tr><th>Partner </th><th>Segment</th><th data-hidden></th></tr></thead><tbody><tr><td>Partner</td><td>Segment</td><td></td></tr><tr><td>Altlayer</td><td>RaaS</td><td></td></tr><tr><td>Avail</td><td>Data availability </td><td></td></tr><tr><td>Babylon</td><td>Shared security </td><td></td></tr><tr><td>Covalent</td><td>Indexing</td><td></td></tr><tr><td>Eigenlayer</td><td>Shared security </td><td></td></tr><tr><td>Filecoin</td><td>Storage</td><td></td></tr><tr><td>LayerZero</td><td>Cross chain messaging</td><td></td></tr><tr><td>Lit Protocol</td><td>Access management and TEE</td><td></td></tr><tr><td>Space &#x26; Time</td><td>Data warehouse </td><td></td></tr><tr><td>Pyth</td><td>Price and date feeds</td><td></td></tr><tr><td>Render</td><td>GPUs/CPUs</td><td></td></tr></tbody></table>


# Additional Network Partners

The W3.io network partner eocsystem consists of 60+ off-chain compute projects across the following segments: &#x20;

1. [Data & Storage](/ecosystem/network-partners/additional-network-partners/data-and-storage)
2. [AI/ML + Compute](/ecosystem/network-partners/additional-network-partners/ai-ml-+-compute)
3. [Identity + Access](/ecosystem/network-partners/additional-network-partners/identity-+-access)
4. [Integration Middleware](/ecosystem/network-partners/additional-network-partners/integration-middleware)
5. [Economic Security](/ecosystem/network-partners/additional-network-partners/economic-security)
6. [RPC](/ecosystem/network-partners/additional-network-partners/rpc)
7. [Network Comms](/ecosystem/network-partners/additional-network-partners/network-comms)


# Data & Storage

<table data-view="cards" data-full-width="false"><thead><tr><th></th><th data-hidden data-type="files"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>0G Labs</td><td><a href="/files/G1rmJAPXJWOElO3b3Qbz">/files/G1rmJAPXJWOElO3b3Qbz</a></td><td><a href="/files/Tz6T2qsbiadJbxjbqk7N">/files/Tz6T2qsbiadJbxjbqk7N</a></td></tr><tr><td>AltLayer</td><td><a href="/files/iOWN5TcghaKzpTV0yAc6">/files/iOWN5TcghaKzpTV0yAc6</a></td><td><a href="/files/77KnaLRSTRA00COVShzQ">/files/77KnaLRSTRA00COVShzQ</a></td></tr><tr><td>API3</td><td></td><td><a href="/files/zvQLUPlnb07NLSFoaTtl">/files/zvQLUPlnb07NLSFoaTtl</a></td></tr><tr><td>Ceramic</td><td></td><td><a href="/files/p5M0m7ngm2Eu0GUcDrNw">/files/p5M0m7ngm2Eu0GUcDrNw</a></td></tr><tr><td>Chaos Labs</td><td></td><td><a href="/files/OMlhBOGEaf7TcPBuDpXF">/files/OMlhBOGEaf7TcPBuDpXF</a></td></tr><tr><td>Covalent</td><td></td><td><a href="/files/dglYBmFaGfVAZwGqe75x">/files/dglYBmFaGfVAZwGqe75x</a></td></tr><tr><td>Cube3</td><td></td><td><a href="/files/petFNKwNdGBo7QVvmRId">/files/petFNKwNdGBo7QVvmRId</a></td></tr><tr><td>Flipside Crypto</td><td></td><td><a href="/files/ItgpJuC4kmFQWXt3Cmfe">/files/ItgpJuC4kmFQWXt3Cmfe</a></td></tr><tr><td>Gelato</td><td></td><td><a href="/files/tBLly2uDGJ7g4qEcMvqS">/files/tBLly2uDGJ7g4qEcMvqS</a></td></tr><tr><td>Jiritsu</td><td></td><td><a href="/files/pMpoq08Khqqn4sVWMkvu">/files/pMpoq08Khqqn4sVWMkvu</a></td></tr><tr><td>Kwil</td><td></td><td><a href="/files/KC3MTNlHCCd8dKQO9ZW3">/files/KC3MTNlHCCd8dKQO9ZW3</a></td></tr><tr><td>Kyve</td><td></td><td><a href="/files/YaT8pr1SNdrkFBz9omsW">/files/YaT8pr1SNdrkFBz9omsW</a></td></tr><tr><td>Lighthouse</td><td></td><td><a href="/files/XXcdQWZoFz5TDg1xth4j">/files/XXcdQWZoFz5TDg1xth4j</a></td></tr><tr><td>Nil Foundation</td><td></td><td><a href="/files/YFAS5xmDEejHWYfsiAQX">/files/YFAS5xmDEejHWYfsiAQX</a></td></tr><tr><td>Nillion</td><td></td><td><a href="/files/mlE8Fnb7KKF8kghdC7Bg">/files/mlE8Fnb7KKF8kghdC7Bg</a></td></tr><tr><td>Pyth</td><td></td><td><a href="/files/64WhTCaQ4an2KconZMrM">/files/64WhTCaQ4an2KconZMrM</a></td></tr><tr><td>Risc Zero</td><td></td><td><a href="/files/ARDsZ0iQdhqSt3if8kPS">/files/ARDsZ0iQdhqSt3if8kPS</a></td></tr><tr><td>Space &#x26; Time</td><td></td><td><a href="/files/CM5XDt7l941Mc5eyZxhg">/files/CM5XDt7l941Mc5eyZxhg</a></td></tr><tr><td>Spheron</td><td></td><td><a href="/files/cS6YWQoKptoE45q7Cj9q">/files/cS6YWQoKptoE45q7Cj9q</a></td></tr><tr><td>Synternet</td><td></td><td><a href="/files/7FrT6Xq8sFh9R1REdpzH">/files/7FrT6Xq8sFh9R1REdpzH</a></td></tr><tr><td>W3bstream</td><td></td><td><a href="/files/iqSBikzesbdh5YOqyASu">/files/iqSBikzesbdh5YOqyASu</a></td></tr><tr><td>ZettaBlock Labs</td><td></td><td><a href="/files/Y0R7f8YtuA8otfsqZvoD">/files/Y0R7f8YtuA8otfsqZvoD</a></td></tr></tbody></table>


# AI/ML + Compute

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Akash</td><td><a href="/files/LxbNYBm3hxa1ygnsAmn4">/files/LxbNYBm3hxa1ygnsAmn4</a></td></tr><tr><td>Allora</td><td><a href="/files/zZBaGe1oeI78Uj5X7gOL">/files/zZBaGe1oeI78Uj5X7gOL</a></td></tr><tr><td>Eternis</td><td><a href="/files/Rgl62JqWc1v4aEhJZqCD">/files/Rgl62JqWc1v4aEhJZqCD</a></td></tr><tr><td>Fluence</td><td><a href="/files/YbnjFPFfOrG9rpydPvfd">/files/YbnjFPFfOrG9rpydPvfd</a></td></tr><tr><td>Gensyn</td><td><a href="/files/hBDATmy8f58CZwisf283">/files/hBDATmy8f58CZwisf283</a></td></tr><tr><td>Giza</td><td><a href="/files/o2Sk2iDFgh6JDMp0HmcX">/files/o2Sk2iDFgh6JDMp0HmcX</a></td></tr><tr><td>Hyperbolic</td><td><a href="/files/4YQM8hNcC9mfAANvRiar">/files/4YQM8hNcC9mfAANvRiar</a></td></tr><tr><td>KiteAI</td><td><a href="/files/vvTI6ItLOTdvvfzEKuUy">/files/vvTI6ItLOTdvvfzEKuUy</a></td></tr><tr><td>Render</td><td><a href="/files/QdMmPm6sidVbcY2kYibC">/files/QdMmPm6sidVbcY2kYibC</a></td></tr><tr><td>Ritual</td><td><a href="/files/vF3h53eMqTcTskNJWuP0">/files/vF3h53eMqTcTskNJWuP0</a></td></tr><tr><td>Theoriq</td><td><a href="/files/NMQY5YUsTWSZiEdf5Y9v">/files/NMQY5YUsTWSZiEdf5Y9v</a></td></tr></tbody></table>


# Identity + Access

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Cubist</td><td><a href="/files/1pR4mnzG5InorY9cPRuI">/files/1pR4mnzG5InorY9cPRuI</a></td></tr><tr><td>idOS</td><td><a href="/files/QYW4sKylH0SbdgwtHSWl">/files/QYW4sKylH0SbdgwtHSWl</a></td></tr><tr><td>Lit</td><td><a href="/files/sDP0nFK7ZE0CLbmb574V">/files/sDP0nFK7ZE0CLbmb574V</a></td></tr><tr><td>SpruceID</td><td><a href="/files/blEndYvhhjeFnTRyPhc6">/files/blEndYvhhjeFnTRyPhc6</a></td></tr></tbody></table>


# Integration Middleware

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Avail</td><td><a href="/files/u0fxInZcR21Apg78uzG9">/files/u0fxInZcR21Apg78uzG9</a></td></tr><tr><td>Axelar</td><td><a href="/files/y6b7cEgPg7VL9Ep9R1La">/files/y6b7cEgPg7VL9Ep9R1La</a></td></tr><tr><td>Layerzero</td><td><a href="/files/AYTpLSt8Zun2il7kGjQU">/files/AYTpLSt8Zun2il7kGjQU</a></td></tr><tr><td>Yelay</td><td><a href="/files/umKlcRw5Pg9o3vDj8dlO">/files/umKlcRw5Pg9o3vDj8dlO</a></td></tr><tr><td>zkPass</td><td><a href="/files/sdmKbifQHuWrp8zddpsW">/files/sdmKbifQHuWrp8zddpsW</a></td></tr></tbody></table>


# Economic Security

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Babylon</td><td><a href="/files/XPx0M1360uEIi6yBWkqZ">/files/XPx0M1360uEIi6yBWkqZ</a></td></tr><tr><td>EigenLayer</td><td><a href="/files/NIVhEFBzPtfX3MqQYmlB">/files/NIVhEFBzPtfX3MqQYmlB</a></td></tr></tbody></table>


# RPC

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Lava</td><td><a href="/files/6rTaY9VboYPzosH3MSYV">/files/6rTaY9VboYPzosH3MSYV</a></td></tr><tr><td>dRPC</td><td><a href="/files/PbUOwwTaroypKFXELi1J">/files/PbUOwwTaroypKFXELi1J</a></td></tr></tbody></table>


# Network Comms

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Fleek</td><td><a href="/files/nvc8KGHUI3GxTUeED9nM">/files/nvc8KGHUI3GxTUeED9nM</a></td></tr><tr><td>Notifi</td><td><a href="/files/s8d8pAhbFoZvgy2bcM24">/files/s8d8pAhbFoZvgy2bcM24</a></td></tr></tbody></table>


# Governance Board

The Governance Board is not just a strategic layer—it’s a bridge between W3.io and the builders who need us most. The L1s/L2s that sit on the W3.io Governance Board play an instrumental role in the network by helping define standards and providing distribution channels for W3.io's recipes. &#x20;

Governance Board members are instrumental in driving growth and impact across W3.io in several ways:

1. They connect projects to solutions. Members can bring in ecosystem projects from their own protocols that need support—whether that’s technical, architectural, or strategic—and offer them access to W3.io’s solutions.
2. &#x20;They help onboard projects to the network. By introducing new teams and use cases, Governance members help grow the network with real-world adoption and active users.
3. They provide critical feedback and guidance. As active voices at the table, they shape how our protocol evolves—offering input that ensures W3.io remains aligned with the needs of the broader EVM-compatible ecosystem.
4. They accelerate integration and alignment. Their involvement helps ensure faster and more effective adoption of W3.io within their own networks and beyond.


# Pipeline

Confirmed:&#x20;

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Avalanche</td><td><a href="/files/1rOmUfbz3Nn2ozCgojEF">/files/1rOmUfbz3Nn2ozCgojEF</a></td></tr><tr><td>Linea</td><td><a href="/files/qpttdR1r9ysT43THTTeu">/files/qpttdR1r9ysT43THTTeu</a></td></tr></tbody></table>

Late Stage Discussions:&#x20;

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Arbitrum</td><td><a href="/files/8A2C3mdA4jMAEPthtdYd">/files/8A2C3mdA4jMAEPthtdYd</a></td></tr><tr><td>Hedera</td><td><a href="/files/LyNNO3qOd5VqKz55pr6H">/files/LyNNO3qOd5VqKz55pr6H</a></td></tr><tr><td>Mantle</td><td><a href="/files/RZpk4p7HlTSbK9Ztjcxa">/files/RZpk4p7HlTSbK9Ztjcxa</a></td></tr><tr><td>Base</td><td><a href="/files/kJRhGhHWg0Xq778PBXQb">/files/kJRhGhHWg0Xq778PBXQb</a></td></tr><tr><td>Berachain</td><td><a href="/files/yPR3TXROidFzuBJcBClP">/files/yPR3TXROidFzuBJcBClP</a></td></tr><tr><td>Monad</td><td><a href="/files/ON0O2UxFpBZbii4qvcW1">/files/ON0O2UxFpBZbii4qvcW1</a></td></tr><tr><td>Optimism</td><td><a href="/files/nUJr6BF629qd7vx6Mulf">/files/nUJr6BF629qd7vx6Mulf</a></td></tr><tr><td>Polygon</td><td><a href="/files/VdDiuks9Q5Qasf6uo4CD">/files/VdDiuks9Q5Qasf6uo4CD</a></td></tr></tbody></table>


# End Users

W3.io has achieved clear product market fit as evidenced by the fact that we identify interesting use cases in virtually 100% of the calls we have with projects teams.  W3.io is currently in the process of implementing a range of high impact use cases across top tier customers. We are currently focused on delivering and harding these solutions in the context of POCs in preparation of scaling them up to an additional 5-10 customers.  &#x20;

<div align="left"><figure><img src="/files/FgK8z9u5u061wgA06vJS" alt="" width="250"><figcaption></figcaption></figure></div>

### A. Creatorland

* Description: Multi-agent deal management solution
* End User: Creators
* Chain: Avalanche
* Partners: Space and Time, KiteAI, Hyperbolic
* Reason: Multi-agent AI

<div align="left"><figure><img src="/files/t59kHj0IiXuzPYf1Ea9C" alt="" width="250"><figcaption></figcaption></figure></div>

### B. Gaia

* Description: Agent training, fine-tuning, and update automation
* End User: Gaia Domain Operators, Data Scientists
* Chain: Ethereum
* Partners: Gaia, Space and Time, Lit Protocol
* Reason: Easy, automated LLM hosting

<div align="left"><figure><img src="/files/JmPBc6uqhNQnQ8iKBgwi" alt="" width="250"><figcaption></figcaption></figure></div>

### C. Ireland Pay

* Description: Crypto payment solution for traditional PSPs and merchants
* End User: Ireland Pay
* Chain: Avalanche
* Partners: Versal, EigenLayer
* Reason: Fiat/Crypto payments

<div align="left"><figure><img src="/files/zjgEAorreG5GwkXPSXyH" alt="" width="250"><figcaption></figcaption></figure></div>

### D. Malda

* Description: Aggregation of data streams with AI-driven asset risk inference
* End User: Data providers
* Chain: Linea
* Partners: Space and Time, KiteAI, Brevis, Yelay
* Reason: Asset risk management

<div align="left"><figure><img src="/files/xjDKNGIqJfzOSrxy8Hxx" alt="" width="250"><figcaption></figcaption></figure></div>

### E. Plume

* Description: Tools for TradFi to trade RWAs in compliance
* End User: Financial institutions
* Chain: Plume
* Partners: Privado ID, Space and Time, Cube3
* Reason: RWA cross-chain transactions

<div align="left"><figure><img src="/files/CM5XDt7l941Mc5eyZxhg" alt="" width="250"><figcaption></figcaption></figure></div>

### F. Space and Time

• Description: Treasury management automation

• End User: Space and Time / Others

• Chain: Multi-chain

• Partners: EigenLayer, Space and Time, Pyth

• Reason: Treasury management

<div align="left"><figure><img src="/files/SGxvbLVzUdZiB0HSdE3R" alt="" width="250"><figcaption></figcaption></figure></div>

### G. XAI

* Description: Intelligent game analytics for Web3 games
* End User: Games
* Chain: XAI (Arbitrum)
* Partners: Space and Time, Covalent, Pyth, KiteAI
* Reason: Gaming analytics


# Market Positioning

W3.io is an industry consortium consisting of Web 3’s top off-chain compute projects and L1/L2 ecosystems. In Web 2 our direct competitors are the large cloud providers (GCP, Azure, etc). Since we are a neutral entity that’s organizational purpose is to increase the total addressable market for Web 3 compute and blockchain ecosystems, we have no direct or indirect competitors in Web 3 currently.

### **TL;DR**&#x20;

W3.io’ is the Chainlink killer. &#x20;

### **Key Takeaways**

* **Chainlink** dominates in **oracles and secure data feeds space;** critical for DeFi.  However, they are too focused on DeFi and on becoming a SWIFT replacement, ignoring high TAM use cases such as RWAs and AI.  &#x20;
* **Chainlink is not intelligent.**  Working off external non-verified data feeds, Chainlink is a 2D model and is limited in its ability to address complex workflows at scale.  W3.io is designed to be 3D model that can support autonomous multi-party transactions bridging both on-chain and off. &#x20;
* **Chainlink works to benefit Chainlink not the industry.**  Whereas w3 works to benefit the entire Web3 ecosystem with easy value creation, revenues, end-user adoption, and next-generation utility.

### Breakdown

W3.io’s long-term objective is to increase the total addressable market for Web 3 compute and blockchain ecosystems by operating a full stack and community governed decentralized AWS equivalent. As the default layer by which organizations large and small will interface with on-chain workflows, W3.io has the potential to achieve business outcomes that are much larger in scope to even the most mature Web 3 infrastructure projects. The table below outlines differences between Chainlink and W3.io. Whereas the Chainlink network is designed to deliver workloads created by Chainlink Labs, W3.io’s objective is to create business and IT functionality by providing the out-of-the box intelligence and seamless two-way business automation for complex onchain workflows required to optimize the decentralized tech stack.&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Topic</strong></td><td valign="top"><strong>Chainlink</strong></td><td valign="top"><strong>W3.io</strong></td></tr><tr><td valign="top">Organizational purpose</td><td valign="top">Maximize adoption of the Chainlink network</td><td valign="top">Increase the total addressable market for Web 3 compute and blockchain ecosystems through the establishment of standards, promotion of technological interoperability, and making on-chain development easier and better</td></tr><tr><td valign="top">Economic focus</td><td valign="top">Maximize economic value that accrues to the Chainlink network</td><td valign="top">Maximize economic value that flows to the off-chain compute segment and blockchain ecosystems</td></tr><tr><td valign="top">Ecosystem participants</td><td valign="top"><p>-End users</p><p>-Chainlink node operators</p><p>-Chainlink Labs</p><p>-Chainlink community</p></td><td valign="top"><p>-End users</p><p>-W3.io node operators</p><p>-Every projects in the off-chain compute stack (40+ currently)</p><p>-Top L1/L2 blockchain ecosystems</p><p>-Communities associated with all of the top off-chain compute projects and leading blockchain ecosystems</p></td></tr><tr><td valign="top">Ceiling for community growth</td><td valign="top">Need to take mindshare away from other off-chain compute projects</td><td valign="top">Can engage with virtually every Web 3 community since makes Web 3 stronger as an industry</td></tr><tr><td valign="top">Technological offerings</td><td valign="top"><p>-Price and data feeds</p><p>-Verifiable randomness</p><p>-Cross-chain messaging</p><p>-Automation</p></td><td valign="top"><p>Full stack suite of decentralized technological offerings with multiple providers per segment including (abridged list):</p><p>-Price and data feeds</p><p>-Cross-chain messaging</p><p>-Automation</p><p>-GPUs</p><p>-CPUs</p><p>-Trusted execution environments</p><p>-Identity </p><p>-AI agents</p><p>-AI </p><p>-Data warehouse</p><p>-Indexing</p><p>-Identity</p><p>-Smart contract security</p><p>-Key management</p><p>-Economic security </p><p>-Edge computing</p><p>-RPC</p></td></tr><tr><td valign="top">Developer acquisition strategy</td><td valign="top"><p>-Acquire individual developers</p><p>-Sign up individual projects</p></td><td valign="top">-Provide an open source technological stack that infra providers, blockchain ecosystems and</td></tr><tr><td valign="top">Monetization model</td><td valign="top"><p>-Charge projects</p><p>-Charge ecosystems large integration fees</p></td><td valign="top"><p>-Serve as reseller for all the major cloud providers (AWS, GCP, Azure) and take 5-20% channel fee (current TAM of $1B)</p><p>-Accrue a portion of the transaction fee from the node network</p><p>-Annual membership fees from L1s/L2s</p></td></tr><tr><td valign="top">Competitive moats</td><td valign="top"><p>-Reputation in the industry</p><p>-Existing relationships</p></td><td valign="top"><p>-First mover advantage</p><p>-Neutral industry utility – no margin for competitor to take if they enter market</p><p>-Setting and maintaining technological interoperability standard – strong benefits for participation, high costs to non-participation at steady state</p><p>-Primary industry mechanism for the distribution of decentralized IT services</p><p>-Index on the industry – if the industry wins, we win</p></td></tr><tr><td valign="top"><br>Final takeaway</td><td valign="top"><br>Chainlink is ripe for distruption.</td><td valign="top"><br></td></tr></tbody></table>

<br>


# Network Effects - Solutions & Sales

The purpose of w3 is to align our ecosystem towards the building of solutions as well as increasing the number of sellers committed to growing pipeline in order to drive end-user adoption.

**Solution Definition Refresher:** Solutions are 1 or more recipes configured into an end user’s IT environment. In short, a recipe (or combination of recipes) graduates to being a solution when the necessary customizations happen for it to go live in an end users’ IT environment.

## Why Solutions Are Essential

End users want *better, cheaper, faster.* What they don’t want are disparate pieces of technology that they need to configure and manage.  Solutions are the pathway to driving utility, usage, and ultimately revenues for their creators as well as the entire w3 ecosystem.  &#x20;

**Why Everyone Wants to be a Solution Builder**

Creating solutions are the best way to drive revenues, cashflows and usage to your project.  Solutions owners get a predetermined margin in USDC as well as a w3 token incentive. Solution Ingredients are automatically paid out based on their pricing model and usage. So if you are the solution owner and one of the ingredients,  you earn more. Both payments and rewards will continue in perpetuity as long as usage continues.&#x20;

## Network Effects of Solutions&#x20;

What Solutions ultimately enable is a dramatic increase in the number of individuals and organizations with a vested interest in selling your solution.

* ***Cash makes the King:*** When W3 is the home for the most end to end user solutions and composable recipes, we will attract an army of both builders and sellers who are looking for adoption and revenue generation.
* ***Ingredient Sellers:*** If a w3 Ingredient is included in your solution, they now have a vested interest in selling it.  If they sell it, they can earn the sales incentive on the front end while still earning based on solution usage.&#x20;
* ***L1 Amplification***: L1s are also incentivized to promote solutions that settle to their chain to their followers, driving organic pipeline growth.  &#x20;
* ***The Ultimate Value***: When a w3 Ingredient builds a recipe, builds a solution, and then sells it, it creates a windfall of revenue; the sales incentive, the solution margin, and their service usage in perpetuity.  Where else does this exist?&#x20;

## Great Solutions Attract Sellers

Quality solutions that solve real world problems combined with residual incentives and w3's ease of use are also what will attract an army of sellers to w3.  Why:

* ***Cutting Edge Solutions:***  Sellers want access to the *next big thing* in order to gain access to decision makers and budgets.  W3 solutions will get them both.  &#x20;
* ***Customer Ownership:***  Sellers are able to maintain their end user relationships (versus handing them off) in order to continue to up-sell/cross sell into the future. &#x20;
* ***Residuals:***  As long as the solution is being consumed, the seller receives a token incentive in perpetuity.  &#x20;
* ***Ease of Use***: With w3, sellers don't need to worry about payments or procurement. They can go straight to sales and account management via their own single-pane of glass dashboard. &#x20;

Currently, there is no other platform in web3 offering a single-pane of glass management console along with residual payments to those who drive user adoption and revenue. &#x20;


# Solutions Roadmap

Our goal is to showcase the value of solutions so that the ecosystem intimately understand why and how to build them on their own.

***Phase 1 - W3 Built & Pilot Solutions (TestNet) 0-6 Months:*** In Phase1, w3 is owning all solution development in order to be able to demonstrate to our community *How Solutions Work* and *Why Everyone Should Want to Build Them.*  Additionally, owning the first wave of solutions ensures that all workflows, payment transfers, verifiability, and rewards flow according to the network's design prior to MainNet launch.

***Phase 2 - Strategic Partner Solutions (MainNet Launch):*** In Phase2, w3 will guide our first 20 strategic partners through their initial solution creation processes in order to have a single solution available per partner.   W3 will use this period to hone documentation, processes, Solution Creation sandboxes, and dashboards to refine requirements on what features, tools, and dashboards are needed for scale.

***Phase 3 - Ecosystem Built Solutions (MainNet):*** In Phase3, w3 will open up solution development for the entire community by providing the tools, sandboxes, documentation, subnets, and incentives structures as well as the full suite of recipes and ingredients for solution inclusion.  &#x20;


# Sales Roadmap

With sales, our goal is to create immediate wins and cash flows for our founding partners to anchor their engagement as well as to enable the largest salesforce in web3.

***Phase 1 - W3 Sold Solutions (TestNet):*** In Phase1, w3 will own the majority of sales initiatives in order to be able to demonstrate to our community *How and Why Everyone Should Sell.* During this stage, w3 can demonstrate how revenue flows downstream, how solutions drive usage for our ingredient partners and how token incentives work within the platform. &#x20;

***Phase 2 - Ingredient Sales (MainNet Launch):*** In Phase2, w3 will guide ingredient partners to sell the solutions they are a part of.  This will naturally increase the number of sellers, pipeline, and usage for each respective solution where each ingredient partner knows exactly how value will flow to them based on consumption.  This Phase will also be essential for demonstrating how our ingredients can earn both on the front (sales) and backend (ingredient) for each solution they are involved in. &#x20;

***Phase 3 - Ecosystem Sales (MainNet):*** In Phase3, w3 will open up solution sales for the entire community by supporting solution owners to create sales enablement packets, documentation, and messaging tools to facilitate deal closures.  Special focus will be provided by w3 in recruiting Managed Service Providers (MSPs),  Global System Integrators (GSIs), and members of our Strategic L1 communities to help push solutions to market in order to grow pipeline.


# Revenue Model

The W3.io protocol will have a token and we anticipate that the financial value will accrue exclusively to the token (vs. the equity). While we have multiple paths to generating revenue, our primary focus at the outset will be on convening the network and getting market share.  We are in the process of scaling the business and plan to achieve the following metrics by the end of 2025 (as outlined in the table below).&#x20;

Over time W3.io’s platform as a service business model can generate revenue in the following ways:

●     Transaction fee on the node network: The Labs organization will receive a portion of the transaction fee that the network charges.&#x20;

●     Channel fee from reselling centralized IT services from AWS, GCP, and Azure: We estimate that Web 3 native companies spend $1B on centralized IT services.  We will serve as a reseller for centralized IT services, collecting a 5-20% fee.&#x20;

●     Membership fees: Since W3.io is an industry utility, over time we will charge participating protocols a management fee that can support protocol operations and growth. &#x20;

●     Spread on payments: We anticipate processing a large amount of financial value at steady state.  We plan to take a small transaction fee when UDSC/USDT is swapped into native tokens.&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"># of chain integrations</td><td valign="top"># recipes created</td><td valign="top"># of projects supported</td><td valign="top"># of supply side network partners integrated</td><td valign="top"># of followers on social platforms</td></tr><tr><td valign="top">10</td><td valign="top">50</td><td valign="top">100</td><td valign="top">60</td><td valign="top">1m</td></tr></tbody></table>

Over time W3.io’s platform as a service business model can generate revenue in the following ways:

* **Transaction fee on the node network:** The W3.io Foundation will receive a portion of the transaction fees the network charges. &#x20;
* **Channel fee from reselling centralized IT services from AWS, GCP, and Azure:** We estimate that Web 3 native companies spend $1B on centralized IT services.  We will serve as a reseller for centralized IT services, collecting a 5-20% fee. &#x20;
* **Membership fees:** Since W3.io is an industry utility, over time we will charge participating protocols a management fee that can support protocol operations and growth.  &#x20;
* **Spread on payments:** We anticipate processing a large amount of financial value at steady state.  We plan to take a small transaction fee when UDSC/USDT is swapped into native tokens. &#x20;


# Moats

W3.io holds a strong first-mover advantage in an emerging category with little direct competition. If we continue to execute our roadmap and deliver value to our partners it will be very difficult for any new entrant to compete with us for the following reasons

**Deep Ecosystem Relationships**

It takes years of relationship building to have the depth of connections needed to convene a network like we are building and have already developed an extensive ecosystem that reaches substantially beyond what would be expected for an early stage project. As a result, we are uniquely positioned to make the project a success.

**Network Effects and Standards Lock-In**

Our partner network already spans most of the decentralized middleware stack. As we integrate partners and build out “recipes,” we are simultaneously establishing a new interoperability standard for decentralized systems. Once adopted, this standard will become foundational—making it both difficult and costly for new entrants to displace or compete with.

**Non-Rent Extractive, TAM-Expanding Design**

W3 is not structured to extract margin from the ecosystem. Instead, we act as a neutral, value-accretive utility that expands the Total Addressable Market (TAM) for all participants. This model leaves little financial incentive or room for copycat competitors, further protecting our position.


# Team + Advisors

<div align="left"><figure><img src="/files/AHDfD42XSsxJ12ziH9oO" alt="" width="99"><figcaption></figcaption></figure></div>

**Porter Stowell** \
CEO\
\
Filecoin Foundation • Coinbase • IBM Blockchain  \
8 Years of Web3 experience\
Deep Web3 Infrastructure, Product and Ecosystem expertise

***

<div align="left"><figure><img src="/files/Qj3xVFxdGP3bNmmW78VQ" alt="" width="95"><figcaption></figcaption></figure></div>

**David Post**\
Core Contributor - Ecosystem\
\
IBM Blockchain • Chainlink • Helix\
8 Years of Web3 experience\
Web3 investor, Advisor and Ecosystem builder

***

<div align="left"><figure><img src="/files/9WZoORwc4p7XDMPzJ0ZF" alt="" width="95"><figcaption></figcaption></figure></div>

Ben **Murray** \
Core Contributor - Solutions\
\
AXA • Avalanche • Space & Time • Helix\
8 Years of Web3 experience\
Solutions and Token Design Wizard

***

<div align="left"><figure><img src="/files/GTQnqrjkMtcTo1eJbKt8" alt="" width="95"><figcaption></figcaption></figure></div>

**Audie Sheridan**\
CTO\
\
VitaDAO • Schneider Electric • BlueCross\
5 Years of Web3 experience\
Built critical systems powering Fortune 500 infrastructure worldwide

***

<div align="left"><figure><img src="/files/IIUo8h9gtxLz6z6NLS3z" alt="" width="95"><figcaption></figcaption></figure></div>

**Chad Itskowitz**\
CMO\
\
Discovery • Warner Bros. • STX\
8 Years of Web3 experience\
Web3 investor, Advisor, Storyteller and Brand builder

***

<div align="left"><figure><img src="/files/RK6JgnbNXrA4Wcf9xfyR" alt="" width="95"><figcaption></figcaption></figure></div>

**Cory Gabrielsen**\
Director of Engineering\
\
Carbon Robotics • Ethereum Follow Protocol • AWS\
12 Years in crypto\
Entrepreneur and Math Magician

***

<div align="left"><figure><img src="/files/2Rc14T3HSzRSz7rzyMHG" alt="" width="95"><figcaption></figcaption></figure></div>

**Robbert van Renesse**\
Chief Scientist, Cornell Professor\
\
Cornell University

***

<div align="left"><figure><img src="/files/ODP5Wv3YG3Gc4W7ntGNJ" alt="" width="95"><figcaption></figcaption></figure></div>

**Adeline Zhou**\
Advisor, Former CMO Chainlink

***

<div align="left"><figure><img src="/files/RPZl8HG8R8wxGxSb1e5M" alt="" width="95"><figcaption></figcaption></figure></div>

**Nate Holiday**\
Advisor, CEO of Space and Time

***

<div align="left"><figure><img src="/files/LuxWI0IuxbAoWAQF2ejg" alt="" width="95"><figcaption></figcaption></figure></div>

**Devon Ferreira**\
Advisor, Founder/Managing Partner of F/AS\
Former CMO of Ava Labs & Immutable

***

<div align="left"><figure><img src="/files/08OZqKRZSQOX5NvUJQBb" alt="" width="95"><figcaption></figcaption></figure></div>

**Shyam Nagarajan**\
Advisor, COO of Hedera


# Investors

### Funds

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>AltLayer</td><td><a href="/files/77KnaLRSTRA00COVShzQ">/files/77KnaLRSTRA00COVShzQ</a></td></tr><tr><td>API3</td><td><a href="/files/zvQLUPlnb07NLSFoaTtl">/files/zvQLUPlnb07NLSFoaTtl</a></td></tr><tr><td>Arrington Capital</td><td><a href="/files/xtPYrIu1omXmi8UufnZ1">/files/xtPYrIu1omXmi8UufnZ1</a></td></tr><tr><td>Avail</td><td><a href="/files/u0fxInZcR21Apg78uzG9">/files/u0fxInZcR21Apg78uzG9</a></td></tr><tr><td>Babylon</td><td><a href="/files/XPx0M1360uEIi6yBWkqZ">/files/XPx0M1360uEIi6yBWkqZ</a></td></tr><tr><td>Bagel</td><td><a href="/files/8cVK9W68BMKrdl1u26ae">/files/8cVK9W68BMKrdl1u26ae</a></td></tr><tr><td>Bitscale Capital</td><td><a href="/files/A7vJcbz4XIACdXgqGxGs">/files/A7vJcbz4XIACdXgqGxGs</a></td></tr><tr><td>Covalent</td><td><a href="/files/dglYBmFaGfVAZwGqe75x">/files/dglYBmFaGfVAZwGqe75x</a></td></tr><tr><td>Cubist</td><td><a href="/files/1pR4mnzG5InorY9cPRuI">/files/1pR4mnzG5InorY9cPRuI</a></td></tr><tr><td>Eighen Layer</td><td><a href="/files/NIVhEFBzPtfX3MqQYmlB">/files/NIVhEFBzPtfX3MqQYmlB</a></td></tr><tr><td>Filecoin</td><td><a href="/files/OaHG1ZOZO1sG7dX6wtk1">/files/OaHG1ZOZO1sG7dX6wtk1</a></td></tr><tr><td>Fleek</td><td><a href="/files/nvc8KGHUI3GxTUeED9nM">/files/nvc8KGHUI3GxTUeED9nM</a></td></tr><tr><td>Framework</td><td><a href="/files/aOQvSOVXjOBSzpQJiPrC">/files/aOQvSOVXjOBSzpQJiPrC</a></td></tr><tr><td>IoTex</td><td><a href="/files/s8d8pAhbFoZvgy2bcM24">/files/s8d8pAhbFoZvgy2bcM24</a></td></tr><tr><td>Lava</td><td><a href="/files/6rTaY9VboYPzosH3MSYV">/files/6rTaY9VboYPzosH3MSYV</a></td></tr><tr><td>Lit</td><td><a href="/files/sDP0nFK7ZE0CLbmb574V">/files/sDP0nFK7ZE0CLbmb574V</a></td></tr><tr><td>Pyth</td><td><a href="/files/64WhTCaQ4an2KconZMrM">/files/64WhTCaQ4an2KconZMrM</a></td></tr><tr><td>Space &#x26; Time</td><td><a href="/files/CM5XDt7l941Mc5eyZxhg">/files/CM5XDt7l941Mc5eyZxhg</a></td></tr><tr><td>Spruce ID</td><td><a href="/files/blEndYvhhjeFnTRyPhc6">/files/blEndYvhhjeFnTRyPhc6</a></td></tr><tr><td>ZettaBlock Labs</td><td><a href="/files/Y0R7f8YtuA8otfsqZvoD">/files/Y0R7f8YtuA8otfsqZvoD</a></td></tr></tbody></table>

### Angel Investors