> For the complete documentation index, see [llms.txt](https://docs.layertao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.layertao.com/welcome-to-layertao/readme-1.md).

# The Problem

### Current Bittensor Experience

Bittensor provides the network, but leaves routing, evaluation, and reliability to the developer.

```
Developer App
    |
    v
Bittensor SDK / CLI
    |
    v
Manual Setup
(Subnet Selection + Wallet + Config)
    |
    v
Metagraph Access
(Node Discovery)
    |
    v
Direct Dendrite Calls
    |
    v
Execution Targets
(Axons / Miners)
    |
    v
Single / Manual Requests
(No built-in retry or routing)
    |
    v
Raw Responses
    |
    v
-----------------------------------
|     ❗ MISSING ABSTRACTION       |
| - No routing intelligence       |
| - No response evaluation        |
| - No reliability layer          |
| - No privacy controls           |
| - No unified API                |
-----------------------------------
    |
    v
Developer Handles Everything
(Retries, Ranking, Failures)
    |
    v
Final Result
```

***

Bittensor is not broken, it’s simply not abstracted yet.

The difficulty comes from three main areas.

#### 1. Fragmentation

Each subnet behaves differently. There is no universal standard.

A developer has to:

* understand the purpose of each subnet
* learn its specific protocol
* test nodes individually

This slows down adoption significantly.

***

#### 2. Unpredictability

Miners (nodes) are independently operated.

That means:

* Performance varies
* Outputs are inconsistent
* Availability is not guaranteed

One request might return an excellent result, while the next might fail entirely.

For experimentation, this is acceptable.\
For production systems, it is not.

***

#### 3. Missing Developer Layer

Modern infrastructure tools provide:

* Authentication
* Billing
* Usage tracking
* SDKs
* Documentation

Bittensor intentionally does not focus on this layer. It provides the network, not the interface.

That gap is exactly where LayerTao operates.

Developer Handles Everything (Retries, Ranking, Failures)