Loading
Loading

Neuron registration trends
LLM providers charge different rates for identical models, and buyers pay retail without access to cheaper sources. Infrastructure operators running inference workloads have no way to monetize spare capacity or arbitrage pricing differences across providers. Centralized gateways also create vendor lock-in and expose request traffic to intermediaries.
A decentralized network where independent operators supply inference capacity from multiple providers simultaneously solves this through cryptographic attestation and per-request settlement. Each operator deploys a secure container that forwards buyer requests to their chosen upstream provider, keeps their API keys encrypted inside a TEE, and earns the difference between buyer retail and their upstream cost. The network's registry tracks which models each operator serves, validates their infrastructure through ARM/Azure configuration checks and image measurement attestation, and settles earnings on-chain.
gm implements this on Bittensor (subnet 28) by having miners deploy container workloads to Phala Cloud's confidential VMs, configure API keys for Anthropic, OpenAI, Google, Chutes, Z.ai, Moonshot, DeepInfra, KubeTEE, Engy, Moonmath, NEAR, and cloud backends (Azure OpenAI, Foundry, Bedrock), and declare which models they serve at what discount. The gateway (also TEE-secured) routes each buyer request to an eligible miner's declared model, verifies the response echoes the correct model identity, and the registry settles what the buyer paid minus the miner's declared discount.
Use cases were auto-generated from the GitHub repository and may not reflect the latest changes.
gm is a Bittensor subnet (netuid 28 mainnet, 482 testnet) where miners supply inference capacity from upstream LLM providers (Anthropic, OpenAI, Google, and 8+ others) through confidential VMs, while buyers access identical APIs through a gm gateway. Miners configure provider API keys, deploy containers to Phala Cloud, declare supported models, and earn the price spread between buyer and upstream costs.
gm uses a three-tier architecture: (1) Miners run in Intel TDX confidential VMs on Phala Cloud, containing Envoy data plane that forwards encrypted buyer requests to upstream providers, attestation server (attestd) that verifies ARM/Azure configuration, optional NEAR TLS verifier for certain routes, and RA-TLS certificate generation. (2) Gateway (operated by gm) runs inside a TEE, routes buyer requests to eligible miners based on model, price, and availability, verifies attestation quotes, and enforces per-response model echo checks. (3) Registry publishes approved image versions (keyed on compose_hash + os_image_hash), maintains miner hotkey registrations, tracks declared products/prices, runs periodic capability probes, and settles earnings. Buyers use standard OpenAI/Anthropic SDKs pointed at gm gateway; miner keys never leave TEE. Multi-key slots allow load-balancing across multiple API keys per provider.
Cloud backends (Azure OpenAI, Foundry, Bedrock) use separate ARM-verified credentials and deployment bindings. NEAR routes use in-image attestation verification before forwarding.
Drop-in access to Claude, GPT, and Gemini.
This information was auto-extracted from the GitHub repository and may be incomplete or out of date. Always refer to the subnet's GitHub repository for the latest instructions.
Payment model: (buyer_retail_price × (10000 - discount_bp) / 10000) minus upstream_cost_per_token = miner_profit_per_token. The registry handles per-offer admission and capability checks. Miner must declare products after deploy; undeclared models generate no revenue.
Different routes for same buyer product compete on price; gateway selects cheapest eligible route per request, giving each worker one lottery entry regardless of route count. Cloud deployments (Azure OpenAI, Foundry) require ARM-verified binding (deployment name must exactly match canonical model id) and registry capabilities upstream-model-echo and upstream-model-hop. Verified key slots enforced at runtime for direct Anthropic/OpenAI routes.
Earnings are served value (not on-chain payments or profit); settled per-token charges appear in registry's earnings endpoint.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository
Your prompts routed through a verifiable TEE.
FAQs were auto-generated from the GitHub repository and may not reflect the latest changes.
Holder & total-staked metrics as of 1h ago (hourly snapshot)
No local GPU required; upstream providers handle inference. Requires funded Phala Cloud account. Miner image is pre-built and pinned by digest.
No validator role documented in this subnet. Validation appears to be performed by registry capability checks and gateway routing logic.
Install Phala CLI and authenticate with a funded Phala Cloud account (create at https://cloud.phala.network)
npm i -g phala && phala auth login
Install gmcli binary from release (placed in ~/.cargo/bin)
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/taostat/gm-miner/releases/latest/download/gmcli-installer.sh | sh
Register serving hotkey with gm registry (provide ss58 directly or use btcli assisted flow with --wallet and --hotkey)
gmcli register-hotkey --hotkey-ss58 <ss58_address>
Authenticate with Taostats via device-code OAuth (credentials saved to ~/.gmcli/config.json)
gmcli login
Set provider API keys for upstreams you intend to serve (Anthropic, OpenAI, Google, Chutes, Z.ai, Moonshot, DeepInfra, KubeTEE, Engy, Moonmath, NEAR). Keys are encrypted in TEE, never seen by gm. Supports up to 8 semicolon-separated keys per provider for slot-based routing.
gmcli set-api-keys --anthropic sk-ant-... --openai sk-... --google AIza...
Run preflight checklist to verify network, login, keys, Phala CLI, and hotkey before deploying(optional)
gmcli doctor
Deploy miner: creates Phala CVM, verifies image hashes, registers worker. Takes a few minutes. Prints worker_id and app_id on success.
gmcli deploy
Declare which models you serve and at what discount off retail. Discount determines payout (10% discount = keep 90% of revenue). Can filter by provider with --provider flag.
gmcli declare-products --discount-pct 5
Check registration state and per-product eligibility and rates(optional)
gmcli status
Monitor lifetime served earnings and recent finalized epochs from registry(optional)
gmcli earnings