Requirements
Hardware, software, and network requirements for local and proxy nodes.
What you need depends on the node type.
Figures marked (inferred)
Items marked (inferred) come from the node's code and defaults, not published specs — treat them as guidance, not a guarantee.
Local inference node
Scales with the model you pick — the CLI wizard filters the catalog to what your free memory holds.
Prop
Type
Proxy node
No weights — the work is outbound API calls, so it stays light.
Prop
Type
Both node types
- Persistent identity: the device identity under
~/.venna/(a mounted volume under Docker) must survive restarts; losing it forfeits earnings attribution. - Connectivity: a persistent outbound connection with reconnect backoff. A mid-stream disconnect ends that job incomplete.
- Account: an operator account to pair against via the RFC 8628 device flow.
Next steps
- Run a node — pair, serve, and start earning from the node CLI.
- Node overview — the pair → serve → earn lifecycle and how local and proxy nodes differ.