Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 3 additions & 7 deletions products/introducing-nexus.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ 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.

In the previous sections**,** we defined Talus Agents as leveraging multiple layers:
In the previous sections, we defined Talus Agents as leveraging multiple layers:

- **Blockchain** as the coordination and value layer.
- **Decentralized data storage platform** as the data layer.
Expand All @@ -14,14 +14,14 @@ In the previous sections**,** we defined Talus Agents as leveraging multiple lay
> 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.
>

![image.png](../.gitbook/assets/card7.png)

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

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.

![Nexus Architecture](../.gitbook/assets/card7.png)

## Technical Component Overview

Developers building with Nexus (purple) will primarily interact through the Nexus SDK, so the complexity is abstracted away from them.
Expand Down Expand Up @@ -92,12 +92,8 @@ Value creation happens across three layers:
- **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.


![Talus ecosystem with scenarios.](../.gitbook/assets/talus_ecosystem_scenario.png)


Talus ecosystem with scenarios.

### **Flagship Applications**

To bootstrap adoption, Talus is launching Nexus with flagship apps that directly map to these economic layers:
Expand Down
4 changes: 0 additions & 4 deletions talus-overview/ai-agent-whats-in-a-name.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,12 +60,8 @@ We believe agentic frameworks (and thus the agents they allow to build) exist on
- **Type 2**: agents that are defined onchain with execution workflows that are verifiable onchain, but, for the sake of performance and cost-effectiveness, outsource (a part of) their execution offchain to service providers.
- **Type 3**: agents that are defined and operate completely onchain.


![Agentic Frameworks as a Spectrum](../.gitbook/assets/agentic-framework-spectrum-v2.png)


Agentic Frameworks as a Spectrum

At Talus, we believe that agentic frameworks should strive towards decentralization but within the bounds of the pragmatic. The emphasis should be on **verifiability onchain** (along with the agent’s workflow definition), rather than putting all agentic execution onchain at great cost/performance penalties.

**We are building Nexus** (decentralized automation protocol and developer framework to build Talus Agents) **to occupy the Type 2 domain of the spectrum** where we leverage the open, censorship resistant and verifiable nature of the blockchain while keeping the overall workflow performant through outsourcing computation to offchain service providers. This is the first step to identify how Talus Agents are different, but there’s more that we can specify to rigorously define them.
Expand Down