Connect your worker
Portal signup and cryptographic admission use different invitations. Request a network invitation with the worker role, the authority public key through a trusted channel, a relay address and your node configuration from the operator.
- Build Sangama and prepare the supported Qwen shard files locally.
- Create a persistent identity. Share only the peer ID/public key with the operator.
- Save your network invitation to a private file (0600), then redeem it locally. Your worker signs the challenge; never upload its private key here.
- Start the managed node. It begins unloaded; the local inference UI can allocate prepared shards and check readiness.
target/release/sangama mesh-identity --state-dir .mesh/worker target/release/sangama mesh-join --config worker.json --invitation-file /path/to/private-invitation python3 scripts/mesh-node.py --config worker.json
Understand your status
- Registered
- A directory entry exists; no network access is implied.
- Admitted
- A peer key has valid scoped membership. It may still be offline.
- Reachable / loaded / ready
- Checked by your local UI against configured bridges. A complete verified route is needed to generate.
- Interrupted
- Recover workers, allocate/check the route and start a new request. Previous KV state is not resumed.
The portal cannot measure worker memory or relay paths. Model weights and credentials stay on your computer. Participating workers can inspect their inference data.