Talus-Network · mike-hanono · Aug 22, 2025 · Aug 22, 2025 · Aug 22, 2025 · Aug 22, 2025
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
 ---
-description: 'Talus: Powering the Autonomous AI Economy'
+description: 'The Missing Infrastructure for the Autonomous Digital Economy'
 cover: .gitbook/assets/Screenshot 2025-04-15 at 17.48.08.png
 coverY: 0
 layout:

diff --git a/SUMMARY.md b/SUMMARY.md
@@ -6,7 +6,7 @@
 
 - [🐸 Introduction to Talus](talus-overview/readme.md)
 - [🤖 AI Agent: What's in a Name?](talus-overview/ai-agent-whats-in-a-name.md)
-- [🔬 Nexus Whitepaper](talus-overview/nexus-whitepaper.md)
+- [🔬 Papers](talus-overview/papers.md)
 
 ## 🚀 Getting Started
 

diff --git a/products/introducing-nexus.md b/products/introducing-nexus.md
@@ -3,92 +3,106 @@ description: Nexus at the heart of the Talus Technical Ecosystem
 ---
 
 # 👋 Introducing Nexus
+The Talus platform, powered by Nexus, allows for an open ecosystem consisting of many actors, our community, building towards a more democratic and efficient digital economy. 
 
-The **Talus platform, powered by Nexus**, allows for an open ecosystem consisting of many actors, our community, building towards a future with Talus AI agents that revolutionize digital experiences to serve everyone.
+In the previous sections**,** we defined Talus Agents as leveraging multiple layers:
 
-In the previous section we defined Talus agents as leveraging multiple layers:
+- **Blockchain** as the coordination and value layer.
+- **Decentralized data storage platform** as the data layer.
+- **Offchain (AI) infrastructure** as the computation/execution layer.
 
-* Blockchain as the coordination and value layer.
-* Decentralized data storage platform as the data layer
-* Offchain (AI) infrastructure as the computation/execution layer
+> At first sight, this layered approach introduces more coordination complexity. This, in a way, is the case. This is exactly why we offer **Nexus**, the developer framework for building Talus Agents.
+> 
 
-{% hint style="success" %}
-At first sight, this layered approach introduces more coordination complexity. This, in a way, is the case. This is exactly why we offer Nexus, the developer framework for building Talus agents. Nexus acts as a tool to streamline the developer experience.
-{% endhint %}
+![image.png](attachment:47f5256b-704d-4f09-81b0-42f7d7994f2a:image.png)
 
-<figure><img src="../.gitbook/assets/nexus-arch.png" alt=""><figcaption></figcaption></figure>
+**Nexus** is a decentralized agentic automation protocol purpose-built to support verifiable agent execution, permissionless tool hosting, and monetization—streamlining the developer experience. It bridges the gap between the different layers that make up a Talus Agent workflow, connecting the onchain and offchain world. It does the heavy lifting in the background and provides developers with an easy-to-use SDK.
 
-In essence, Nexus as a framework enables us to bridge the gap between the different layers that make up a Talus agent workflow, between the onchain and offchain world. It does the heavy lifting in the background and provides the developer with and easy to interact with SDK.
+Nexus lays the groundwork for an efficient, decentralized digital economy by turning AI logic into autonomous, value-generating actions. It enables agents to securely execute complex workflows with dynamic on-chain permissions, using trustless coordinators for routing, delegation, and verification. Developers can build high-performance, AI-powered dApps that ingest real-time data and interact across services. With Nexus, Talus establishes a foundation for decentralized AI automation at scale, where logic, data, and value move seamlessly to their highest use, maximizing transparency and efficiency across the ecosystem.
 
 To get a holistic overview of all actors and technical components of the Talus platform, let’s consider the following diagram.
 
-### Technical Component Overview
+## Technical Component Overview
 
 Developers building with Nexus (purple) will primarily interact through the Nexus SDK, so the complexity is abstracted away from them.
 
 The current version of Nexus is a combination of onchain and offchain components, corresponding with the different layers. Let’s give an overview:
 
-#### Sui - the Coordination & Value Layer
+### **Sui – the Coordination & Value Layer**
 
-The onchain components are initially deployed on the Sui Blockchain, and thus the smart contracts written in Sui Move. The reasoning behind picking Sui as the first layer to deploy Nexus, are examined in [another section](../why-sui-move.md).
+The onchain components are initially deployed on the Sui Blockchain, with smart contracts written in Sui Move. The reasoning behind picking Sui as the first layer to deploy Nexus is examined in  [another section](https://github.com/Talus-Network/gitbook-docs/blob/production/why-sui-move.md).
 
-There’s 3 different types of onchain Sui packages that are relevant for Nexus and Talus agents:
+There are three different types of onchain Sui packages that are relevant for Nexus and Talus Agents:
 
-1. **Talus Agent Package (TAP**): A developer building an agent will deploy a Talus Agent Package (TAP) to the blockchain. Its main purpose is to store the agent’s workflow and some additional custom business logic. (This is managed by the agent developer with tooling provided by Nexus SDK)
-2. **Tools**: Tools in used by Talus agents can either be offchain or onchain. In the case of onchain tools, agent developers will have a wide array of options to use existing Sui packages and use them as onchain Tools.
-3. **Onchain Components**: The Nexus onchain components are packages maintained by the Talus Labs team that enable the deployment and execution of agent workflows. It consists of some primitives, a package to manage the workflow and a registry for (onchain or offchain) Tools.
+1. **Nexus Onchain Package (NOP):** Defines the common data structures used by other packages and is maintained by the Talus team. Based on NOP, developers can build Talus Tools and Talus Agent packages to construct services that can be used in Talus workflows or define data structures for managing permissions.
+2. **Talus Agent Package (TAP):** A developer building an agent deploys a TAP to the blockchain. Its main purpose is to store the agent’s workflow and additional custom business logic. This is managed by the agent developer with tooling provided by the Nexus SDK.
+3. **Tools:** Tools used by Talus Agents can either be offchain or onchain. For onchain tools, agent developers can integrate existing Sui packages and use them as onchain Tools.
 
-#### Walrus - the Data Storage Layer
+### **Walrus – the Data Storage Layer**
 
-Some crucial metadata associated with the agent workflow has to be stored onchain (Sui). However, due to the expensive nature of a coordination and value blockchain like Sui, all data that can be stored elsewhere ought to do so. Walrus, a decentralized data storage platform built by the Mysten Labs team, provides an excellent alternative. Technically also a decentralized ledger, from the viewpoint of the agent and onchain components of Nexus, data stored on Walrus can be considered “offchain”.
+Some crucial metadata associated with the agent workflow has to be stored onchain (Sui). However, due to the expensive nature of a coordination and value blockchain like Sui, all data that can be stored elsewhere should do so. **Walrus**, a decentralized data storage platform built by the Mysten Labs team, provides an excellent alternative.
 
-Data that could be stored on Walrus includes: agent metadata, agent memory and context for the agent’s operation.
+Data that could be stored on Walrus includes: agent metadata, agent memory, and context for the agent’s operation.
 
-#### Offchain Tools - the Computation & Execution Layer
+### **Offchain Tools – the Computation & Execution Layer**
 
-Many of the AI tools an agent could be using (e.g. LLMs, image recognition or generation, text processing tools, mathematical operations, web access functions, file handling utilities etc.) would prove to be too expensive to perform fully onchain, i.e. have the computation performed by every validator through consensus.
+Many AI tools an agent could use—such as LLMs, image recognition or generation, text processing tools, mathematical operations, web access functions, and file handling utilities—would be too expensive to perform fully onchain.
 
-Instead the Tool is executed offchain, with its inputs and outputs being provided by an offchain service, which we’ll discuss next.
+Instead, these Tools are executed offchain, with their inputs and outputs handled by an offchain service, which we’ll discuss next.
 
-#### Nexus Offchain
+### **Nexus Offchain**
 
-Provided that the agent workflow is deployed onchain, but the Tools (can be) run offchain, there is a need for Nexus to provide an offchain service that will orchestrate the communication between the onchain and offchain worlds. That component is the **`Leader`** component in the Nexus (offchain) backend.
+Provided that the agent workflow is deployed onchain, but the Tools can be run offchain, Nexus provides an offchain service that orchestrates communication between the onchain and offchain worlds: the **Leader network**.
 
-The Leader will:
+The Leader network acts as a coordinator, linking off-chain tools (such as LLM APIs or other Web2 services), on-chain tools, and workflow execution with minimized trust.
 
-* Listen for events emitted by the agent’s onchain workflow that request execution of an offchain Tool
-* Index these events
-* Look up the Tool information in the onchain Tool registry
-* Request the execution of the Tool and provide it with the inputs
-* Listen for the Tool execution result (or error) and then communicate the outputs back to the workflow onchain
+The `Leader` will:
+
+- Listen for events emitted by the agent’s onchain workflow that request execution of an offchain Tool.
+- Index these events.
+- Look up the Tool information in the onchain Tool registry.
+- Request the execution of the Tool and provide it with the inputs.
+- Listen for the Tool execution result (or error) and then communicate the outputs back to the workflow onchain.
 
 Through the actions of the Leader, we can resume an onchain workflow after the execution of an offchain Tool has successfully occurred.
 
-Note: the term Leader has been chosen with a future of progressive decentralization in mind, when the Leader process will be part of a decentralized protocol.
+Nexus is designed to gradually evolve into a trusted leader network utilizing TEEs, and ultimately to a fully decentralized leader network where anyone can participate permissionlessly. This approach preserves service availability while progressively improving decentralization and trust minimization.
+
+## **Ecosystem**
+
+In addition to the technical components, it’s important to highlight the actors that build on Talus, the marketplaces and services that create economic value, and the applications that showcase what’s possible.
+
+### **Developer Personas**
+
+- **Nexus Maintainer** → Core Talus contributor responsible for maintaining the Nexus codebase.
+- **Tool Developer** → Publishes new Talus Tools by wrapping offchain services or onchain contracts into Nexus-compatible modules.
+- **Agent Developer** → Designs workflows and deploys Talus Agents as smart contracts.
+- **Application Developer** → Builds user-facing apps powered by agents and workflows.
+
+### **Ecosystem Partners**
 
-### Ecosystem Actors
+- **Service Providers (for Tools)** → External entities offering offchain services (e.g., APIs, infra) that Tool Developers can integrate.
+- **Onchain Applications (for Tools)** → Smart contracts on Sui that Tool Developers can connect as onchain agent capabilities.
 
-Next to an analysis of the technical components in the diagram, we can also consider the different actors that are interacting with all of the components. We’ll distinguish between:
+### **Economic Structures: Marketplaces and Services**
 
-* **Developer Personas**: Those individuals or entities that will be building with or contribute to Nexus and Talus as a whole.
-* **Ecosystem Partners**: Those providers of services, infrastructure or onchain contracts that add value to the Talus ecosystem without requiring active engagement with the Nexus framework.
+Value creation happens across three layers:
 
-{% hint style="info" %}
-The developer personas are a proxy for the applications they represent or perform services for. Ultimately, Nexus as a framework, aims to empower applications to leverage onchain agents in a seamless manner.
-{% endhint %}
+- **Tool Marketplace (TM)** → Tool Developers publish and monetize Tools (e.g., LLMs, DeFi modules). Every workflow execution pays for these Tools, creating recurring revenue and strengthening network effects as agent capabilities grow.
+- **Agent Marketplace (AM)** → Agent Developers create and monetize agents that operate as decentralized services (e.g., automated trading strategies). Users can instantiate or customize agents, driving demand for more sophisticated Tools.
+- **Agent-as-a-Service (AaaS)** → Application Developers compose Talus Agents into autonomous services for existing apps and dApps (e.g., audit bots for DEX users). This makes agent capabilities widely accessible while extending automation to mainstream protocols.
 
-#### Developer personas
+![Talus ecosystem with scenarios.](attachment:3b80aa02-a82a-4865-ba4c-3356d6fb2d79:image.png)
 
-For the purposes of this documentation we make distinction between different user roles within the ecosystem:
+Talus ecosystem with scenarios.
 
-* **Nexus maintainer:** Core team member that maintains the Nexus codebase.
-* **Tool developer:** Developer who integrates an existing Tool with Nexus by ensuring the Tool definition complies with the expected interface and the tool is registered.
-* **Agent developer:** Developer who designs the agent workflow and subsequently deploys the agent smart contract.
-* **Application Developer:** Developer who builds applications using agents.
+### **Flagship Applications**
 
-#### Ecosystem Partners
+To bootstrap adoption, Talus is launching Nexus with flagship apps that directly map to these economic layers:
 
-For the purposes of this documentation we make the distinction between different partners:
+- **Talus Vision (Agent Marketplace)** → A no-code workflow builder that makes Nexus accessible and understandable. It lets anyone design, test, and deploy autonomous workflows visually, serving as the first Agent Marketplace.
+- **IDOL.fun (Agent Marketplace + AaaS)** → A consumer-facing app that shows agents as productive, monetizable entities:
+    - **IDOL Launchpad (AM)** → Twitter-based IDOLs that react to fans and can be “hired” for tasks.
+    - **AvA Gaming (AaaS)** → Competitive **Agent-vs-Agent** battles with provably fair outcomes where speculators can bet transparently.
 
-* **Service Provider (for Tools)**: These are 3rd party entities that run services that are desirable for Tool developers to integrate as additional offchain features for AI agents.
-* **Onchain applications (for Tools)**: These are onchain applications or contracts on the Sui blockchain that can be used for Tool developers to integrate as additional onchain features for AI agents.
+Talus will empower developers, businesses, and AI agents to coordinate, automate, and monetize intelligent workflows at global scale, all in a verifiable and permissionless manner.