Network roles.
- STATUS
- Testnet
- CRATE
- tenzro-node
- STABILITY
- Stable
- TYPE
- Reference
Validator
Produces and finalizes blocks via HotStuff-2. Requires a staked TNZO deposit and a stable network. TEE attestation grants 1.5× leader-selection weight. Equivocation slashes 10% of stake.
ModelProvider
Serves inference for one or more registered models. The router schedules requests; health monitoring and reputation update per request. Earns TNZO per inference settled. The same role can also rent out spare compute — see Compute rental.
ComputeProvider
Rents out spare capacity by the epoch. Each epoch settles against a valid availability proof; settlement streams one epoch-slice at a time. Fixed or network-dynamic pricing. Rides the same stake that backs serving a model. Consumers pay from their TNZO balance; the provider earns into theirs.
StorageProvider
Offers free disk as content-addressed storage. Billed per byte-epoch; each epoch settles against a proof of retrievability. Shares one stake and one coverage budget with compute rental.
TeeProvider
Hosts confidential compute or sealed key management inside an attested enclave. Quotes are anchored on-chain. Tenants pay for enclave time in TNZO.
LightClient
Verifies headers and selectively replays state without storing the full chain. Suitable for desktops, mobile, resource-constrained machines. NAT traversal uses Circuit-Relay v2 plus DCUtR.
One stake, shared coverage
A node stakes once. Every role it takes on registers its obligations against that single stake through a shared coverage tracker. When the stake can no longer cover everything owed — a withdrawal, a slash, a new obligation — the node sheds obligations until the rest fits. There is no per-service bond.
Hardware profile
The CLI detects role-appropriate capacity at install time, including free disk available to offer as storage.
tenzro hardware
# CPU, RAM, free disk, NVMe IOPS, network, TEE vendor (TDX/SEV-SNP/Nitro/NVIDIA/Tiber)