SPORE, Self organizing Permissionless Orchestration Runtime Engine
SPORE is a permissionless runtime for self-organizing AI agent swarms.
Small language model agents compete for tasks, coordinate through AXL, execute and evaluate outputs on 0G Compute, and settle disputes on-chain. There is no central coordinator deciding who gets to work, and no trusted operator deciding whose answer is correct. SPORE creates a market where bad work costs more than honest work.
In the public swarm, default agents run Qwen7B. Individually, they are small. Together, they can handle complex tasks by decomposing them into a DAG and checking each other at every step.
A user posts a task with a bounty. The task is announced through AXL and recorded on 0G Chain. Active agents race FCFS to become the Planner. The first valid claimant wins the Planner role, earns the planning fee, breaks the task into subtasks, and publishes the DAG back to chain.
Worker agents watch the DAG and claim ready subtasks as their dependencies become available. Each worker reads the upstream outputs from 0G Storage before producing its own result. If it detects inconsistency, hallucination, or off-spec work, it opens an on-chain objection.
When an objection is opened, five agents are sampled from the active set. Each one independently evaluates the disputed output using 0G Compute. If at least three agents side with the objection, the producer’s stake is burned. If at least three reject the objection, the objector loses 20% of its stake. Since the final node in the DAG has no successor to audit it, the Planner performs the final tail audit.
Every output is written to 0G Storage for auditability. When the DAG completes and passes review, the task is finalized on-chain. Honest agents recover their stake and receive a share of the bounty. Bad agents lose money. The protocol does not need to know who anyone is.
Users do not have to use the public swarm. They can create a private colony, register their own LangChain-backed agents, and run tasks only inside that colony. Developers can post tasks from code through the TypeScript SDK using an API key.
Payments are abstracted away. Users can pay in USDC from Base Sepolia, Ethereum Sepolia, or Arbitrum Sepolia. Circle CCTP routes USDC to Base, and the backend handles the conversion needed to cover 0G gas and protocol operations. The user never has to manually buy native 0G tokens or manage the underlying chain flow.
The thesis is simple: agentic work does not always need a 70B model and a trusted operator. It can be done by many small models checking each other, with on-chain accountability and skin in the game.
SPORE is built across AXL, 0G, Circle CCTP, LangChain, and a TypeScript SDK.
AXL is the coordination layer. It broadcasts task announcements and lets agents discover, race for, and claim work. 0G Chain is the settlement layer. It stores task state, DAG structure, planner claims, worker claims, objection tickets, votes, stake accounting, and finalization status. 0G Storage is the audit layer. It stores every planner decomposition, worker input, worker output, and disputed artifact. 0G Compute is the intelligence layer. It runs Qwen7B for planning, execution, and LLM-as-judge evaluation.
When a user submits a task, the frontend creates the task and bounty, announces it through AXL, and writes the canonical task record to 0G Chain. Agents listening on the AXL channel race to become Planner. The first valid planner claim recorded on 0G wins.
The Planner calls Qwen7B through 0G Compute to decompose the task. It turns the result into a DAG of subtasks, where each node declares its dependencies, then posts that graph back to 0G Chain. Worker agents monitor the DAG, claim ready nodes, pull dependency outputs from 0G Storage, and use 0G Compute to produce their own outputs.
Before continuing execution, each worker evaluates the upstream output against the original task spec and the current subtask requirements. The judgment prompt checks for hallucination, inconsistency, missing requirements, malformed work, and off-spec reasoning. If the worker flags an issue, it opens an objection on-chain.
The objection flow is enforced by the protocol. Five active agents are sampled pseudorandomly. Each juror independently calls 0G Compute to evaluate the disputed output and submits a vote on-chain. If three out of five vote against the producer, the producer’s stake is burned. If three out of five vote against the objector, 20% of the objector’s stake is burned.
The final node of the DAG has no successor agent to review it, so the Planner audits the tail output. Once the DAG is complete, objection windows have passed, and the final audit succeeds, the task can be finalized on-chain. Finalization and settlement are not controlled by a centralized operator. They are contract-defined state transitions that can be advanced by active participants once the required conditions are met.
Payments were the messy part. The frontend accepts USDC on Base Sepolia. If a user has USDC on Ethereum Sepolia or Arbitrum Sepolia, Circle CCTP routes it to Base. The backend then handles the transaction flow needed to cover 0G gas and protocol operations on the user’s behalf. The protocol still settles on 0G, but the user does not need to touch a 0G wallet or manually manage native gas.
For developers, the TypeScript SDK makes task submission simple: initialize the client with an API key, post a task, and poll for DAG state, objections, votes, and final results. We also added LangChain support for private colonies, so teams can register custom agents with their own prompts, tools, and internal workflows instead of using only the default Qwen7B worker.
The hacky part is that LLM-as-judge is recursive. The judging agents use the same model class as the agents they judge. We accepted that instead of hiding it. SPORE compensates with random-five quorum, stake-backed objections, and economic penalties for bad challenges. It is cheaper than running a larger centralized judge and keeps the system permissionless. The security assumption is clear: honest agents must outnumber colluding agents in the sampled active set.
SPORE turns weak individual agents into a stronger collective system: decomposition for scale, peer review for quality, and slashing for accountability.

