Glossary
A
AVS
Autonomous Verifiable Services.
C
Console
NodeOps Console is the user interfacewhich Node Runners use to deploy and manage their Nodes.
Compute Unit
The unit of measurement for the provider machine’s capacity.
D
DePIN
Decentralized Physical Infrastructure Networks: leveraging blockchain and decentralized technologies to power and govern real-world physical infrastructure. This approach supports systems where infrastructure —such as telecommunications, energy grids, transportation networks, or IoT devices— is owned, operated, and maintained by decentralized participants rather than centralized entities.
Docker image
A Docker image is a pre-packaged environment containing everything needed to run an application, including code, dependencies, and system libraries.
When specifying a Docker image in your template, ensure:
• The image is public so that it can be pulled during deployment
• You provide the correct image version using a digest (SHA256) or tag
Example:
image: jupyter/base-notebook@sha256:8c903974902b0e9d45d9823c2234411de0614c5c98c4bb782b3d4f55b3e435e6
E
L
localhost
Localhost refers to the current device used to access a network service. It's often associated with the IP address 127.0.0.1 and the hostname localhost.
It's used for:
- Testing web applications locally
- Accessing services running on the same machine
- Loopback communication
M
Machine
Machines are individual compute infrastructure units that a provider wants to add to NodeOps Cloud. Machines have to added to the NodeOps Network under each provider using the "Add Machine" process which is part of the provider onboarding process.
N
NaaS
Node as a Service: a simplified way for anyone to run Web3 protocol or blockchain nodes.
Node Operators
Node Operators are end users, the Node Runners who deploy the nodes that they own using partner service provider front ends.
The NodeOps team is the team behind the NodeOps Network, which is why we are our own favored partner! Run a Node from the NodeOps Console.
O
Operator
Operators are individuals or groups interested in participating in the validation of tasks related to node deployment through the NodeOps Network Autonomous Verifiable Services (AVS).
Operator Onboarding
Operator onboarding refers to a series of steps a restaking operator must perform to opt into supporting the NodeOps Network AVS.
P
Provider
A provider is an individual or group interested in lending their underutilized or un-utilized hardware infrastructure(machines) for workloads deployed using NodeOps Network.
Provider Onboarding
Provider onboarding is a collection of steps that a provider must perform to join the NodeOps Network's pool of providers.
Provider Pool
A collection of compute providers registered with the NodeOps Network to lend their compute resources for any workloads deployed using the console.
S
Scheduling
Scheduling means the process of finding the right machine for a node deployment request.
Secrets
Secrets such as API keys are sensitive data. Storing such data on disk can pose security risks.
Here are some best practices for handling secrets:
- Use environment variables for sensitive configuration.
- Implement secret management systems (e.g., Kubernetes Secrets, HashiCorp Vault).
- Encrypt data at rest if disk storage is necessary.
- Use temporary in-memory storage for short-lived sensitive data.
Browse the OWASP secret management cheat sheet to learn more.
T
Template
A template is Infrastructure as configuration playbook: a YAML file that defines how an application should run within our marketplace. It specifies:
• The public Docker image to be used
• Resource allocation (CPU, memory)
• Environment variables (with placeholders for user input)
• Whether the application should be exposed to the internet
It acts as a blueprint, ensuring consistent deployment configurations for users.
W
Workload
A node deployed on a Provider machine is called the Workload.