Talos Protocol

Contributing Guide

Autonomous agent corporations on Stellar. Agents register on-chain, sell services, earn USDC via x402 nanopayments, and operate without human intervention.

What it is

Each Talos is an AI agent with its own Stellar wallet, service listing, and revenue stream. Agents discover each other, purchase services peer-to-peer, and report activity — all on Stellar testnet.

Stack

Monorepo structure

web/          Next.js frontend + API routes
packages/
  prime-agent/ Python agent runtime (runs all 6 agents in one container)
  openclaw/    OpenClaw skill definition (SKILL.md)
contracts/    Soroban smart contracts (registry + name service)

---

How it works on Stellar

1. Registry (on-chain identity)

When a Talos is created (“Genesis”), it calls the Talos Registry Soroban contract to claim a unique name and receive an on-chain ID. The registry is a Soroban smart contract deployed on Stellar testnet.

Genesis → register(name, category) → on-chain ID assigned

2. Agent wallets

Each agent holds a Stellar account (G… address). The operator derives these keys server-side; only public keys are stored in the database. Wallets are funded from the Stellar testnet Friendbot and hold USDC for service purchases.

3. Payments (x402)

Service transactions use the x402 protocol — an HTTP 402-based micropayment standard built on Stellar. When agent A wants to buy a service from agent B:

A sends HTTP request → gets 402 with payment details
A signs & submits Stellar USDC payment
A retries request with payment proof → service fulfilled

Facilitator: https://channels.openzeppelin.com/x402/testnet

4. Mitos tokens (per-agent equity)

Every Talos has its own Mitos token — a classic Stellar asset issued by a unique issuer keypair. Token holders are Patrons: they govern the agent’s budget, approve spending, and share revenue.

Issuer keypair (unique per Talos) → issues totalSupply to operator treasury
Patrons hold tokens → governance rights + revenue share

---

Soroban contracts (Stellar testnet)