Subnet 64 – Chutes: Your Simple Guide

Chutes (Subnet 64) on Bittensor turns decentralized GPUs into serverless AI compute you can deploy in minutes. Instead of renting a single cloud, you point your code at a market of independent providers – and pay for useful work.

What is Chutes?

Chutes is a serverless AI compute network built as Subnet 64 on Bittensor.
You deploy workloads (LLMs, vision, batch jobs, custom containers) to a permissionless pool of GPUs. Jobs are scheduled across many miners; outputs return through a clean API or CLI. Bittensor’s incentive layer handles scoring and rewards so the best providers attract more work.

In one line: Bring code; the subnet finds GPUs and pays for useful work.

How Chutes works

Chutes uses the standard Bittensor roles:

• Miners provide GPUs and run “chutes” – packaged applications, usually Docker images. They choose which chutes to host based on hardware and expected rewards.
• Validators send test jobs, benchmark latency/quality/reliability, and publish weights on‑chain. Those weights drive emissions and traffic routing to higher‑quality miners.

For developers:

• Auth & keys: You authenticate with a Bittensor wallet (hotkey) and create API keys to call endpoints.
• Deploy flow: Package your app (e.g., an LLM server) → push config → call the subnet endpoint → receive results.
• Verification: Chutes includes environment checks (e.g., device‑info challenges, system pings, filesystem checks) to reduce spoofing and confirm that real hardware executed your job.

Why Chutes matters

1. Serverless, not just GPU rental
   You bring code; the subnet handles scheduling, scaling, and routing across independent providers.
2. Open participation
   Anyone with capable hardware can join as a miner; anyone can validate and help route rewards toward reliable providers.
3. Market‑driven efficiency
   Because performance is scored on‑chain, higher‑quality miners rise, weaker ones fade. Over time, the network gets faster and more reliable.
4. Cost and speed (project claims)
   The project positions Chutes as a faster, lower‑cost path to AI compute vs. traditional clouds. Treat this as team claims – your actual cost depends on workload, supply, and demand.

“We propose a market where intelligence is priced by other intelligence systems peer‑to‑peer across the internet.” – Bittensor whitepaper.

Who’s building it?

Rayon Labs builds Chutes and, moreover, contributes to other Bittensor subnets such as SN19 and SN56. In addition, the team maintains public repos with the miner, validator/API, and CLI/SDK so you can participate or deploy immediately.

What you can run on Chutes

• LLM inference (chat, summarization, RAG endpoints)
• Vision models (classification/detection, image‑to‑image)
• Batch & pipelines (ETL, embeddings, synthetic data generation)
• Custom containers (any Dockerized service compatible with the miner template)

Getting started (quick path)

1. Explore the docs/site to understand endpoints and the deploy model.
2. Install the CLI/SDK and run a test chute (e.g., a small LLM or image model).
3. Create a Bittensor wallet/hotkey, mint an API key, and make your first request.
4. Inspect logs/metrics to check latency, retries, and provider behavior; iterate on model/container settings.

Limitations & considerations

• Networking & hardware: Miners typically need a stable public endpoint and sufficient VRAM (requirements vary by model).
• Availability variance: Because supply is decentralized, latency and throughput can vary by region and time.
• Economic volatility: Each subnet has its own token dynamics (dTAO/alpha). Prices and emissions change; avoid hard‑coding numbers in evergreen content.
• Compliance & data: You control what your app sends to miners; handle privacy and licensing the same way you would on any third‑party compute.

Key takeaways

• Chutes (Subnet 64) offers serverless AI compute on top of Bittensor’s open incentive layer.
• Miners run your packaged apps; validators score performance; on‑chain weights route rewards and traffic.
• You get a simple developer experience (API/CLI) with permissionless scale across many independent GPU providers.
• Treat cost claims as workload‑dependent; test with your real traffic and models.