Join the testnet as a provider
tenzro join --provider takes a machine from bare metal to serving inference in one command — hardware detection, wallet, bond, registration, pricing, and a served model, all automatic.- Level
- Beginner
- Time
- ~10 min
- Prerequisites
- Linux or macOS box, CPU or GPU, public IP optional
- Stack
- CLI
Start a node
Providers run their own node. Hardware — CPUs, RAM, GPUs and VRAM, TEE capability — is detected at startup with no configuration.
tenzro-node --roles model-provider --data-dir ./dataBecome a provider in one command
Against the running node, one command provisions your identity and wallet, funds it from the testnet faucet, posts the 1,000 TNZO compute bond, registers you as a model provider with default per-token pricing, and downloads + serves the largest catalog model that fits your machine. TEE capability is enrolled when the hardware carries it.
tenzro join --providerNo config files, no flags beyond --provider. Use --rpc <url> to target a node you operate remotely.
Watch demand arrive
Capacity advertisement is automatic — your node broadcasts its registered capacity on the provider gossip topic, and the router places real requests against your endpoint. Reputation accrues per served call and settlement is in TNZO.
tenzro provider status --detailedCompare advertised and measured capacity
The capacity view lists every provider's advertised claim next to the throughput the node has actually measured, along with p95 latency and a reputation-discounted throughput figure. Consumers rank on observed behaviour, not the claim alone.
tenzro provider capacityTune pricing and models (optional)
Every automatic step is individually controllable. Adjust per-token pricing, serve additional models, or increase your bond for a higher reward multiplier.
tenzro provider pricing set \
--input-price-wei 100000000000000 \
--output-price-wei 200000000000000
tenzro model serve qwen3-0.6b
tenzro provider bond increase --did <your-did> --address <your-address> --amount 500Leave and recover your bond
The bond sits in a vault derived from your provider DID — nobody holds its key. Recovering it is two-phase: withdraw starts a cooldown, finalize returns the funds once it elapses. The gap is what stops a provider exiting ahead of a dispute filed against work it already served. bond paramsreports the node's minimum and the cooldown length.
tenzro provider bond params
tenzro provider bond withdraw --did <your-did> --address <your-address>
# ...after the cooldown
tenzro provider bond finalize --did <your-did> --address <your-address>