---
sidebar_position: 6
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lium.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Staging (Testnet)

Lium runs a parallel staging environment on Bittensor **testnet Subnet 37** so you can validate your provider setup without spending mainnet TAO. Use it to test hardware, debug node registration, or try new node configs before pointing them at production Subnet 51.

:::warning Test TAO has no real value
Test TAO is free from the Bittensor testnet faucet but cannot be exchanged for real TAO and earns no real rewards. The staging environment is for verification only.
:::

## What's different from mainnet

| | Mainnet (production) | Staging (testnet) |
|---|---|---|
| Bittensor subnet | `51` | `37` |
| Bittensor network | `finney` | `test` |
| Provider Portal | [provider.lium.io](https://provider.lium.io) | [provider.staging.lium.io](https://provider.staging.lium.io) |
| Renter UI | [lium.io](https://lium.io) | [staging.lium.io](https://staging.lium.io) |
| Validator hotkey | `5F7X5UpKSr26KU3jKfpLmT8kuKtBNyHhEnfS8xtxPCqCb13p` | `5DHgdomxxHSQf7neJWcagvGhTMKpqvKWwuprEaFF8C653qty` |
| TAO source | exchange / wallet transfer | testnet faucet |

## Get started in 5 min

### Step 1 — Get test TAO and register on subnet 37

```bash
# Request test TAO (rate-limited; rerun if your balance is still 0)
btcli wallet faucet --wallet.name <wallet> --network test

# Register your hotkey on testnet subnet 37
btcli subnet register --netuid 37 --network test \
  --wallet.name <wallet> --wallet.hotkey <hotkey>
```

### Step 2 — Point the provider at testnet

If you self-host the coordinator, set these two values in `neurons/miners/.env` before `docker compose up -d`:

```bash
BITTENSOR_NETUID=37
BITTENSOR_NETWORK=test
```

Everything else in [Self-Hosted Provider Setup](./self-hosted-provider.md) works the same.

### Step 3 — Sign in to the staging Provider Portal

1. Add your testnet hotkey to a supported wallet extension — e.g. the [Polkadot.js extension](https://chromewebstore.google.com/detail/polkadot%7Bjs%7D-extension/mopnmbcafieddcagagdcbnhejhlodfdd) or the [Bittensor Wallet extension](https://chromewebstore.google.com/detail/bittensor-wallet/bdgmdoedahdcjmpmifafdhnffjinddgc).
2. Sign in at [provider.staging.lium.io/signature-login](https://provider.staging.lium.io/signature-login).
3. Add your GPU node from the staging portal — same flow as [Node Quickstart](./nodes/quickstart.md), just registered against the staging environment.

:::tip Attaching a node via the provider CLI
If you skip the portal and use `add-executor` directly (see [Self-Hosted Provider Setup → Add a node from the CLI](./self-hosted-provider.md#add-a-node-from-the-cli)), pass the staging validator hotkey explicitly:

```
--validator 5DHgdomxxHSQf7neJWcagvGhTMKpqvKWwuprEaFF8C653qty
```
:::

To exercise the rental side end-to-end, place a test rental from [staging.lium.io](https://staging.lium.io) using a separate testnet wallet.

## Next steps

- [Quickstart](./quickstart.md) — repeat the flow on mainnet once staging looks green.
- [Self-Hosted Provider Setup](./self-hosted-provider.md) — full coordinator setup, applies the same way to either network.
- [Node Quickstart](./nodes/quickstart.md) — bring your first GPU online.