01
Connect
Access models and agent capabilities through a familiar gateway. Bring your task; choose the tools it needs.
Many minds in.
One intelligence out.
Models, agents and compute, woven into one open network. Terza brings a builder-first vision to Bittensor — useful intelligence, with every contribution traceable.
BITTENSOR SUBNET CONCEPT ↗TASKWhat if intelligence belonged to everyone?EXPLORE
OPEN MODELS. INDEPENDENT COMPUTE. VERIFIABLE CONTRIBUTIONS. ONE NETWORK, BUILT TOGETHER.
OPEN INTELLIGENCE · PROPOSED NETWORKCONCEPT
One place to build. An open network underneath.
τA BITTENSOR-NATIVE VISION FOR USEFUL INTELLIGENCE
Open modelsMODELSModel gatewayAPIHermesAGENTSLinux workspacesLINUXMinersCOMPUTEValidatorsEVALUATIONSkillsTOOLSBittensorNETWORKOpen modelsMODELSModel gatewayAPIHermesAGENTSLinux workspacesLINUXMinersCOMPUTEValidatorsEVALUATIONSkillsTOOLSBittensorNETWORKOpen modelsMODELSModel gatewayAPIHermesAGENTSLinux workspacesLINUXMinersCOMPUTEValidatorsEVALUATIONSkillsTOOLSBittensorNETWORK
Open modelsMODELSModel gatewayAPIHermesAGENTSLinux workspacesLINUXMinersCOMPUTEValidatorsEVALUATIONSkillsTOOLSBittensorNETWORKOpen modelsMODELSModel gatewayAPIHermesAGENTSLinux workspacesLINUXMinersCOMPUTEValidatorsEVALUATIONSkillsTOOLSBittensorNETWORKOpen modelsMODELSModel gatewayAPIHermesAGENTSLinux workspacesLINUXMinersCOMPUTEValidatorsEVALUATIONSkillsTOOLSBittensorNETWORK
02 · PROOF OF CONTRIBUTION
Every answer has a thread. Follow it.
A proposed network where work can be inspected. Follow a request from execution to evaluation and its usage receipt. Select a stage to explore this illustrative flow.
STAGE08 of 30 · Miner
FROMworker.execution · result = completed
STEPinspect the contribution record
STATUSIllustrative flow · no live network connected
03 THE NETWORK LOOP
From open compute to useful work, in three steps.
A simple idea: builders bring the task, miners do the work, and validators evaluate the result. Useful contributions should be what moves the network forward.
Explore the flow→
02
Contribute
Independent miners supply inference and execution. Each result carries a record of the work that produced it.
03
Verify
Validators evaluate outputs against the subnet’s task and scoring rules. Mechanism design is still in development.
04 BUILT FOR BUILDERS
Your next idea. An open network behind it.
Explore the proposed developer experience. These examples illustrate the interface and network flow; they do not execute requests or connect to a live subnet.
TERZA / EXAMPLE 01
{ }
const response = await client.chat.completions.create({
model: "terza/open-model",
messages: [{ role: "user", content: "Build something useful." }],
stream: true
});ILLUSTRATIVE INTERFACENOT A LIVE ENDPOINT
VISUAL STUDY · NOT NETWORK METRICS05 OBSERVABILITY
Useful work should leave a visible trail.
A network is only as useful as the work it delivers. Our proposed control plane puts execution, evaluation and usage in the same view.
Know where a task runs
Follow each request through its model, worker and runtime.
Understand the quality signal
Inspect how a contribution is evaluated, with scoring criteria made explicit.
See what produced the result
Connect usage back to the request and the agent that initiated it.
06BY DESIGN
What matters when intelligence is shared.
The principles behind a proposed Terza subnet. These are architecture goals, not live network statistics.
Open
a design goal: accessible interfaces for independent builders
3
proposed roles: builders, miners and validators
Useful
evaluate outputs against real application tasks
TBD
subnet number and registration are not yet decided
Every result inspectable
A proposed trace from request to output and evaluation.
Quality
a research focus, not a measured network benchmark
Concept
an exploration of the Terza subnet direction
07THE TERZA THESIS
Intelligence becomes infrastructure when anyone can contribute, every output can be evaluated, and useful work comes first.
A proposed direction for Terza on Bittensor · concept stage
Build
applications that use the network
Serve
inference and agent outputs
Verify
quality against shared tasks
08POSSIBILITIES
Useful work. Many directions.
Three illustrative workflows for the proposed network. Examples of what could be built, not deployed products or customer results.
09TRUST BY DESIGN
Trust should travel with the task.
A decentralized network needs explicit boundaries and inspectable results. These principles guide the design; security implementation is not yet available.
Bounded execution
Design goal: each request defines the permitted task, input and output. Agent capabilities should remain explicit and scoped.
Inspectable evaluation
Design goal: publish task definitions and make scoring understandable, reproducible and open to review.
Data-aware routing
Design goal: make data handling and provider selection explicit. Privacy guarantees will depend on the final protocol and implementation.
EXPLICIT TASKSOPEN EVALUATIONTRACEABLE OUTPUTSSCOPED ACCESSPROPOSED DESIGN
10THE ECOSYSTEM
Many contributors. One network.
An architectural map of the proposed subnet: from application requests to useful outputs and independent evaluation.
REQUEST LAYER
Applications
A proposed entry point for products that need model inference and agent execution.
PROPOSED INTERFACEINFERENCE
Model providers
Independent operators serving useful model outputs against a shared task specification.
DESIGN IN PROGRESSEXECUTION
Agent runtimes
A proposed execution layer for bounded tasks with explicit inputs and inspectable results.
CONCEPT STAGEEVALUATION
Validators
Evaluation designs that compare task quality, latency and reliable execution.
UNDER RESEARCHDATA LAYER
Retrieval
Explore ways to provide relevant context while keeping provenance attached to each request.
PROPOSED CAPABILITYOBSERVABILITY
Trace records
A common record of request, response and evaluation to make network behavior inspectable.
DESIGN GOALCOORDINATION
Bittensor
A subnet concept within the Bittensor ecosystem. Registration and subnet identity are not yet set.
SUBNET ID · TBDDEVELOPERS
Open interfaces
An approach built around understandable specifications and reproducible integration examples.
PLANNED11PARTICIPATE
Different roles. Shared intelligence.
Explore a potential role in the network. Participation requirements, incentives and availability remain to be defined.
Builder
Create
Explore applications powered by useful intelligence.
- Model inference workflows
- Bounded agent tasks
- Inspectable execution traces
- API specification to be defined
Miner
CONCEPTContribute
Explore serving model and agent task outputs.
- Independent model operations
- Shared task specification
- Quality-focused evaluation
- Requirements to be defined
Validator
Evaluate
Explore independent evaluation of useful work.
- Reproducible evaluation tasks
- Output quality assessment
- Transparent scoring design
- Incentives to be defined
12 · QUESTIONS
Before you join the conversation.
A clear view of what is proposed, what is undecided, and what this concept demonstrates.
Explore TerzaNo live subnet is represented by this website. This is a proposed Terza direction for decentralized model inference and agent execution. The subnet number, final positioning and launch plan are still undecided.
The concept connects applications with independent inference and agent operators, then evaluates the usefulness of their outputs. The task specification, API and evaluation methodology remain to be defined.
No. The interface contains illustrative workflows and design goals, not production performance, customers, revenue or token returns.
The proposed roles are to serve task outputs and evaluate them against a common specification. Hardware requirements, registration, scoring and incentives are not yet published.
The playground on this page is a local interface demonstration. It does not submit requests to a live subnet or expose an available API.
Explore Terza for the existing Terza website and the official Bittensor documentation to understand the ecosystem. This concept does not announce an official partnership or a registered subnet.