# NodeOps Network Documentation > Deploy nodes, rent compute, and manage DePIN infrastructure. NodeOps Network is a decentralized physical infrastructure network for blockchain Node deployment, GPU/CPU Compute rental, $NODE staking, and Web3 infrastructure management. --- ## Core Services ### NodeOps Ecosystem > Explore the NodeOps Network ecosystem: DePIN Cloud Marketplace, Console for managed Nodes, DeFi staking, AI tools, and enterprise infrastructure. URL: https://docs.nodeops.network/Core-Services Welcome to **NodeOps Network**: the leading chain-agnostic, DePIN orchestration layer for general-purpose Compute. This permissionless Network enforces no exit terms, and no long-term commitments. Our mission is simple: remove the complexity of running technical infrastructure so anyone can access and benefit from decentralized Cloud. ## Ecosystem participants The NodeOps ecosystem is [governed by the DAO](/Tokenomics/governance), while the Protocol itself is verified by [Node Orchestrators](/Learn/Ecosystem/nodeorchestrator). A wide range of users leverage the products and services, from people using apps with no idea they are hosted on NodeOps, to digital asset enthusiasts, to non-technical Node license holders, to developers deploying apps and infrastructure in the DePIN Cloud. ## Product and services NodeOps Network provides the following core products and services, coordinated by the Protocol and driven by the [\$NODE economy](/Tokenomics/node.md). ### 1. NodeOps Cloud Permissionless DePIN Cloud Marketplace for verifiable generalized Compute: allowing anyone to provide, purchase, deploy, and manage decentralized Cloud. The NodeOps ecosystem rewards all participants for their involvement, whether you are on the supply or demand sides of the Network (or both). | Supply side | |Demand side | |-----------------------------------------------------------|-|------------| |[Provide Compute](/Get-Started/Cloud-Compute/Provide-Compute/README.md)| | [Farm Compute](/Guides/Marketplace/farm) | |[Provide a Cloud template](/Guides/Marketplace/Configure-Compute)||[Deploy a Cloud template](/Get-Started/Cloud-Infrastructure/deploy)| [Hardware providers](/Learn/Ecosystem/providers) earn when their Machines that make up the DePIN Cloud run workloads. Those workloads are created when users [deploy](/Get-Started/Cloud-Infrastructure/deploy.md) templatized apps, environments, and infrastructure. The developers who [provide those templates](/Learn/Products/Cloud/Cloud-Infrastructure/README.md) also earn a share of the workload triggered when a user runs their template/s. And, finally, users [earn rewards](/Guides/Community-Incentives/points#earn-gnode) when they leverage NodeOps' products and services. > - Launch Cloud services from the [Marketplace app](https://cloud.nodeops.network/), or a subset of these direct from the [Telegram Bot](/Get-Started/enable-telegram-bot). > - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) to deploy apps, Nodes, environments, and Cloud infra at-a-click ### 2. NodeOps Console NodeOps Console makes the NodeOps Cloud infrastructure effortless with at-a-click services, bringing AI, Web3, and decentralized Cloud within reach of anyone, from seasoned engineers to complete beginners. No need to browse the template marketplace nor think about which version to use or what resources that workload needs: everything is abstracted away. With Console, you can launch and maintain Blockchain or Protocol Nodes in seconds. No manual setup needed, no steep learning curve. | Supply side | |Demand side | |-------------|-|-------------| |Enquire about [Node bootstrapping](https://share.hsforms.com/1hrTm5qFaQEuvqldNmIg6ngrr6lj)| | [Managed Node services](/Guides/Console/README.md) | NodeOps Console bridges the gap between Protocols needing to bootstrap and scale their Networks and Node runners looking for immediate opportunities to deploy Nodes and earn rewards. ### 3. DeFi services The vision of Web3 is to empower everyone to earn yield from the assets they hold. NodeOps makes this a reality across the ecosystem. These services are already live and generating real revenue for real people: #### Staking Together we are stronger: not everyone has the minimum number of tokens required to run a validator Node. That's why NodeOps offers our community the ability to gather together to pool their tokens and beat those minimum requirements. > [Drop your Stake](/Get-Started/DeFi-Services/stake.md) and earn dual incentives with [NodeOps Portal](https://portal.nodeops.network/). #### Liquidity release Don't just hoddle those NFTs, make them work for you. Drop supported NFTs into the NodeOps LNT vault in exchange for crypto. > [Drop your NFT/s](/Get-Started/DeFi-Services/liquidity.md) and release liquidity with [NodeOps Console](https://console.nodeops.network/). ### 4. Toolsets NodeOps' own dev team constantly build tools to solve the real-world problems they face. We don't hoddle these; we release them to you, the community and ask you to battle test them! #### Agent Terminal Open to beta testers: Collaborative AI and blockchain developer sandbox. The Agent Terminal provides a developer-friendly environment for experimenting, building, and deploying AI solutions in real time. Whether you're working on small-scale agents based on OpenAI technologies, or testing advanced AI workloads. > [Build AI Agents](/Get-Started/Cloud-Tools/agent-terminal.md). #### Security Hub NodeOps Security Hub provides an at-a-click, AI-powered code vulnerability service protecting you from exposed apps and code. You keep your finger on the pulse with personalized alerts when the apps or tech stack you rely on are flagged as impacted by malicious code. > [Scan for vulnerabilities](/Get-Started/Cloud-Tools/scan.md). ### 5. NodeOps Enterprise Enterprise-grade B2B Node services: for robust and reliable RPC and Validator Nodes supporting Enterprise Staking infrastructure. > Enquire about the [NodeOps B2B](https://share.hsforms.com/1hrTm5qFaQEuvqldNmIg6ngrr6lj) services. > **Info: Our Goal** At NodeOps, our goal is not just to provide the infrastructure, but to nurture an ecosystem where decentralization thrives organically. We envision a future where deploying infrastructure is as seamless as contributing to it, fostering a paradigm where everyone β€” be it a no-code user, solo developer, large Protocol, or traditional enterprise can focus on innovation without being bogged down by operational complexities. ## What next? - If you wish to leverage any of NodeOps Core services, please review NodeOps' [Terms & Conditions](https://nodeops.network/terms) - Understand how we use your data with our [Privacy policy](https://nodeops-public.hel1.your-objectstorage.com/privacy.pdf) - Learn more from our [competitive positioning](https://nodeops.network/blog/nodeops-network-a-decentralized-compute-layer) article in our blog --- --- ## Get Started ### Verify Compute > Become a Node Orchestrator on NodeOps Network. Deploy an orchestrator Node, delegate your UNO NFT, and earn gNODE rewards by verifying DePIN Compute. URL: https://docs.nodeops.network/Get-Started/Cloud-Compute/node-orchestrator 🌟 Status: Live > **Tip: TL;DR** Earn by verifying the Compute that providers bring to the Cloud Marketplace: - Hold an [UNO NFT](/Guides/Community-Incentives/uno) - Deploy the Orchestrator Node - Delegate the UNO to the Node This page details how to become a [Node Orchestrator](/Learn/Ecosystem/nodeorchestrator) and earn while verifying the NodeOps Compute layer, with step-by-step guides. ## Become a Node Orchestrator on the NodeOps Network ## Prerequisites - EVM-compatible wallet holding an [UNO NFT](/Guides/Community-Incentives/uno) > UNO are still [available for sale](https://portal.nodeops.network/) - [Console](https://console.nodeops.network/) or [Marketplace](https://cloud.nodeops.network/) account - Sufficient funds to deploy the Node ### Step 1. Deploy an Orchestrator Node 1. Connect to wallet that holds your UNO NFT to the [NodeOps Cloud Marketplace](https://cloud.nodeops.network/) or the [NodeOps Console](https://console.nodeops.network/). 2. Choose the Orchestrator Node to deploy: Navigate to the [Template Marketplace](https://cloud.nodeops.network/marketplace) page and select the **Orchestrator Node** card. Navigate to the [Node Deployment](https://console.nodeops.network/deployNode) page and select the **Orchestrator Node** card. Click on the card to begin the subscription flow. **Show me** 3. Select the Compute provider for this Node, or accept the default **Go with my preference** and click **Continue**. 4. Click **Fetch NFT** to validate that you have an available UNO to deploy to this Node, click **Next**. 4. Select the duration to run this Node for or accept the default of one month and pay. > Learn more about [payment options](/Get-Started/Pay-for-Services#payment-within-nodeops). 5. Click **Purchase & Deploy**. ### Step 2. Delegate the UNO NFT to your Node 1. Locate the deployed Node: From your [Deployments](https://cloud.nodeops.network/deployments) page, click the card for the Orchestrator Node you have set up. From your [NodeFolio](https://console.nodeops.network/dashboard) page, click the card for the Orchestrator Node you have set up. **Show me** 2. Click **Delegate** to link your selected UNO with the Operator wallet that controls this Node. 3. Confirm the delegation event in your wallet. Congratulations, you are now earning [gNODE](/Guides/Community-Incentives/points) for verifying [Compute provider](/Get-Started/Cloud-Compute/Provide-Compute/README.md) SLAs for NodeOps Network Protocol. ## What next? - Learn more about the [UNO NFT](/Guides/Community-Incentives/uno) - Learn more about the [gNODE](/Guides/Community-Incentives/points) you earn - Learn more about the [Node Orchestrator's role](/Learn/Ecosystem/nodeorchestrator) within NodeOps Network Protocol --- ### Provide Compute > Learn how to provide decentralized Compute on NodeOps Network. Bond $NODE, register machines, and earn rewards on the DePIN Cloud Marketplace. URL: https://docs.nodeops.network/Get-Started/Cloud-Compute/Provide-Compute To become a provider of high-availability, decentralized Compute: 1. Connect wallet to the [Cloud Marketplace](https://cloud.nodeops.network/) 2. Bond: - 2000 \$NODE + 200 \$NODE for every CU 3. Add Machine/s > πŸ‘‰ Run one line of code to P2P **Show me video** ## Earn rewards for providing Machines Each 2CU provided earns up to 10 \$NODE per day: - Base reward: 8 \$NODE - Performance rewards: up to 2 \$NODE ## Compute requirements for Machines on NodeOps Cloud Marketplace > **Info: Machines **must**** Comply with the minimum hardware and port requirements: - CPUs or vCPUs: β‰₯2 - GB RAM: β‰₯4 - SSD storage: β‰₯80GB NVMe Storage - Network bandwidth: β‰₯1Gbps unlimited - Uptime: β‰₯ 99% - OS: Debian (12+) or Ubuntu (22.04+) installation with: - Linux kernel 6.7+ - Latest security patches - Allow traffic on ports: - UDP 8472,51820 - TCP 10250 - Public static IPv4 address - Run the Protocol at root > **Warning: Machines **must not**:** - Run additional workloads - Have third-party applications or monitoring agents installed - Enable [SWAP](https://wiki.archlinux.org/title/Swap) - Be exposed to intervention with the workload or machines > **Info: Run at root** NodeOps Network's integration must be run directly on a machine at root: - You can't run it in Docker - Don't run it on a homelab ## What next? - Register as a [Compute provider](./register-to-provide.md) - Understand more about [managing a Machine](/Guides/Marketplace/Manage-Machines) - If you just want to run a proof of concept, but don't have a Machine with enough capacity, don't worry, you can re-sell [Cloud Compute](/Guides/Marketplace/Provide-Compute/provide-gcp-compute.md) - Learn about [unbonding your \$NODE](/Guides/Marketplace/marketplace-account#unbond-node) --- ### Register a Machine > Step-by-step guide to register a machine on the NodeOps Cloud Marketplace. Bond $NODE, run the setup command, and start providing DePIN Compute. URL: https://docs.nodeops.network/Get-Started/Cloud-Compute/Provide-Compute/register-a-machine 🌟 Status: Live on Mainnet > **Tip: TL;DR** - Run one line of code to register your Machine - Bond $NODE according to your Machine's CU This page details the Machine registration process, with video and step-by-step guides. ## Register a Machine on NodeOps Cloud Marketplace **Show me video of the flow** ## Prerequisites - [Registered as a provider](register-to-provide.md) - Dedicated Machine or virtual Machine satisfying the [minimum requirements](./README.md#compute-requirements-for-machines-on-nodeops-cloud-marketplace) - Wallet with - β‰₯0.01 Arbitrum ETH - $NODE on the Arbitrum network: - 2000 \$NODE + 200 \$NODE for every CU - Optional: Email address > While an email is optional, it's required to receive alerts about the status of any Machines you supply ## Register a new Machine ### Step 1. Collect the code to run on your Machine 1. Logged in to the [Cloud Marketplace](https://cloud.nodeops.network/) > **Compute** > **+ Farm Compute**. **Show me** 2. Select **Add My Own Machine** > **Continue** > Determine how many machines > **Continue**. **Show me** 3. Sign the 2 transaction requests in your wallet. Congratulations, the Protocol has registered your Machine and provided it with a unique identifier. 4. Copy the setup code: from the **All** or the **Pending** tab, click **Setup** > **Copy**. > Refresh the page if your Machine doesn't appear in the tab. **Show me** ### Step 2. Make the Machine available > **Info: Your Machine will remain in "PENDING" status until the command you generated in Step 1 is executed on that Machine.** 1. Open the command line interface on the Machine you wish to add. Run the command provided in Step 2 at root on the Machine you wish to add. > This code makes the Machine available on the NodeOps Network and the secret identifies it. **Show me** > See the [Gotchas](#copy-error) if this step fails. 2.2 Upon the command's successful execution, the Machine will be visible under the **All** tab in the "AWAITING-STAKE" state. ### Step 3. Bond $NODE to the Machine 1. Click **Bond**. > The value of the bond is determined by the number of [CUs](/Learn/Glossary/compute-unit) the machine offers. **Show me** 2. Confirm the transaction in your wallet. 3. Your Machine's state changes to "CONFIGURING" and then to "ACTIVE." ## Gotchas ### Copy error An error such as `cannot create regular file '/usr/local/bin/nn-provider': Permission denied` means you didn't create a user account at root for NodeOps Cloud with the correct permissions to run the code. You can get around this on Ubuntu by downloading the script locally and then running these with `sudo`. That means: ``` curl -L | sh -s - ZxEsuA******************zAJ6 ``` becomes ``` curl -L -o nn-installer.sh chmod +x ./nn-installer.sh sudo sh nn-installer.sh ZxEsuA******************zAJ6 ``` ### Rejected Machines Your machine will be rejected if: - It runs workloads in addition to the NodeOps Network assigned loads - If [SWAP](https://wiki.archlinux.org/title/Swap) is enabled ## Troubleshooting Q. Can I check why my machine is not transitioning to active state? A. Yes. From the machine terminal, and run the following command to check if you're facing any issue or if you haven't met the requirements. ```shell journalctl -fu nn-provider* ``` Congratulations, you are providing decentralized Compute via the NodeOps Network's Protocol on Arbitrum. ## What next? - To view your Machines, click on **ACTIVE Machine**. New Machines can take several minutes to display these details. - Learn more about [the provider role](/Learn/Ecosystem/README.md) - Understand more about your [Machine's status](/Guides/Marketplace/Manage-Machines/machine-status.md) - Learn about the [gNODE](/Guides/Community-Incentives/points) rewards that providers earn - Learn more about [\$NODE](/Tokenomics/node) that gNODE converts to - Learn how to [unbond your \$NODE](/Guides/Marketplace/marketplace-account#unbond-node) that was previously bonded to Compute --- ### Register as a provider > Register as a Compute provider on NodeOps Network. Connect your wallet, bond $NODE, and supply machines to the decentralized Cloud Marketplace. URL: https://docs.nodeops.network/Get-Started/Cloud-Compute/Provide-Compute/register-to-provide 🌟 Status: Live on Mainnet > **Tip: TL;DR** Connect your wallet to register and bond \$NODE to become a Machine provider. [Providers](/Learn/Ecosystem/providers.mdx) are a vital element of the NodeOps Network. They bring computing resources (Machines) to the Network to run all manner of workloads. This page details the registration process, with video and step-by-step guides. > **Important: Remember to top up with Arbitrum ETH for gas.** ## Register as a Provider on NodeOps Cloud Marketplace **Show me video of the flow** ## Prerequisites - Wallet with - β‰₯0.01 Arbitrum ETH - $NODE on the Arbitrum network: - 2000 \$NODE + 200 \$NODE for every CU - Optional: Email address > While an email is optional, it's required to receive alerts about the status of any Machines you supply ## Step 1: Register on the NodeOps Network platform 1. From the [Marketplace dashboard](https://cloud.nodeops.network/), log in and connect a wallet to get started. **Show me** 2. Click **+ Farm Compute** > **Add My Own Machine** > **Become Provider** to begin the Machine provider flow. **Show me** ## Step 2: Bond $NODE 1. Click **Bond and Become a Provider** to initiate the process to allow the NodeOps Network Protocol to bond \$NODE. Confirm the transaction in your wallet. **Show me** 2. Approve the fee in Arbitrum ETH to allow NodeOps Network to bond \$NODE. ## What next? Congratulations, you are now registered as a provider and can: - [Register a Machine](register-a-machine.md) - [Learn more about becoming a provider](/Learn/Ecosystem/README.md) - Learn how to [unbond your \$NODE](/Guides/Marketplace/marketplace-account#unbond-node) --- ### Rent Compute > Rent decentralized Compute from the NodeOps Cloud Marketplace. Farm crowd-sourced machines and earn gNODE rewards for your workloads on the DePIN network. URL: https://docs.nodeops.network/Get-Started/Cloud-Compute/rent-compute 🌟 Status: Live on Mainnet This page details how you can rent a Machine from the crowd-sourced Compute on NodeOps Network. > **Tip: Earn rewards** Renting a Machine gives you the opportunity to earn [gNODE rewards](/Guides/Community-Incentives/points) for the workloads run on that Machine. > **Important: πŸ›‘ Are you sure you want to rent a Machine?** - You will not be provided with SSH access to Machines you rent from the NodeOps Cloud Marketplace: this is not a traditional VM - Renting a Machine is such a unique flow when compared to the Cloud Hyperscaler ecosystem that we coined a new term for it: [Farm Compute](/Guides/Marketplace/farm) - Most customers access Compute from NodeOps Cloud Marketplace indirectly, by selecting a [tool or service](/Core-Services#product-and-services) > **Note: 🚧 Status: Coming soon** You will be able leverage the Compute you rent by: - [Selecting the Machine when you deploy templates](/Guides/Marketplace/Manage-Machines#option-1-assign-specific-workloads-to-designated-machines) - [Setting the Machine as a preference for auto assigning](/Guides/Marketplace/Manage-Machines#option-2-set-up-a-preferred-machine-or-provider) - [Sharing the Machine Id](/Guides/Marketplace/Manage-Machines#option-2-use-your-own-resources) with others to set it as their preference ## Prerequisites - Wallet with - β‰₯0.01 Arbitrum ETH - [Cloud Marketplace account](https://cloud.nodeops.network/) ## Rent a Machine from the Cloud Marketplace Use the walkthrough or video provided to rent a Machine from NodeOps Cloud Marketplace. **Show me video** 1. Logged in to the [Cloud Marketplace](https://cloud.nodeops.network/) > **Compute** > **+ Farm Compute**. **Show me** 2. Select **Rent Machine**, determine: - How many machines - Number of CUs and click **Continue**. **Show me** 3. Select duration in months and decide [how to pay](/Get-Started/Pay-for-Services#step-2-pay-for-a-subscription-or-service): - Available credits - Promo code - Payment partner and click **Deploy**. **Show me** Congratulations, once the Machine's status updates to active, you may click on it's name and view the monitoring logs. > Learn how to [assign workloads to this Machine](/Guides/Marketplace/Manage-Machines) to improve its yield Notice that a Machine you rent has the **Occupied** label which differentiates it from any Machine that you [provide](/Get-Started/Cloud-Compute/Provide-Compute/README.md) to the Network. **Show me** ## What next? - [Add workloads to your rented Machine/s](/Guides/Marketplace/Manage-Machines) to earn [gNODE](/Guides/Community-Incentives/points) rewards - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) - Understand [converting](/Guides/Community-Incentives/points.md) the [gNODE](/Guides/Community-Incentives/points) rewards to \$NODE - Learn more about the NodeOps Ecosystem [core services](/Core-Services) --- ### Create templates > Create and upload Cloud templates to the NodeOps Marketplace. Build apps, agents, or infrastructure configurations and earn from workload deployments on DePIN. URL: https://docs.nodeops.network/Get-Started/Cloud-Infrastructure/create ## Create a Cloud Template Developers are able to create and upload templates to the Cloud Marketplace. Significant efforts are underway to make templates a first-class citizen of the NodeOps Compute offering. Currently, as a developer, to get started you need to: - Prepare a template for a working app, agent, or an environment or infrastructure configuration - Upload the template to the Cloud Marketplace and either, submit this for review or publish privately > You can earn a share of the workload fee when users deploy your template. Use the guides as your Get Started flow: 1. [Dockerize your App](/Guides/Marketplace/Configure-Compute/public-docker). 2. [Create and upload the template](/Guides/Marketplace/Configure-Compute/upload-template). ## What next? - Learn more about the NodeOps Ecosystem [core services](/Core-Services) - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) - Understand more about [template requirements](/Reference/template-schema.md) - Learn more about pricing and the difference between [private and public templates](/Learn/Products/Cloud/Cloud-Infrastructure/README.md) --- ### Deploy templates > Deploy Cloud templates on the NodeOps Marketplace. Select, configure, and launch apps and infrastructure on decentralized DePIN Compute in minutes. URL: https://docs.nodeops.network/Get-Started/Cloud-Infrastructure/deploy ## Prerequisites - Account on the [Compute Marketplace](https://cloud.nodeops.network/) - Sufficient funds ## Get started with templates Use the video or walkthrough to understand how deploy apps and infrastructure by selecting, paying, and using a template from NodeOp's Cloud Marketplace. **Show me video** ### Step 1: Select template 1. Logged into the [Compute Marketplace](https://cloud.nodeops.network/marketplace), navigate to **Template Marketplace**. **Show me** 2. Choose your template by clicking the card you want. **Show me** > Notice the filters on the right hand side of the dashboard to help you search the template options. ### Step 2: Set up and pay 1. Click **Deploy Template** and select which Machine the template will deploy on, if in doubt, select **Auto assign** and click **Continue**. > Learn about [delegating workloads to a specific Machine or Provider](/Guides/Marketplace/Manage-Machines). 2. Configure the min/max resources this template may consume, or leave the default and click **Next**. **Show me** 3. Click **Pay & Deploy**. ### Step 3: Access your template's entrypoint 1. Navigate to **My Deployments** within the Account menu. **Show me** 2. Select the template you wish to leverage. > Ensure the template's status is **Deployed**, a "deploying" template has no endpoint. 3. Click **Endpoints** and access the entry point to the workload of the template. **Show me** ## What next? - Learn more about the NodeOps Ecosystem [core services](/Core-Services) - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) - Learn about [delegating workloads to a specific Machine or Provider](/Guides/Marketplace/Manage-Machines) - Learn about how playbooks assist you to [configure your Compute Infrastructure](/Learn/Products/Cloud/Cloud-Infrastructure/README.md) --- ### Develop AI agents > Develop AI agents on NodeOps Network using the Agent Terminal sandbox. Access decentralized DePIN Compute from a hosted development environment. URL: https://docs.nodeops.network/Get-Started/Cloud-Tools/agent-terminal 🌟 Status: Open to beta testers on Mainnet > **Tip: TL;DR** Log in with your wallet to access Compute from a familiar development environment. The developer sandbox allows users to connect their AI agents direct to the Compute they need. ## Prerequisites for beta testers - EVM-compatible wallet ## Get started with Agent Terminal This guide supports beta testers to access the agent developer platform from NodeOp's marketplace to automatically integrate with the Compute they need. ### Step 1: Request access as a beta tester 1. Navigate to your **Profile** and copy your User Id. 2. Pass a NodeOps team member your User Id to have this feature turned on. > Ask if you may be assigned credits. **Show me** ### Step 2: Provision your sandbox with Compute Once you have been assigned credits / promo code: 1. Navigate to **Deploy Templates** and open the app **AI Agent Terminal** **Show me** 2. Click to enter the app and choose **Auto assign** and **Continue**. **Show me** 3. Enter a password for your sandbox, click **Next**. 4. If you have a promo code, enter that or top up funds. **Show me** Congratulations, your terminal's status becomes **Deployed** **Show me** ### Step 3: Access your sandbox 1. Logged in to your [NodeOps account](https://cloud.nodeops.network/), navigate to [My Deployments](https://cloud.nodeops.network/deployments). **Show me** 2. Double-click on your sandbox and click to follow the link to your hosted instance. **Show me** ## Use your Agent Terminal You now have access to your developer environment where you can connect with the extensions you know and love, and import resources from GitHub etc. **Show me** To open a terminal, navigate -> Hamburger -> Terminal -> New terminal, or use your shortcuts. **Show me** ## Gotchas - LLM models require their respective API keys. Ensure to set them in your environment variables before running the agent. ## What next? - Learn more about [Agent Terminal](/Learn/Products/Cloud/agent-terminal.md) - Learn how to [templatize your agent](/Guides/Marketplace/Configure-Compute/README.md) for orchestrated deployment on NodeOps Cloud. --- ### Scan vulnerabilities > Scan Docker images for vulnerabilities and generate SBOM reports using the NodeOps Security Hub. Protect your DePIN infrastructure with built-in tools. URL: https://docs.nodeops.network/Get-Started/Cloud-Tools/scan 🌟 Status: Available on Mainnet > **Tip: TL;DR** Log in to the [Marketplace](https://cloud.nodeops.network/scan) to access vulnerability and SBOM reports from an intuitive dashboard. ## Overview The NopeOps Marketplace Dashboard provides an [integrated vulnerability scanner](https://cloud.nodeops.network/scan) to allow you to verify the integrity of: - 🚧 Codebases / repositories - Public Docker images (including Marketplace templates) ## Prerequisites - [Marketplace account](https://cloud.nodeops.network/) - For recurring scans, a registered email - Publicly available resource to assess ## Scan for vulnerabilities with Security Hub This guide supports you to understand how to scan for vulnerabilities with the NodeOps Marketplace Security Hub. Use the video or steps to understand the flow. ### Step 1: Access the tool Logged in from your [account](https://cloud.nodeops.network/), navigate the left hand menu to **Security Hub**. **Show me** ### Step 2: Scan your resource 1. Click **Upload for Scanning**. **Show me** 2. Enter a publicly-available Docker image name and choose scan type: - Vulnerability - SBOM **Show me** 3. (Optional) Click **Enable Recurring Scan**. This requires that you have an email linked to your Marketplace account to receive alerts on. ### Step 3: Review the analysis > **Tip: You may view the scan's progress by clicking the resource name.** **Show me** 1. Once the scan is complete, click the resource name to view a summary. > Reload the page if necessary. **Show me** 2. Click the summary block to deep dive into the scan details. **Show me** Congratulations: you can now deep-dive into the vulnerabilites identified by the scanner. ## What next? - Follow the [User Guide](/Guides/Marketplace/Monitor-Infrastructure/manage-scans.md) to manage your scans - To test an [OWASP-issued](https://owasp.org/) Docker image of an app with known vulnerabilities, consider scanning `bkimminich/juice-shop` - [Learn more about the Security Hub](/Learn/Products/Cloud/security.md) --- ### Commission service > Delegate your NFT Node license to NodeOps and earn instant rewards via commission-based Node-as-a-Service on the decentralized DePIN network. URL: https://docs.nodeops.network/Get-Started/Console/commission-based 🌟 Status: Live > **Tip: TL;DR** Connect to [Console.NodeOps.Network](https://console.nodeops.network/node-delegation) to delegate your NFT Node-running license and start earning instant rewards. **Show me supported Protocols** - [0G](/Guides/Console/Managed-Nodes/og-alignment) - Arbitrum - [Carv Checker license](/Guides/Console/Managed-Nodes/carv) - [Xai Sentry license](/Guides/Console/Managed-Nodes/xai) - [Sophon Guardian license](/Guides/Console/Managed-Nodes/sophon/commission) ## Follow a basic walkthrough to understand the Commission-based flow This Get Started uses [0G](/Guides/Console/Managed-Nodes/og-alignment) as an example. Note that some Protocols may require: - Gas in the native token - Additional registration steps for the Node > Remember, if you are delegating a Node for commission-based earnings, you will **not** use the **Node Deployment** tab. Use the video or walkthrough to understand how to delegate NodeOps to run a Node with your NFT license. No need to set up or subscribe to run a Node. ### Prerequisites - EVM-compatible wallet with the 0G NFT ### Step 1: Connect Wallet > Remember to either sign in with the wallet that holds your 0G NFT, or to link that wallet to your account. ### Step 2: Delegate your NFT 1. Navigate to **Commissioned Delegation** and select 0G's **Register**. **Show me** 2. Navigate to the **My Delegations** tab then click **Delegate**. **Show me** 3. Select the NFT based on its identifier, and click **Approve**. **Show me** 4. Approve the delegation transaction in your wallet, click **Delegate**, then approve the final transaction. **Show me** Congratulations, your NFT is now earning commission. ### (Optional) Step 3: Review your delegations From the **Node Delegation** page, select the **My Delegations** tab to track your current NFT delegations. ## What next? - Follow the guide to learn more about using your [Console account](/Guides/Console/console-account.md) - [Undelegate your NFT](/Guides/Console/console-account.md#undelegate-your-nft) - Learn about the full set of [products and services](/Core-Services#product-and-services) offered across the NodeOps ecosystem --- ### Node-as-a-Service > Get started with NodeOps Console Node-as-a-Service. Deploy blockchain Nodes via subscription or commission-based delegation on the DePIN network. URL: https://docs.nodeops.network/Get-Started/Console With NodeOps Console you can: - [Pay a subscription to run a Node](/Get-Started/Console/subscription), or - [Delegate an NFT license to NodeOps](/Get-Started/Console/commission-based) who will take a commission to run the Node If you choose to pay a subscription to run a Node, you take 100% of the rewards. Should you delegate, then NodeOps takes a commission, a share of the rewards. ## NodeOps-supported Protocols | Protocol | Keys or license required | NFT delegation supported | |--------------------------|--------------------|--------------------| | [Aethir](/Guides/Console/Managed-Nodes/aethir.mdx) |Y| | | [Avail](/Guides/Console/Managed-Nodes/avail.mdx) |N | | | [Beam](/Guides/Console/Managed-Nodes/beam.mdx) |Y|| | [CARV](/Guides/Console/Managed-Nodes/carv.mdx) |Y | [Y](/Guides/Console/Managed-Nodes/carv#carv-commission-model)| | [Celestia](/Guides/Console/Managed-Nodes/celestia.mdx) |N | | | [Captain & Company](/Guides/Console/Managed-Nodes/capnco.mdx)|Y | | | [DIN](/Guides/Console/Managed-Nodes/din.mdx) |Y | | | [Fuse](/Guides/Console/Managed-Nodes/fuse.mdx) |Y | | | [Huddle01](/Guides/Console/Managed-Nodes/huddle01.md) |Y | | | [Hybrid](/Guides/Console/Managed-Nodes/hybrid.md) |Y | | | [Hychain](/Guides/Console/Managed-Nodes/hychain.md) |Y | | | [iAgent](/Guides/Console/Managed-Nodes/iagent/bootstrapping.md)|Y| | | [KIP](/Guides/Console/Managed-Nodes/kip.md) |Y | | | [Lumoz](/Guides/Console/Managed-Nodes/lumoz.md) |Y | | | [Nexus](/Guides/Console/Managed-Nodes/nexus.md) |N | | | [0G](/Guides/Console/Managed-Nodes/og-alignment.md) |Y | [Y](/Guides/Console/Managed-Nodes/og-alignment#delegate-your-0g-alignment-nft-to-earn-commission)| | [OpenPad](/Guides/Console/Managed-Nodes/openpad.md) |Y | | | [PlayAI](/Guides/Console/Managed-Nodes/playai.md) |Y | | | [Rivalz](/Guides/Console/Managed-Nodes/rivalz.md) |Y | | | [Sophon](/Guides/Console/Managed-Nodes/sophon/README.md) |Y| [Y](/Guides/Console/Managed-Nodes/sophon/commission)| | [Vemp Horizon](/Guides/Console/Managed-Nodes/vemp-horizon.md)|Y | | | [XAI](/Guides/Console/Managed-Nodes/xai.md) |Y |[Y](/Get-Started/Console/commission-based)| | [XProtocol](/Guides/Console/Managed-Nodes/xprotocol.md) |Y | | --- ### Subscription service > Run blockchain Nodes with NodeOps Console subscription service. Deploy no-code Nodes, earn 100% rewards, and manage subscriptions on the DePIN platform. URL: https://docs.nodeops.network/Get-Started/Console/subscription 🌟 Status: Live > **Tip: TL;DR** Log in to run subscription-based Nodes. ## Introduction This page guides you through the basics of [NodeOps Console's](/Guides/Console/README.md) Node-as-a-Service subscription. NodeOp's easy-to-use NaaS enables Web3 Protocols and Blockchains to achieve their Node distribution needs by incentivizing you, the Node runners. NodeOps Console is so simple that anyone can run a Node and earn. No code needed; create a subscription and we do all the hard work for you. ## Prerequisites - EVM-compatible wallet - Sufficient funds or promo code - [Specific Protocols](/Guides/Console/README.md) may have additional requirements such as a Node license ## Sign up ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol Navigate to Node Deployment on the left side menu and select your chosen Protocol. ## Deploy Nodes ### Step 3: Choose your deployment type There are 3 deployment options, for inexperienced Node Runners, we recommend using the default, **Auto-assign** mode, alternatively, use the tabs to learn about the 3 deployment options: Auto-assign is the default and the most straightforward way to deploy Nodes in the NodeOps Network. With Auto-assign, NodeOps selects the best available Provider for your deployment. **Show me how to deploy in **Auto-assign** mode.** Node Runners can set their preferred Providers and machines for all their deployments. You can do this using the Advanced Setting option under their Profile. Watch how to deploy in **Profile Preference** mode. Node Runners can also choose a specific Provider machine for a particular Node deployment and further customize the Node using the Custom option. Watch how to deploy in **Custom** mode. ### Step 4: Pay for subscription Choose your payment method: Follow the [payment guide](../Pay-for-Services/Readme.mdx#step-2-pay-for-a-subscription-or-service) to pay with fiat, stables, or tokens. Follow the [top up guide](../Pay-for-Services/Readme.mdx#step-1-optional-top-up-your-credits) to convert $NODE into credits or to top up your credits with fiat, stables, or tokens. If you have a Promo to redeem, you can use this for partial or total payment. You're now ready to [choose which Protocol's Node you wish to run](/Guides/Console/README.md). Or stay here and learn about managing your Nodes and subscriptions. ## Monitor Nodes Once your Nodes are deployed, you can monitor them from **My Nodes**. Clicking on a Node pulls up a page with its details. ### Inactive Node? If a Node is inactive: - Restart it on the same machine - Or, reschedule it to run on a different machine using the **Reschedule** button ### Machine details As a Node Runner, you can navigate to the machine of the Provider on which your Node is deployed by clicking on the machine name. Machine details shows the technical specifications of the machine along with the number of Nodes (workloads) currently running on that machine. ## Renew subscription Use the **My Plans** feature to look up your Node subscriptions and renew these. ## Gotchas If you login with your email, this becomes your identifier and you can later connect your wallet. Should you login with your wallet and later with your email, you just created a second Console account. ## What next? - Choose from our extensive ecosystem of [supported Protocols](/Guides/Console/README.md) and become a Node Runner today. - Running a Node is so simple that you can do it from a mobile, why not have a go? **Show me** --- ### Release liquidity > Release NFT liquidity using the NodeOps LNT Vault. Deposit Node licenses, access liquid tokens, and unlock DeFi opportunities on the DePIN platform. URL: https://docs.nodeops.network/Get-Started/DeFi-Services/liquidity 🌟 Status: Live > **Note: TL;DR** Connect to [Console.NodeOps.Network](https://console.nodeops.network/lnt_vault) to release NFT liquidity. ## Deposit your NFT Node license to release liquidity Use the video or walkthrough to understand how to release liquidity from NFT assets with LNT Vault. **Show me video** ### Prerequisites - EVM-compatible wallet containing: - Asset 1: Vault-supported Protocol's NFT - Asset 2: (Optional, according to Vault rules) Protocol's native token > This tutorial covers the Aethir Vault which requires 2 assets to back the liquidity position: the NFT and $ATH. **Show me supported Protocols** - Aethir > The NFT may be available on a reseller marketplace such as [Opensea](https://opensea.io/collection/aethir-checker-license). ### Step 1: Deposit your NFT into the LNT Vault 1. Logged into the [NodeOps Console](https://console.nodeops.network/lnt_vault), click **LNT Vault** on the left hand menu. **Show me ** 2. Click the card for the Protocol your NFT relates to. This takes you to the correct Vault. **Show me ** This tutorial follows the Aethir Protocol's flow. 3. Click **Deposit** and select the NFT to drop into the Vault by its assigned Id. **Show me ** This tutorial follows the Aethir Protocol's flow. ### Step 2: Access the liquid token 1. Click **Withdraw**. **Show me ** This tutorial follows the Aethir Protocol's flow. 2. Select how many licenses you hold in the Vault to back your liquidity position, and click **Withdraw**. **Show me ** This tutorial follows the Aethir Protocol's flow. 3. (Optional by Protocol): Click **Add liquidity** and topup with the native token to back the position. **Show me ** This tutorial follows the Aethir Protocol's flow. Congratulations. You have access to your liquid token/s. ## What next? - Consider holding your VT till maturity to redeem T at 1:1 ratio - Consider trading the VT for liquidity - Consider providing VT:T liquidity to earn optimal swap rates - Consider investigating the arbitrage opportunities to profit from VT:T's converging price - Learn about the full set of [products and services](/Core-Services#product-and-services) offered across the NodeOps ecosystem --- ### Stake $NODE on NodeOps > Stake $NODE and supported tokens on NodeOps Portal to earn rewards. Connect your wallet and start staking on the decentralized DePIN network today. URL: https://docs.nodeops.network/Get-Started/DeFi-Services/stake 🌟 Status: Live > **Note: TL;DR** Connect your wallet to [Portal.NodeOps.Network](https://portal.nodeops.network/) to stake your tokens. Earn \$NODE by staking [\$NODE](#stake-node-with-nodeops-portal). Earn \$NODE by staking [supported tokens](#stake-supported-tokens-with-nodeops-portal). ## Stake $NODE with NodeOps Portal Use the video or walkthrough to understand how to stake \$NODE to earn \$NODE yield. **Show me video** For a real-time, guided walkthrough, checkout the [YouTube of **How to stake \$NODE**](https://www.youtube.com/watch?v=8ozK86yBWVw). ### Prerequisites - EVM-compatible wallet containing \$NODE - Gas funds ### Step 1: Lock your \$NODE 1. Logged into [NodeOps Portal](https://portal.nodeops.network), click **Stake** on the left hand menu. 2. Enter the amount of \$NODE to stake. 3. Select your lockup period. > The longer you stake, the better the rewards. 4. Click **Approve NODE**, review the transaction details, and confirm in your wallet. 5. Click **Stake**, review the transaction details, and confirm in your wallet. ### Step 2: (Optional) verify the transfer Click **View on explorer** to examine the onchain record of the transaction. ## Stake supported tokens with NodeOps Portal **Show me supported tokens** - **$ATH** Mainnet > 100 K gNode pool | ends 4th October, 2025 - **$POL** on Ethereum Mainnet > 2 mil gNODE pool | ends 28th July, 2026 NodeOps is working hard to make our vision a reality: - $HYPE Mainnet - $ETH EigenLayer Mainnet - $BEAM Mainnet - **$HYPE** Testnet This guide walks you through staking supported tokens. Use the video or walkthrough to understand how to stake to earn yield and gNODE rewards. > Testnet $HYPE is used in this example, the flow is identical for other tokens. **Show me video** ### Prerequisites - EVM-compatible wallet containing the supported tokens ### Step 1: Connect with the Staking apps > **Tip: Connect your wallet on the [HyperLiquid Testnet explorer](https://app.hyperliquid-testnet.xyz/explorer) to view your Testnet $HYPE holdings.** Using the wallet containing your tokens: 1. Connect to the [HyperLiquid staking app](https://app.hyperliquid-testnet.xyz) 2. Click on **Spot←→Staking Balance Transfer** and assign the value of tokens you will stake. **Show me** 3. Connect the same wallet at [Portal.NodeOps.Network](https://portal.nodeops.network). ### Step 2: Stake 1. Click **Stake** on the right hand side of the dashboard. 2. Enter the **Amount** of tokens you wish to stake, or click **Max**. **Show me** 3. Review the details and confirm your selection by clicking **Stake**. 4. Review and confirm the transaction request in your wallet. Congratulations, you should received a **Stake successful** alert and may now close the form. ### Step 3: (Optional) Verify your stake Click the **My Stakes** tab to review your delegated stakes. ## What next? - To stake $ATH [use the Guide](/Guides/Portal/stake-aethir) to follow the unique flow - Follow the guide to learn how to use the [Portal](/Guides/Portal) app to manage your tokens - Browse the [staking with NodeOps FAQ](/Learn/FAQ/portal.md) --- ### Enable Telegram bot > Enable the NodeOps Telegram bot to manage your DePIN Nodes, top up credits, and access NodeOps Network services directly from Telegram. URL: https://docs.nodeops.network/Get-Started/enable-telegram-bot 🌟 Status: Live ## Get started with NodeOps Telegram bot #### Prerequisites - [Console](https://console.nodeops.network/profile) or [Marketplace](https://cloud.nodeops.network/profile) account - Personal Telegram app is active #### Setup a connection to the bot To use this bot, you need to connect your Telegram account: 1. From your: [NodeOps Console profile](https://console.nodeops.network/profile), or your [NodeOps Marketplace profile](https://cloud.nodeops.network/profile), click **Connect Telegram**. **Show me** 2. Copy your OTP, and click the **exit** icon to move to the Telegram app. **Show me** 3. Enter the OTP code in the TG bot chat. > If you return to your profile dashboard, you will see "Your telegram is connected". > > **Show me** > > In Telegram, you will see: "βœ… Telegram account connected successfully!"" You can now use all the bot's features. Congratulations, you can now manage your NodeOps account and services directly from Telegram. ## What next? - Learn what you can do with the [Telegram bot](/Guides/tg-bot) --- ### Top up with $NODE > Convert $NODE tokens to credits on NodeOps Console and Marketplace. Step-by-step guide to top up your account and pay for DePIN services with $NODE. URL: https://docs.nodeops.network/Get-Started/Pay-for-Services/node-to-credits ## Prerequisites - EVM-compatible wallet holding Wave 1 airdropped \$NODE ## Pay for credits with \$NODE This guide walks you through paying for credits with \$NODE in NodeOps Console and Marketplace. ### Step 1: Ensure \$NODE is available in your wallet You may view your \$NODE from the [Portal app](/Guides/Portal) or directly in your EVM-compatible wallet. **Show me how to add the \$NODE token to my wallet** Wallets differ slightly in their flows, this demonstration uses MetaMask. 1. Log in to your wallet. 2. From the **Tokens** tab, select the hamburger menu and click **Import tokens**. 3. Click **Custom token**, and select the chain your \$NODE is on. 4. Copy the \$NODE token address and enter it into the **Token contract address** field: > This demo shows Arbitrum One's \$NODE. 5. If the token symbol comes up as NODE, you're good to go, click **Next**. Congratulations, your \$NODE holdings are now visible in your wallet. ### Step 2: Sign up or log in 1. From the [Console](https://console.nodeops.network) or [Marketplace](https://cloud.nodeops.network/) Apps, sign up or log in using the **Log In** button. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 3: Convert \$NODE to credits **Watch a video walkthrough** a. Select \$NODE as the payment method. b. Enter the USD amount of \$NODE that you wish to convert to credits. c. Click **Checkout**. d. Confirm the transaction in your wallet. ## What next? - Learn more about [\$NODE](/Tokenomics/node.md) - If you encounter issues, ensure the contract address is correct by verifying it on a blockchain explorer like [Etherscan](https://etherscan.io/) - Avoid scams by double-checking token details on trusted platforms like [CoinGecko](https://www.coingecko.com/en/coins/node-2) or [CoinMarketCap](https://coinmarketcap.com/currencies/nodeops/). --- ### Pay for services > Pay for NodeOps services with $NODE, fiat, stables, or tokens. Top up credits and manage payments across Console and Cloud Marketplace on the DePIN network. URL: https://docs.nodeops.network/Get-Started/Pay-for-Services > **Tip: TL;DR** You may top up credits or pay the required amount using the following apps: - [Telegram bot](/Guides/tg-bot.md) - [Console](https://console.nodeops.network/) - [Marketplace](https://cloud.nodeops.network/) Pay with \$NODE or via our payment partner which accepts fiat card payments and supported stables and tokens. **Show me accepted stables and tokens** You can convert $NODE to credits, convert other supported stables or tokens to credits, or pay with supported cards or tokens: [Source](https://copperx.io/payment-methods). ## Prerequisites - Funds in either an: - EVM-compatible wallet - Stables/Tokens/$NODE - Credit or debit card ## Overview Follow this guide to understand how to pay for subscriptions and services provided within the NodeOps Console and NodeOps Marketplace apps. You can either pay the exact subscription amount each time, or you can add credits to your NodeOps account and use these as needed. ## Payment within NodeOps ### Step 1: (Optional) top up your credits To save you from paying multiple sets of transactions fees, you may top up your funds and hold them in your account. If you wish to skip this, jump to [Step 2](#step-2-pay-for-a-subscription-or-service). > **Warning: Credits are bound** When you add credits to your dashboard, they are bound there until you use them. There's no withdrawal mechanism. Please load the amount that aligns with your intended usage. 1. Logged in to [Console](https://console.nodeops.network/), or [Marketplace](https://cloud.nodeops.network/), click **Add Credits** in the bottom left of the dashboard. **Show me** 2. Enter the USD value you wish to credit your account with, and click **Checkout**. 3. Choose your payment vehicle: Fiat, tokens, or stables **Watch a video walkthrough** a. Select **Copperx** as the payment method. b. Enter the USD value you wish to credit your account with, and click **Checkout**. c. Select from: - Wallet/Scan QR Code: For stable/token payments - Card: For fiat payments **Show me** > **Tip: QR code** This option provides an address that you may copy directly into the "To" address in your EVM-compatible browser wallet, or you can use a mobile wallet to scan the QR to pickup that address. **Watch a video walkthrough** a. Select \$NODE as the payment method. b. Enter the USD amount of \$NODE that you wish to convert to credits. c. Click **Checkout**. d. Confirm the transaction in your wallet. ### Step 2: Pay for a subscription or service Choose your payment vehicle: You may pay for credits, subscriptions, and services via our payment partner using: - Debit or credit card - Stables and tokens on supported chains **Show me stable and token payment options** **Show me accepted stables and tokens** You can convert $NODE to credits, convert other supported stables or tokens to credits, or pay with supported cards or tokens: [Source](https://copperx.io/payment-methods). 1. Logged in to [Console](https://console.nodeops.network/), or [Marketplace](https://cloud.nodeops.network/), subscribe for a product or service and follow the payment flow. **Show me** 2. Select **Copperx** and click **Checkout** **Show me** Choose to pay with stables, tokens or fiat, use the tabs below: 1. Select the wallet containing your funds. **Show me** 2. Continue with payment. 2.1 Choose either: - Wallet - Scan QR Code > This option provides an address that you may copy directly into the "To" address in your EVM-compatible browser wallet, or you can use a mobile wallet to scan the QR to pickup that address. **Show me** 2.2 Select the network your stables or tokens reside on. 2.3 Enter the amount you wish to pay, and confirm the transaction. 2.1 Select **Card**. **Show me** 2.2 Enter your card details for our payment partner to process. **Show me** 3. Complete the payment. 1. Ensure your account is [in credit](#step-1-optional-top-up-your-credits). 2. Select your product or service. 3. Complete the payment using your credits. If you have a Promo to redeem, you can use this for partial or total payment. Congratulations, you are ready to use your favorite NodeOps services. ## What next? - Learn about NodeOps' [Core Services](/Core-Services/Readme.md) - Learn to [manage your Marketplace account](/Guides/Marketplace/marketplace-account.md) --- --- ## Guides ### gNODE Points β€” Community Rewards > Learn about gNODE, the non-transferable reward points on NodeOps Network. Discover how to earn gNODE and redeem it for $NODE tokens. URL: https://docs.nodeops.network/Guides/Community-Incentives/points > **Tip: TL;DR** NodeOps Network's Protocol awards gNODE to participants gNODE is the reward layer used within the NodeOps Network to distribute incentives. gNODE Points represent earned rewards that can be redeemed for [$NODE](/Tokenomics/node). gNODE is not transferable nor tradable. gNODE to NODE conversion is constrained by the following redemption cycle: - 100%: 150 days - 50%: 90 days - 25%: 30 days - 10%: 15 days ## Earn gNODE gNODE is used to reward engagement with NodeOps ecosystem, for example: - Become a [Template developer](/Guides/Marketplace/Configure-Compute/upload-template) and earn rewards when users run workloads via your code - [Provide Compute](/Get-Started/Cloud-Compute/Provide-Compute/README.md) - Earn higher rewards when you assign your machine/s workloads - [Verify the Protocol](/Get-Started/Cloud-Compute/node-orchestrator.md) - [Top up with credits](/Get-Started/Pay-for-Services/Readme.mdx): Burn \$10 or more \$NODE to earn Credits and unlock multipliers that boost your future rewards - [Deploy Nodes](/Get-Started/Console/README.md): Use the [NodeOps Console](https://console.nodeops.network/) to deploy Nodes or workloads - [Farm Compute](/Guides/Marketplace/farm) / [rent a machine](/Get-Started/Cloud-Compute/rent-compute.md): Lease Compute from the Marketplace - [Mint a UNO NFT](/Guides/Community-Incentives/uno#mint-uno): Mint a UNO NFT to gain ecosystem perks, future governance access, and airdrop eligibility - [Stake](/Get-Started/DeFi-Services/stake.md) \$NODE or supported tokens with [NodeOps Portal](https://portal.nodeops.network/) - [Launch UNO-enabled CU](/Guides/Community-Incentives/uno#uno-available-cu) ## What next? - Learn more about the NodeOps Ecosystem [core services](/Core-Services) - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) - Convert [gNODE to $NODE](/Guides/Portal#redeem-gnode-with-nodeops-portal) - Learn about [$NODE](/Tokenomics/node) - Learn about [previous reward mechanisms](/Learn/FAQ/community-rewards.md#can-i-earn-nps-and-stnode) used in Testnet --- ### Community incentives > Explore NodeOps Network community incentives including gNODE rewards and UNO NFTs. Learn how to earn and redeem rewards in the DePIN ecosystem. URL: https://docs.nodeops.network/Guides/Community-Incentives NodeOps Network strives foster a balanced circular economy that rewards contributors and sustains long-term growth. We do this through our [tokenomics](/Tokenomics/node.md) and incentive programs. The different reward mechanisms are listed, follow their links to learn more. - [UNO](./uno.mdx): A tokenized security NFT investment vehicle - [gNODE](./points.md): A non-tradable and non-transferrable reward that can be exchanged for [$NODE](/Tokenomics/node.md) > **Tip: $NODE Tokenomics are underway** With [Governance](/Tokenomics/governance) underway, the proposed [$NODE tokenomics](/Tokenomics/node) can now be initiated to achieve our vision of a robust NodeOps Ecosystem economy. ## What next? - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) and earn gNODE when you subscribe to run template workloads - Get started with [Console](/Get-Started/Console/README.md) and earn gNODE when you subscribe to run Blockchain or Protocol Nodes - Get started with the [Cloud Marketplace](/Guides/Marketplace/README.md) and earn gNODE as you leverage products and services - Get started with [Stakedrop](/Get-Started/DeFi-Services/stake.md) and earn gNODE while you stake - Convert [gNODE to $NODE](/Guides/Portal#redeem-gnode-with-nodeops-portal) --- ### UNO Rewards Program > Mint and manage UNO NFTs on NodeOps Network. Learn how UNO tokenized security NFTs unlock Compute units and Orchestrator Node rewards. URL: https://docs.nodeops.network/Guides/Community-Incentives/uno > **Tip: TL;DR** - Holding UNO offers some of the same properties as holding [$NODE](/Tokenomics/node.md) - UNO holders are eligible to run [Orchestrator Nodes](/Learn/Ecosystem/nodeorchestrator) - UNO holders are [eligible to vote](/Tokenomics/governance#eligible-participants) as part of the DAO - Purchase UNO from [portal.nodeops.network](http://portal.nodeops.network) and mint on Ethereum, Arbitrum, or Base ### Overview UNO is a Flagship NFT collection, released for public sale in March 2025. UNO confers the following utility to holders: - Revenue share: Quarterly share from NodeOps Network profits - Allowlists: Ecosystem allowlists and early access to [Console](/Guides/Console/README.md) projects - Platform access and discounts: Save on Node Deployments and migrations and get beta access to new features. > **Note: UNO rewards have dropped** Each UNO NFT grants access to one 2CU machine to allow you to [farm its workload rewards](/Guides/Marketplace/farm.md) in [gNODE](/Guides/Community-Incentives/points.md). - Favourable unlocks: Earn the rights to early \$NODE unlocks and more favourable vesting schedules by being an UNO holder and active on the ecosystem - Governance: Influence network decisions along with \$NODE holders - Auto-bonding: UNO holders that become Compute providers will have \$NODE bonded on their behalf > **Important: UNO properties** - Non-transferrable for 1 year from mint ## Mint UNO ### Prerequisites - EVM-compatible wallet containing funds and gas for your preferred chain: - Ethereum - Base - Arbitrum 1. Connect wallet at [portal.nodeops.network](http://portal.nodeops.network), review the transaction details, and confirm in your wallet. 2. Select the chain you wish to mint on. 3. Read and accept the terms and conditions. 4. Click **Mint UNO**. 5. Pay or apply platform credits. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ## UNO-available CU #### Claim your 2CUs per UNO 1. Connect your wallet with UNO NFT/s to the [Cloud Marketplace](https://cloud.nodeops.network/). 2. Click **Farm Compute** > You’ll see: "You're eligible for a 2CU machine". 3. Click **Continue**, then **Deploy**. Repeat these steps for each UNO NFT you hold. Remember to renew your machines. **Show me** ## Earn with Orchestrator Nodes You may [delegate your UNO NFT](/Get-Started/Cloud-Compute/node-orchestrator.md) to run an [Orchestrator Node](/Learn/Ecosystem/nodeorchestrator) and earn [gNODE](/Guides/Community-Incentives/points.md). The gNODE rewards you earn are based on the Orchestrator Node's responsiveness, which is tracked across 24 epochs per day. If the Node actively participates and responds during these epochs, the license holder receives rewards β€” up to a set amount per day per license. The more consistently the operator performs, the more rewards are distributed. > Learn about the [current campaign for Node Orchestrator rewards](/Learn/FAQ/UNO#current-uno-node-operator-campaign). ## What next? - Learn about the [current UNO Operator reward season](/Learn/FAQ/UNO#current-uno-node-operator-campaign) - Learn more about the [$NODE ecosystem](../../Learn/README.md) - Learn more about the NodeOps Ecosystem [core services](/Core-Services) - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) - Convert [gNODE to $NODE](/Guides/Portal#redeem-gnode-with-nodeops-portal) - Learn about [$NODE](/Tokenomics/node) - Learn more about the [UNO release](https://nodeops.network/blog/introducing-uno-your-gateway-to-the-nodeops-network) from our blog --- ### Console account > Manage your NodeOps Console account β€” update your profile, register an email, delegate or undelegate NFTs, and deploy blockchain Nodes. URL: https://docs.nodeops.network/Guides/Console/console-account > **Note: From your account on the NodeOps Network Cloud Compute Marketplace, you may:** - Create an account - Log into an account - Log out of an account From the NodeOps Console, you may: - Add credits - Earn commission - [Delegate NFTs](/Get-Started/Console/commission-based) - [Undelegate NFTs](#undelegate-your-nft) - Deploy Nodes - Get help - Manage profile - Add/edit [username](#username) - Add/edit connected wallets - Register an [email](#register-your-email) - Manage **My plans** - [Pay for services](/Get-Started/Pay-for-Services#payment-within-nodeops) - Manage my deployed Nodes - Review Nodes - Subscribe to [run a managed Node](/Guides/Console) - [Release liquidity](/Get-Started/DeFi-Services/liquidity.md) from an NFT license - Share the love - Take part in Node sale with NodePad ## Manage profile ### Username 1. Logged into the [Console](https://console.nodeops.network/profile), navigate to the **Profile** to add or edit your username. ### Register your email 1. Logged into the [Console](https://console.nodeops.network/profile), navigate to the **Profile** to add and register your email. 2. Either: - **Register with Email**, or - **Continue with Google** for social sign on **Show me** ## Undelegate your NFT 1. Logged into the [NodeOps Console](https://console.nodeops.network/node-delegation), click **Delegation** on the left hand menu and enter the **My Delegations** tab. > Ensure you connect a wallet that supports the chain for your NFT license. **Show me ** 2. Click **Undelegate**. **Show me ** ## What next? - Learn about the full set of [products and services](/Core-Services#product-and-services) offered across the NodeOps ecosystem --- ### Manage liquidity > Extract liquidity from NFT licenses using the NodeOps Console LNT Vault. Deposit NFTs, track rewards, view buyback rates, and withdraw. URL: https://docs.nodeops.network/Guides/Console/manage-liquidity 🌟 Status: Live > **Note: NodeOps Cloud Console's [LNT Vault](https://console.nodeops.network/lnt_vault), lets you:** - [Deposit supported NFTs](/Get-Started/DeFi-Services/liquidity) to extract liquidity - [Track and manage your rewards](#track--manage) - [View buyback rates](#track--manage) - [Withdraw your NFT](#withdraw-your-nft) ## Track & Manage Displayed in the UI: - Partner Project details - Real-time rewards. - VT buyback rates - YT balance ## Withdraw your NFT To withdraw your NFT, simply return and burn the required VT. > Protocols may apply a minimum Vault lock-in period. ## FAQ ### Where do the NFTs go? Deposited NFTs are used to spin up Nodes hosted by NodeOps' [DePIN Cloud](/Core-Services#1-nodeops-cloud). ## What next? - Learn about the full set of [products and services](/Core-Services#product-and-services) offered across the NodeOps ecosystem. --- ### Aethir > How to Run Your Aethir Checker Node | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/aethir ## Overview [Aethir](https://aethir.com/) is a Cloud computing infrastructure platform that revolutionizes the ownership, distribution, and utilization paradigms of enterprise-grade graphical processing units (GPUs). By moving away from traditional centralized models, Aethir has deployed a scalable and competitive framework for sharing distributed computational resources, catering to enterprise applications and clientele across various industries and regions. ## Aethir Checker Nodes An [Aethir Checker Node](https://docs.aethir.com/checker-nodes-explained) is a fundamental component in the Aethir Network's backend infrastructure, along with Containers and Indexers. All three are intricately linked. ## Prerequisites - Checker Node Key License - EVM-compatible wallet - $ETH on Arbitrium One for gas fees to perform delegation transaction - Sufficient funds or credits for your Node subscription ## Run your Checker Nodes via NodeOps Console This guide supports you in deploying Checker Nodes. Use the video or walkthrough to understand how to set up your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node 1. Navigate to **Node Deployment** on the left side menu and select **Aethir** & Node type As **Checker**. 2. Connect your wallet holding the Checker Nodes and click on **Fetch NFT** ### Step 3: Set up your Node subscription 3. Pay the subscription fees. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). 4. Your order is now been executed. Once you are directed to your NodeFolio, you will see **Action Required**. ### Step 4: Delegate your licenses 1. Delegate your Licenses to the dedicated Burner Wallet / Address. 2. Copy The Public Key From the Above Step to Proceed to Delegate on your Aethir Dashboard. 3. Headover to [app.aethir.com/licenses](https://app.aethir.com/licenses), Click on **Delegate** and past the respective address. 4. Submit the Delegate Transaction. ### Step 5: (Optional) Verify your deployment Within 10-15 seconds, your Nodes should be up and running which you can check on both NodeOps Console & the Aethir Dashboard. ## FAQ - What's the cost of running a Checker Node? | Duration (Months) | Discount | $ cost per license (per m) total| |-------------------|----------|---------------------------------| | 1 | NA | (6) 6.00 | | 3 | 5% | (5.70) 17.10 | | 6 | 10% | (5.40) 32.40 | | 12 | 20% | (4.80) 57.60 | | 24 | 25% | (4.50) 108.00 | | 36 | 30% | (4.20) 151.20 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: - What Node running status do I need to be aware of? * Checking: Running checking tasks * Ready: Ready to receive checking tasks * Offline: Not connected * Banned: Banned due to malicious intents - Does NodeOps take some of my AETHIR rewards (that is, vATH or ATH tokens)? > No, NodeOps does not take any of your rewards. You only need to pay a fixed fee for Node operation or a Node deployment subscription. All rewards from your Aethir Node operations are entirely managed by you. #### Node Operation - How do I switch from Testnet to Mainnet? > All testnet operations were on Arbitrum Sepolia. For Mainnet, you must redelegate your license on the Aethir Owner portal. Ensure you have some ETH on Arbitrum One to cover gas fees. We will also provide tutorials to facilitate a seamless transition from Testnet to Mainnet. - I participated in the testnet using NodeOps. Does this bring any advantage? > Yes, testnet participants using NodeOps will receive a free 1-month extension of their subscription + NODE Points Already dropped to users. - Can I connect multiple wallets to have a unified way to manage my Nodes? > Yes, you can. Sign in with the same email, connect all your wallets, and subscribe using the same email. You'll have a unified Dashboard (NodeFolio) to manage all your Nodes. - If I purchase additional Checker Nodes, do I need to subscribe again? > If you have purchased additional checker Node licenses via the same wallet, you do not need to purchase additional subscriptions, if it is a different wallet, you would have to subscribe through the new wallet. ## What Next? - Reach out on Discord if you need further assistance - [Learn more about the partnership and Checker Nodes](https://x.com/AethirCloud/status/1783810892838088748) - [NodeOps: Aethir Partnership](https://x.com/NodeOps_App/status/1783862954594550105) - Aethir docs: [Checker Nodes Explained](https://docs.aethir.com/checker-nodes-explained) - [Video On How To Run](https://youtu.be/QWBk11Fc03I) --- ### Avail > NodeOps provides containerized infrastructure specifically curated for developers and Node operators designed to simplify the development process and operations for Web3 Protocols. URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/avail [Avail](https://www.availproject.org/) is a Web3 infrastructure layer that allows modular execution layers to scale and interoperate in a trust minimized way. This guide walks you through deploying Avail Validator Nodes Powered by NodeOps. ## Prerequisites - EVM-compatible wallet - Sufficient funds or credits for your Node subscription ## Deploy Avail Validator Nodes with NodeOps Console Checker Nodes ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node Navigate to **Node Deployment** on the left side menu and select **Avail**. ### Step 3: Set up your Node subscription Pay using your favorite stables on your preferred chains. Once the Payment is successful, you will automatically be redirected to the Dashboard. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 4: Verify your deployment 1. Wait for a couple of minutes for the Deployment status to change from Pending to Running. 2. Check your logs. Once the status is Running, the Logs will automatically display the steps, to validate if your Node is working fine, you should see logs something like this ### Step 5: Verify deployment at Avail Telemetry Check [telemetry.avail.tools](https://telemetry.avail.tools/) and search for your namespace showcasing the sync status of the Node. The synchronization approximately takes 18-24h_ ### Step 6: Register and create stash & a controller account > **Tip: Learn more about this from the [Avail docs](https://docs.availproject.org/operate/validator/staking/).** To register your Node as an active validator, bond your tokens to the respective Node: 1. Navigate to the Goldberg network explorer at [goldberg.avail.tools](https://goldberg.avail.tools/) 2. Create a `stash` and a `controller` account. The `stash` account should ideally be a cold wallet, while the `controller` can be a hot wallet. > - The controller key is responsible for managing staking activities and executing transactions, including the payment of transaction fees. > - The stash key primarily safeguards your funds and should ideally be stored in a cold wallet or kept offline. It is not recommended to use the stash key for routine account activities like submitting extrinsics. 3. Create a Controller Account. > **Warning: REMEMBER TO STORE YOUR MNEMONICS/KEYS SAFELY** ### Step 7: Bond your funds Follow the Avail docs to [bond your funds](https://docs.availproject.org/operate/validator/staking/#bond-your-funds) Go To Goldberg Explorer -> Network -> Staking Click on **Stash** to proceed with Bonding. ### Step 8: Add a session key 1. Head over to [NodeOps Console](https://console.nodeops.network/), go to your Node and fetch the session key 2. Copy and paste the session key in the session key section. ### Step 9: Register as a validator 1. Register as a validator by Clicking on **Validate** on the **Staking** tab. 2. Set your validator commission, enter your password & Start the Validation ### Step 10: (Optional) Verify & monitor your validator on the explorer To verify if your validator is running properly, verify the validator status, and monitor the dashboard logs in the Console. ## FAQ - What's the subscription cost? | Duration (Months) | 1–10 Keys $ (per m) cost | |-------------------|---------------------------| | 1 | (7.50) 7.50 | | 3 | (7.13) 21.38 | | 6 | (6.75) 40.50 | | 12 | (6.00) 72.00 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance Learn more about: - [Validator staking with Avail](https://docs.availproject.org/operate/validator/staking/#verify-validator-status). - The various types of [Avail Nodes](https://docs.availproject.org/operate/node-types/) - [Getting Avail tokens from their faucet](https://docs.availproject.org/about/faucet/) --- ### Beam > How to Run Beam Nodes Using NodeOps Console URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/beam [Beam Network](https://onbeam.com) is a permissionless, proof-of-stake Layer 1 blockchain that anyone can help secure and validate. Beam Nodes form the backbone of this decentralized network infrastructure, processing transactions and adding new blocks to the Beam Network. As a [Beam token holder](https://nodes.onbeam.com/) you can stake BEAM and help validate the network. ## Prerequisites - EVM-compatible wallet containing: - Minimum stake of 20,000 BEAM > BEAM is a publicly listed token - NFT license Beam:Node Token (ERC-721) - Sufficient funds or credits for your Node subscription ## Run your Beam Validator Nodes with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node 1. Navigate to **Node Deployment** on the left side menu and select **Beam**. 2. Update the **Quantity** to determine how many Nodes to deploy. > **Important: Maximum limit** Maximum Stake Limits: Each Beam Node can have up to 200 million BEAM and 1,000 Node Tokens staked to it. 3. Select the **delegation duration** that suits your requirements. 4. Click **Purchase and Deploy** to confirm your selection and complete the transaction. 5. Once deployed, go to the [NodeFolio](https://console.nodeops.network/dashboard) page. ### Step 3: Stake your BEAM tokens 1. Click on your Beam subscription. 2. Copy your unique Node configuration data: - Node ID - BLS Public Key - BLS Proof of Possession - P-Chain Address **Show me** ### Step 4: Register Your Validator with Beam 1. Connect your wallet at the [Beam delegator page](https://delegation.onbeam.com/validators). 2. Click **Add New** to start the validator registration. 3. Paste the details copied from Step 3 above. 4. Set the **Commission Rate** and **Minimum Stake Duration**. **Show me** > **Tip: License ** Ensure you are using the wallet that holds your NFT license to be automatically recognized by Beam. 5. Enter the **amount of BEAM tokens** you want to stake. 2. Confirm and complete the registration process. ### Step 5: (Optional) Verify your deployment Within 30-60 seconds, your Nodes should be up and running which you can check on both NodeOps Console & the Beam Dashboard. ## FAQ - What's the cost of running a Beam Node subscription? | Duration (Months) | Discounts (%) | Price up to 1000 licenses (per m) $ | |-------------------|----------------|--------------------------------------| | 1 | NA | (40) 40 | | 3 | 5% | (38) 114 | | 6 | 10% | (36) 216 | | 12 | 20% | (32) 384 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Learn more from the [Beam documentation](https://docs.onbeam.com) > Dedicated [Beam Node troubleshooting page](https://docs.onbeam.com/nodes/maintenance/troubleshooting) - Reach out on Discord if you need further assistance --- ### Captain & Co. > How to Run Captain & Company Nodes Using NodeOps Console URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/capnco [Captain & Company](https://capnco.gg/) is a player econonomy built by KAP Games. ## Prerequisites - EVM-compatible wallet - Sufficient funds or credits for your Node subscription - Minimum 0.01 ETH is required for your operator wallet balance - Captain & Co. NFT License > **Tip: You can still purchase licenses** Purchase [direct from the KAP Foundation](https://kap.foundation/nodes). ## Run your Captain & Company Nodes with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console > **Important: Remember to connect with the wallet that holds your NFT license.** 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Set up Node 1. Navigate to **Node Deployment** on the left side menu and select **Captain & Company**. 2. Click **Fetch NFT** to link your NFT license to your Node. **Show me** 3. Update the **Quantity** and **Duration** to determine how many Nodes to deploy and for how long. 4. Review the details and confirm your selection by clicking **Purchase & Deploy**. ### Step 3: Set up your Node subscription Once the Payment is successful, you will automatically be redirected to the Dashboard. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 4: Delegate your licence to your deployment 1. From your [NodeFolio](https://console.nodeops.network/dashboard), click on your Captain & Co. Node that needs a license applied. **Show me** 2. Click **Fetch NFT** and, if you have multiple, select how many NFTs to delegate to this Node. 3. Click **Click to Delegate**. Congratulations, your Captain & Company Node/s are set up. ## FAQ - What's the pricing for deployment? | Duration (Months) | Discounts (%) | Price per node $ (no license cap) | Total $ | |-------------------|----------------|------------------------------------|---------| | 1 | NA | (3.00) 3.00 | 3.00 | | 3 | 5% | (2.85) 8.55 | 8.55 | | 6 | 10% | (2.70) 16.20 | 16.20 | | 12 | 20% | (2.40) 28.80 | 28.80 | | 24 | 25% | (2.25) 54.00 | 54.00 | | 36 | 30% | (2.10) 75.60 | 75.60 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: Delegate your licences to the NodeOps’ Pool and earn a 5% $CNC commission. ## What next? - Once you have set up your Node through NodeOps Console: you can create your own pool on the [KAP Foundation dashboard](https://kap.foundation/nodes) and set whatever commission you deem fair. - Learn about delegating to the [NodeOps official Node](https://nodeops.network/blog/how-to-earn-as-a-node-operator-for-captain-and-company) - Learn more from the [Captain & Company documentation](https://docs.capnco.gg/) - Reach out on Discord if you need further assistance --- ### CARV > How to Run Your CARV Verifier Node | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/carv ## What is CARV Protocol? The [CARV Protocol](https://carv.io/) is a modular data layer that facilitates data exchange and value distribution across gaming, AI, and ∞. It encompasses end-to-end data flow processes, including data verification, identity authentication, storage, processing, model training, and value distribution. The CARV Protocol empowers users by granting them control over their own data, enabling them to share information securely and privately while participating in revenue generated from their data usage. ### Understand CARV verifier Nodes Verifier Nodes are components of CARV's verification layer. Verifier Nodes are lightweight Nodes managed by the community. They play a crucial role in maintaining the Protocol's integrity, thereby enhancing its trustworthiness and security. Currently, these Nodes primarily check TEE attestations onchain, verifying that the results are reliable and that the process maintains the privacy of user data. ## Prerequisites - EVM-compatible wallet - Sufficient funds or credits for your Node subscription - CARV Node NFT > **Tip: Don't have a CARV NFT? [Investigate](https://verifier.carv.io/?code=nodeops) whether they're still available to purchase.** ## Run your CARV verifier Nodes with NodeOps Console ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ## Choose between two subscription models Use the tabs to follow the flow for the model you wish to use: 1. [CARV Premium](carv#carv-premium): This subscription model requires you to pay for your Node operations, allowing you to retain your full rewards. Additionally, you can enable users to delegate to your Node, offering flexibility in setting the commission rate you wish to receive from license holders who delegate to you. 2. [Commision-based model](carv#carv-commission-model): In this model, you do not need to pay for monthly subscriptions. Instead, the cost of your Node operations is covered by a 5% share of your rewards. This means you retain 95% of your reward tokens, while 5% is allocated to NodeOps. ## CARV premium Use the video or guide to understand how to set up your Nodes. ### Step 2: Select your Protocol and Node 1. Navigate to **Node Deployment** on the left side menu and select β€œCARV Premium”. 2. Select "Verifier Node" for the Node type. This option is selected by default. 3. Connect your wallet to the account where you want your commission rewards to be deposited. Then enter the commission you want from users who delegate to your Node. The commission rate can be set between 0-100. 0 means you don't take any commission from delegators. 100 means you take all rewards. 4. Select your subscription duration. The longer your subscription, the lower the monthly cost. After selecting your subscription, click Continue to pay.; > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 3: Set up your Node subscription 1. Make the payment for the subscription using your preferred blockchain. Once the payment is complete, you will be redirected to the NodeFolio. 2. After completing the payment, you will be redirected to Nodefolio. Select the Node you just set up, then click "Delegate" to initiate the delegation process. 3. Connect to the wallet that contains your CARV Verifier Node license. Click on "Fetch NFT" to automatically detect the CARV NFTs in your wallet. 4. Click "Click to Delegate" and sign the transaction. Ensure you have sufficient ETH to cover gas fees, as all operations on the Alphanet are conducted on Arbitrum One. Congratulations! You have successfully set up your CARV Verifier Node and completed the delegation process. Optionally, you can verify the delegation on the [CARV alphanet verifier page](https://d.docs.live.net/812cddea220c08e4/Shared%20files/MMMD/Youtube%20videos/DEPINspirationHUB/NodeOps/CARV%20verifier%20node/alphanet-explorer.carv.io/verifier). ## CARV commission model ## Delegate your NFT Node license to earn Protocol rewards Use the video or walkthrough to understand how to delegate NodeOps to run a CARV Node with your NFT license. No need to set up or [subscribe](/Core-Services#2-nodeops-console) to run a Node. **Show me video** ### Prerequisites - EVM-compatible wallet - CARV Node NFT ### Step 1: Generate a wallet for the Node Operator 1. Logged into the [NodeOps Console](https://console.nodeops.network/node-delegation), click **Commissioned Delegation** on the left hand menu and enter the **My Delegations** tab. > Ensure you connect the wallet containing the NFT license. **Show me ** 2. Click **Delegate** to register which Protocol you will delegate Node running for. **Show me ** 3. Click to increment the Node Operator count, click **Add Operator** and copy the address of the Node Operator wallet that's created. **Show me ** Retain the wallet address for the next step. ### Step 2: Delegate your NFT license 1. Switch to the Arbitrum Protocol's verifier app [Explorer.Carv.io/verifiers](https://explorer.carv.io/verifiers). 2. Click **Delegate My License** and paste the wallet address copied in Step 1. 3. Select how many NFT licenses to delegate, click **Delegate**, and confirm the transaction in your wallet. Congratulations, your Node license is now actively earning the Protocol rewards. ## FAQ - What's the cost for the Premium subscription? | Duration (Months) | 1–10 Keys $ (per month) total | 11–50 Keys $ (per month) | 51–100 Keys $ (per month) | 100+ Keys $ (per month) | 200+ Keys $ (per month) | 500+ Keys $ (per month) | 1000+ Keys $ (per month) | |-------------------|-------------------------|---------------------------|----------------------------|--------------------------|---------------------------|----------------------------|-----------------------------| | 1 | (20) 20 | (25) 25 | (30) 30 | (40) 40 | (50) 50 | (100) 100 | (200) 200 | | 3 | (18) 54 | (22.50) 67.50 | (27) 81 | (36) 108 | (45) 135 | (90) 270 | (180) 540 | | 6 | (16) 96 | (20) 120 | (24) 144 | (32) 192 | (40) 240 | (80) 480 | (160) 960 | | 12 | (14) 168 | (17.50) 210 | (21) 252 | (28) 336 | (35) 420 | (70) 840 | (140) 1680 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance: see the Community Links in the footer - For more detailed information, visit the [CARV Documentation](https://docs.carv.io/carv-protocol/overview/) --- ### Celestia > How to Run Celestia Light Nodes Using NodeOps Console URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/celestia [Celestia](https://celestia.org/) is a modular blockchain powering applications with full-stack customizability. ## Prerequisites - EVM-compatible wallet - Sufficient funds or credits for your Node subscription ## Run your Celestia Nodes with NodeOps Console This guide supports you to deploy Celestia Nodes. Use the video or walkthrough to understand how to set up your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node Navigate to **Node Deployment** on the left side menu and select **Celestia**. ### Step 3: Set up your Node subscription > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). Once the Payment is successful, you will automatically be redirected to the Dashboard. ### Step 4: Verify your deployment Wait for a couple of minutes for the Deployment status to change from Pending to Running. ## FAQ - What's the subscription cost? | Duration (Months) | Discounts (%) | $ (per m) cost | |-------------------|---------------|-------------------| | 1 | NA | (15) 15 | | 3 | 5 | (14.25) 42.75 | | 6 | 10 | (13.50) 81 | | 12 | 20 | (12) 144 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance --- ### DIN > DIN Chipper Node Delegation | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/din [DIN](https://din.lol) is the first modular AI-native data pre-processing layer, revolutionizing data flow and AI agent building with its innovative Protocols and communities. A key component of the DIN network is the [**Chipper Node**](https://docs.din.lol/din-cook-data-for-ai/how-to-join/chipper-node-explained), which playsa vital role in the AI data preprocessing workflow. As licensed Data Validators and Vectorizers, Chipper Nodes handle the validation, classification, cleaning, and augmentation of raw data collected by Data Collectors. Node operators can run these Nodes on their own edge devices, leveraging a lightweight language classification model powered by **fastText** for efficient and accurate multilingual text processing. This processed data is optimized for AI training purposes. ## Prerequisites - EVM-compatible wallet containing: - DIN Chipper Node License: Only available to users who participated in the Chipper Node sale. - Sufficient funds or credits for your Node subscription ## Run your DIN Nodes with NodeOps Console This guide supports you to deploy DIN's Chipper Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Set up your Node 2.1 Navigate to **Node Deployment** on the left side menu and select **DIN**. 2.2 Select the default β€œChipper” Node type. 2.3 Click **Connect Wallet** with your wallet containing the Chipper Node NFT. 2.4 Click **Fetch NFT**. > The system will display the number of Chipper Node NFTs linked to your wallet. 2.5 Select the NFTs you wish to deploy from the displayed list. > **Tip: Upper limit of 10 delegations per Node.** ### Step 4: Set up your subscription 4.1 Select your desired subscription duration. Longer subscriptions offer reduced monthly rates. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). > **Tip: * If you have **NodePoints** or a discount code, apply them at this step.** 4.2 Click **Continue to Pay** to proceed. 4.3 Complete Payment If you have a Promo to redeem, you can use this when you pay to deploy your Node. No need to topup, you're ready for Step 3. ### Step 5: (Optional) Confirm Node activation Once payment is complete, your DIN Chipper Node status will change to **Running** in the NodeOps Console. Congratulations! Your DIN Chipper Node is now active and contributing to the DIN network. ## FAQ - What's the pricing for deployment? | Duration (Months) | Discount (%) | 1–10 Keys $ (per m) cost | |-------------------|--------------|---------------------------| | 1 | NA | (4.00) 4.00 | | 3 | 5% | (3.80) 11.40 | | 6 | 10% | (3.60) 21.60 | | 12 | 20% | (3.20) 38.40 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance - Learn more from the [DIN documentation](https://docs.din.lol/din-cook-data-for-ai) --- ### Fuse > How to Run Your Fuse Nodes | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/fuse [Fuse](https://www.fuse.io/) is a customizable suite of financial products and payment solutions for businesses and users in Web3. ## Prerequisites - EVM-compatible wallet - NFT Light license key - $FUSE to pay transaction fee - Sufficient funds or credits for your Node subscription ## Run your light Nodes for Fuse with NodeOps Console This guide supports you to deploy Fuse light Nodes. Use the video or walkthrough to understand how to set up your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node 1. Ensure your wallet is connected. 2. Navigate to **Node Deployment** on the left side menu and select **Fuse**. ### Step 3: Set up your Node subscription 1. Select the correct Node tier. 2. Choose the number of Nodes you'd like to purchase and the subscription period. 3. Click β€œPay” to start the payment process: To pay with $FUSE: - Confirm the transaction in your wallet. - Wait for the transaction to be verified on the blockchain. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 4: Verify your deployment Once the payment is confirmed, you will be redirected to [NodeFolio](https://console.nodeops.network/dashboard). 1. Wait for a couple of minutes for the Deployment status to change from Pending to Running. 2. Check your logs. Once the status is Running, the logs will automatically display the steps, to validate if your Node is working fine. ### Step 5: Delegate your Node To initiate delegation, click **Click to Delegate** to see your Node's status. > **Info: Delegation takes place on the Fuse Network.** Congratulations your Node is successfully running. You can confirm this from: - [NodeFolio](https://console.nodeops.network/dashboard) ## FAQ - What's the pricing for deployment? | Duration (In Months) | Discount | Total (in $) | | ----- | ----- | ----- | | 1 | NA | 12 | | 3 | 5% | 34 | | 6 | 10% | 65 | | 12 | 20% | 115 | | 24 | 25% | 216 | | 36 | 30% | 302 | - What are the available payment options? > You can pay in FUSE native token, or the normal options (listed in the table below) - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: - Which chain they are Fuse live on? > They are live on their own Native network Fuse. ## What next? - Reach out on Discord if you need further assistance - Learn more from the [Fuse Network docs](https://docs.fuse.io/) --- ### Huddle01 > Node Deployment Step-by-Step Guide | Powered By NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/huddle01 [Huddle01](https://huddle01.com/) is decentralizing audio and video connectivity. ## Prerequisites - EVM-compatible wallet - Gas fees - NFT license - Sufficient funds or credits for your Node subscription ## Run your Huddle01 Nodes with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Select Huddle01 & Connect Wallet 1. Navigate to the NodeOps Console. 2. Select Huddle01 from the list of available Nodes. 3. Connect your preferred EVM Wallet. ### Step 2: Fetch NFT & Select Pool Once your wallet is connected, you need to fetch your NFT license and choose a staking pool. #### You have two pool options: πŸ”Ή 4 CPU Pool β†’ Supports up to 10 delegations. πŸ”Ή 8 CPU Pool β†’ Supports up to 40 delegations. Select the appropriate pool size based on your needs. ### Step 3: Complete Payment 1. Review your selection and confirm the pool size. 2. Proceed to payment checkout. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). Once the payment is confirmed, your Node deployment process will proceed. ### Step 4: Select Nodes and Deploy 1. Choose the Nodes from the available list. 2. Click on the Delegate button to finalize the Node setup. Your Node will now be active and processing delegations. πŸŽ‰ Congratulations! Your Huddle01 Node is successfully deployed and delegated. You can monitor your Node's performance via the NodeOps dashboard. ## FAQ - What is the pricing for Node Deployment? > Please Note: Above 10 licenses, the cost is $1 per license per month | Duration (In Months) | Discounts | $ cost for up to 10 licenses| | -------------------- | --------- | ---------------------------- | | 1 | N/A | 4 | | 3 | 5% | (3.80) 11.40 | | 6 | 10% | (3.60) 21.60 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: - Which chain are Huddle01 live on? > It's live on their own testnet chain - Is it an incentivized testnet? > Yes, it is incentivized testnet. - Where can I check the rewards? > You can check the same on Huddle01 Node delegation [dashboard](https://www.huddle01.network/) after connecting your wallet. - What is the difference between 4 CPU and 8 CPU Compute? > You can delegated up to 10 licenses in 4CPU and up to 40 licenses in 8CPU resource. Please check Huddle01 [docs](https://docs.huddle01.com/docs) for more information. ## What next? - Reach out on Discord if you need further assistance - Learn more from [Huddle01's docs](https://docs.huddle01.com/docs) βœ… Monitor Node activity and rewards in the respective dashboards. βœ… Ensure your Node remains active to avoid delegation interruptions. βœ… Join the Huddle01 & NodeOps community for updates and support. --- ### Hybrid > Hybrid Integrity Node | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/hybrid [Hybrid](https://buildonhybrid.com/) is a Web3-native ecosystem designed to empower the development, monetization, and interaction with AI agents and blockchain-powered applications. It operates as an [Ethereum Layer 2](https://ethereum.org/en/layer-2) solution, built on the [Arbitrum Nitro]( https://docs.arbitrum.io/welcome/get-started) framework, and integrates a [Mixture of Experts](https://arxiv.org/abs/1701.06538) (MoE) architecture to deliver scalable and intelligent AI capabilities. Integrity Nodes earn rewards in 3 ways: - $HYB token allocation - Gas fees from transactions on the Layer 2 blockchain - Revenue from the Hybrid SDK and Agents Hybrid doesn't solely rely on token allocations for rewards, instead, Integrity Nodes are designed for long-term earning sustainability. ## Prerequisites - EVM-compatible wallet containing: - Hybrid Integrity Node license - Arb ETH for the operator wallet - Sufficient funds or credits for your Node subscription ## Run your Hybrid Integrity Nodes with NodeOps Console This guide supports you to deploy Hybrid Integrity Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Set up your Node 2.1 Navigate to **Node Deployment** on the left side menu and select **Hybrid**. **Show me** 2.2 If you're logged in with the wallet containing your Hybrid NFT/s, skip to 2.3. Click **Connect wallet** to connect the EVM-compatible wallet containing your Hybrid Integrity Node license/s. **Show me** 2.3 Click **Fetch NFT**. > The system will display the number of NFTs linked to your wallet. **Show me** 2.4 Select the NFTs you wish to deploy from the displayed list. > **Tip: Upper limit of 50 delegations per Node.** ### Step 3: Set up your subscription 3.1 Select your desired subscription duration. Longer subscriptions offer reduced monthly rates. 3.2 Click **Purchase and Deploy** to proceed. **Show me** 3.3 Complete Payment > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). If you have a Promo to redeem, you can use this when you pay to deploy your Node. No need to top up, you're ready for Step 4. ### Step 4: Delegate your NFT license 4.1 From the [NodeFolio dashboard](https://console.nodeops.network/dashboard) under **Deployments**, click your Hybrid Node. Notice the flag **Action Required**. **Show me** 4.2 Copy the NodeOps Operator wallet address and click **Delegate Here**. **Show me** 4.3 From Hybrid's delegation dashboard [nodes.buildonhybrid.com](https://nodes.buildonhybrid.com), click **Delegate NFTs** and paste the wallet address copied in the previous step. **Show me** 4.4 Review and sign the transaction request. ### Step 5: (Optional) Confirm Node activation Once payment is complete, your Hybrid Node status will change to **Live** in the NodeOps Console. Congratulations! Your Hybrid Node is now active and contributing to the Hybrid network. ## FAQ - What's the pricing for deployment? | Duration (Months) | Discount (%) | $ per month cost | $ Total | |-------------------|--------------|------------------|---------| | 1 | N/A | 20 | 20 | | 3 | 10% | 18 | 54 | | 6 | 20% | 16 | 96 | | 12 | 30% | 14 | 168| - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance - Learn more from the [Hybrid documentation](https://docs.buildonhybrid.com) --- ### HYCHAIN > How to Run a Hychain Guardian Node in a one-click powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/hychain [HYCHAIN](https://www.hychain.com/) is an Ethereum L2 Rollup and a suite of Web3 infrastructure that was created to eliminate onboarding and technical challenges for Web3 games aiming for widespread adoption. ## Prerequisites - EVM-compatible Wallet containing: - Sufficient funds or credits for your Node subscription - Node Key to run a Guardian Node - 3-5 $TOPIA > **Tip: Node Keys** Node Keys can be purchased from HYCHAIN at [Nodes.Hychain.com](https://nodes.hychain.com/). As the official Node Infrastructure partner for HYCHAIN, use code "nodeops" to get an additional discount on your Node Key Purchase. > **Tip: $TOPIA** You can bridge $TOPIA from the Ethereum Network using [bridge.hychain.com/deposit](https://bridge.hychain.com/deposit) ## Run a HYCHAIN Guardian Node with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node 1. Navigate to **Node Deployment** on the left side menu and select **HYCHAIN**. 2. Update the **Quantity** to determine how many Nodes to deploy. 3. Select HYCHAIN & Type of Node as **Guardian Node**. 4. Connect your EVM-compatible wallet to make the Node Key available. ### Step 3: Set up your Node subscription Subscribe by selecting the duration (in months) and pay. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 4: Delegate your keys Once Payment is Successful, you'll be redirected to the Dashboard where you'll see the Action Required. Under this Step, select **Click to Delegate** to Delegate the Keys to assign a Guardian Operator for your keys. This is redirected to [delegate.xyz](https://delegate.xyz) which takes care of delegating & assigning the keys to an Operator. ### Step 5: Verify your deployment Head over to the NodeOps Dashboard and wait for 10-30 s for your Guardian Nodes to be up and running. You should see the Node info along with respective logs for your Nodes. ## Claim rewards Click On the Claim Rewards Button (Once A Day). This submits a request to claim the rewards based on Assertions Submitted & Participated. All the Gas Fees are typically paid in $TOPIA which is covered by NodeOps. So, users don't have to worry about funding their wallets with $TOPIA. ## FAQ - What's the cost of running a Guardian Node? | Duration (Months) | 1–10 Keys $ (per m) cost | 11–50 Keys $ (per m) cost | 51–100 Keys $ (per m) cost | 100+ Keys $ (per m) cost | |-------------------|--------------------------|----------------------------|-----------------------------|---------------------------| | 1 | (20) 20 | (25) 25 | (30) 30 | (35) 35 | | 3 | (18) 54 | (22.5) 67.5 | (27) 81 | (31.5) 94.5 | | 6 | (16) 96 | (20) 120 | (24) 144 | (28) 168 | | 12 | (14) 168 | (17.5) 210 | (21) 252 | (24.5) 294 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: - Do I need to Purchase a new Subscription if I purchase a new key? > If you purchase a new key using the same wallet, you don't have to do anything. It would automatically be fetched and set up by our infrastructure in 6h intervals. > If you purchase a new key using a different wallet, You would have to set a new subscription > All the subscriptions would be per wallet basis, you can use the same email to have a single dashboard for all your keys and Nodes, we call it NodeFolio - Do I need $TOPIA in my Wallet? > Yes, you need $TOPIA initially to perform Step 3 of delegating the keys to a guardian (typically 3-5 TOPIA). You can bridge it from the Ethereum Network using [https://bridge.hychain.com/deposit](https://bridge.hychain.com/deposit). - Is the Guardian Operator Dedicated One Per User? > Yes, Every User (Signed Up Per Email) would have a dedicated guardian operator. - Can I have all my wallets under a single dashboard? > Yes, you can. Sign in with the same email, connect all your wallets, and subscribe using the same email. You would have the same Dashboard (NodeFolio). ## What next? - Reach out on Discord if you need further assistance - Learn more from the [HYCHAIN docs](https://docs.hychain.com/docs/getting-started) --- ### iAgent Node bootstrapping guide > iAgent Protocol Node Setup Guide | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/iagent/bootstrapping The [iAgent Protocol](https://www.iagentpro.com/) allows gamers to train AI agents using gameplay footage; supported by DePIN decentralized computing. iAgent introduces a new digital asset class on the blockchain. iAgent operates through a network of publicly maintained computers known as 'Protocol Nodes', which secure the network, manage GPU worker rewards, and earn rewards for their contributions. How to Set Up Your iAgent Protocol Node via Node Bootstrapping This tutorial provides a step-by-step guide for purchasing your iAgent Protocol license and deploying it, all through a streamlined process. > **Info: If you already own a license and wish to delegate that, use the [delegation guide](./delegating.md).** ## Prerequisites - EVM-compatible wallet - Sufficient funds or credits for your Node subscription ## iAgent Node Bootstrapping with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node 1. Navigate to **Node Deployment** on the left side menu and select **iAgent**. 2. Update the **Quantity** to determine how many Nodes to deploy. 3. Review the details and confirm your selection. ### Step 3: Set up your Node subscription 1. Connect Your Wallet and Subscribe: Connect your wallet to proceed with the subscription process for deploying your Nodes. If you participated in the iAgent Pre-sale, the platform will automatically detect the number of Nodes you own. If not, you can select the number of Nodes you wish to purchase and specify the deployment duration. To manage the Nodes yourself, simply check the β€œClaim Node(s) without deploying” box. 2. Complete Payment: Click **Pay** to begin the payment process. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 4: Delegate Your Node 1. After completing the payment, you will be redirected to Nodefolio, where a unique delegation URL will be generated for you. Please wait until the message "Generating Delegation URL" updates to "Click to Delegate." Once "Click to Delegate" appears, click on it, then select "Delegate Here" to initiate the delegation process. This will redirect you to the iAgent Dashboard to finalize the delegation. | Unique URL been generated | Proceed with delegation | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXcJcXPXSc8iIKIF0JNJBTk_wV-S5kaloXknZyMZzHBkCClD-723sEye2eCBvYcXruZMhfymJjJIXz2Bzv1HLveu7yBTyUyPROCzxYzku30ORcKE4RNaJiW3-uA6crL6Vp378SvD2Jcq9yZx_nhMwQjS4hj3s0c3QVnd6PGT7A?key=YtV8ryCXgt4jpfQSVdARaQ) | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXdmdl84Rr6xnqvU4pmGKlaNWyj2UVhv5xQEL1So8lOFm8gTV3RO7RX-xQ0Sq0hyJW--Hzp3WRsPse-JDNxEEn0d5X0eUekI39A_8Livvs2fSBBqQYgZZoC4BuJcZaMwUWWQl9whEorqcR0NHt4uuEobhBnaK9d-XdX1WBNynQ?key=YtV8ryCXgt4jpfQSVdARaQ) | 2. Connect your wallet to the iAgent Dashboard Connect the wallet that holds your NFT to the iAgent Dashboard. 3. View and Map NFTs On the licenses page, click β€œView NFTs” to see the licenses associated with your PCID. Select the NFTs you want to delegate and click β€œMap”. Alternatively, click β€œMap All” to delegate all your licenses. You will receive a notification confirming successful mapping. ### Step 5: (Optional) Verify your deployment Congratulations! Your iAgent Protocol Node is now set up. Return to Nodefolio to see the status of your Node update from β€œClick to Delegate” to β€œRunning”. ## FAQ - What is the cost to deploy iAgent Nodes? β†’ The discounts increase with an increase in the duration of the subscription. However, regardless if you hold 1 or 5 licenses in a wallet, the prices are as mentioned below; | Duration (In Months) | Price Per Month (In USD) | Total Price (In USD) | | -------------------- | ------------------------ | -------------------- | | 1 | 25 | 25 | | 3 | 23.75 | 71.25 | | 6 | 22.5 | 135 | | 12 | 20 | 240 | | 24 | 18.75 | 450 | | 36 | 17.5 | 630 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: - I clicked on Participate, closed the window by mistake leading to incomplete payment and its now showing me that I need to pay again, What do I do? β†’ We ideally reserve and lock your allocation for 25 mins to give you sufficient time to pay, If you have not completed the payment during this 25 mins, you can check back again after 25 mins and continue - How can I deploy the Nodes for free 2 months? β†’ You will have to take a minimum of 1 month subscription to get 2 months free. - Can I connect multiple wallets to have a unified way to manage my Nodes? β†’ Yes, you can and delegate + manage all your Nodes to a single seamless dashboard - Where can I check my NFTs? β†’ Use this to check your iAgent NFTs in the respective wallets. Please replace WALLET_ADDRESS with your wallet address at the end of the link at the end of the link [https://eth.blockscout.com/token/0xff51A51F38F26BC03085642aA1a7082D7845c94d?tab=inventory&holder_address_hash=WALLET_ADDR](https://eth.blockscout.com/token/0xff51A51F38F26BC03085642aA1a7082D7845c94d?tab=inventory&holder_address_hash=WALLET_ADDR) - How can I manage my Nodes with multiple wallets? If you're using multiple wallets, double-check on the iAgent Dashboard (https://node.iagentpro.com/) that you're connected to the desired wallet before proceeding with the "Delegate Now" option in the NodeOps Console. Connecting with the wrong wallet may result in associating your Node's PCID with an unintended wallet address, potentially causing issues with delegation and Node management. Always verify your wallet connection to avoid complications. - Can I delegate my Nodes with NodeOps, if I have more than 5 Nodes? Yes, regardless you have more than 5 Nodes in a single wallet or multiple wallets, you can delegate them with NodeOps. ## What next? - Reach out on Discord if you need further assistance --- ### iAgent NFT delegation guide > If you have multiple Nodes in a single wallet or previously chose not to deploy with NodeOps but now want to proceed, you can follow the steps outlined here. URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/iagent/delegating ## Prerequisites - EVM-compatible wallet - Sufficient funds or credits for your Node subscription - iAgent Protocol Node NFT ## Subscription Purchase Process ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node 1. Navigate to [Node Deployment Page](https://console.nodeops.network/deployNode/), and select **iAgent**. 2. Update the **Quantity** to determine how many Nodes to deploy. 3. Review the details and confirm your selection. ### Step 3: Set up your Node subscription 1. Opt for the defualt **Genesis Node** for the Node type. 2. Click **Connect Wallet** to link your wallet containing the iAgent Protocol Node NFT. 3. Once connected, select **Fetch NFT**, and the system will automatically retrieve and display the number of NFTs associated with your wallet. 4: Select your subscription duration. The longer your subscription, the lower your monthly cost. If you have NodePoints, you can redeem them for a discount, and if you have a discount code, you can apply it here as well. After selecting your subscription and optionally applying your NodePoints and/or discount code, click "Continue to Pay" to proceed with payment. 5. Complete Payment > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 4: Delegate Your Node 1. After completing the payment, you will be redirected to NodeFolio, where a unique delegation URL will be generated for you. Please wait until the message "Generating Delegation URL" updates to "Click to Delegate." Once "Click to Delegate" appears, click on it, then select "Delegate Here" to initiate the delegation process. This will redirect you to the iAgent Dashboard to finalize the delegation. 2. Connect your wallet to the iAgent Dashboard Connect the wallet that holds your NFT to the iAgent Dashboard. 3. View and Map NFTs On the licenses page, click β€œView NFTs” to see the licenses associated with your PCID. Select the NFTs you want to delegate and click β€œMap”. Alternatively, click β€œMap All” to delegate all your licenses. You will receive a notification confirming successful mapping. 4. Confirmation Congratulations! Your iAgent Protocol Node is now set up. Return to Nodefolio to see the status of your Node update from β€œClick to Delegate” to β€œRunning”. ## FAQ - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance --- ### KIP > How to Run Your KIP Checker | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/kip [KIP](https://www.kip.pro/) provides data and payment rails to connect owners of AI assets – models, apps and datasets – letting them compete and collaborate freely within a decentralized ecosystem. As in any decentralized system, KIP's goal is trustless coordination: requiring legions of indexers, validators, checkers, voters, bundlers, and RPC providers. From the validators who update the underlying chain, to the indexers who make on-chain data available for query, to the voters who exercise governance powers. Checker Nodes within KIP Protocol's system play a role in both the operations and the governance of the system as a whole and are rewarded in $KIP. ## Prerequisites - EVM-compatible wallet - Sufficient funds or credits for your Node subscription - KIP Checker Node license ## Set up a KIP Checker Node with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Navigate to the Node Deployment Menu 1. Navigate to **Node Deployment** on the left side menu and select **Kip**. 2. Update the **Quantity** to determine how many Nodes to deploy. ### Step 3: Connect Your Wallet Click β€œConnect Wallet” to link the wallet containing your Checker Node NFT. After connecting, click β€œFetch NFT” to allow the console to automatically detect the NFTs in your wallet. ### Step 4: Choose Your Subscription Duration Select your desired subscription duration. Longer subscriptions reduce your monthly cost. You can also apply a discount code if available. Once finalized, click β€œContinue to Pay” to proceed. ### Step 5: Complete Payment > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 6: Initiate Node Delegation After payment, you'll be redirected to Nodefolio. Locate the newly deployed Node, which will show an β€œAction Required” status. Click β€œClick to Delegate” to start the delegation process. ### Step 7: Complete the Delegation Process A pop-up window will appear. Select the licenses to which you want to delegate your Node, click β€œDelegate,” and sign the transaction. Ensure you have sufficient ETH in your wallet to cover gas fees. ### Step 8: Confirm and Verify Your KIP Checker Node is now fully deployed. Return to Nodefolio to confirm the status of your Node. The status will change from β€œClick to Delegate” to β€œRunning,” indicating successful setup. You're now ready to start earning rewards with your KIP Checker Node! ## FAQ - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? If you encounter any issues or have questions, use the Discord link in the footer below for guidance. - Learn more from the [KIP Protocol docs](https://kipprotocol.gitbook.io/kip-node-documentation) --- ### Lumoz > Lumoz Testnet Node Setup Tutorial | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/lumoz [Lumoz](https://lumoz.org/) is a globally distributed modular computing network that leverages a DePIN network to offer a secure and flexible computing platform for users around the world. Lumoz focuses on advanced zero-knowledge proof (ZKP) services, supports Rollup network development, and provides computational power for AI technologies. At the heart of this ecosystem is the Lumoz zkVerifier Node, a universal verification Protocol on-chain, providing data verification services to enterprises and users. With just a standard server, you can easily participate in zero-knowledge computation verification through Lumoz. ### Prerequisites: - EVM-compatible wallet - Sufficient funds or credits for your Node subscription - zkVerifier License - MOZ tokens for gas fees > **Tip: Refer to the [Lumoz documentation](https://docs.lumoz.org/delegate-licenses/claim-testnet-license) for instructions on how to obtain the testnet license and MOZ test tokens.** ## Set up your Lumoz zkVerifier Node with NodeOps This tutorial guides you through the process of deploying your Lumoz zkVerifier Node using NodeOps. ### Step 1: Connect with the Console ### Step 2: Select your Protocol and Node 1. Navigate to the [Node Deployment page](https://console.nodeops.network/deployNode) and select Lumoz. 2. Select Node Type Choose the default **Verifier** as the Node type. 3. Connect your wallet containing the Lumoz zkVerifier Testnet License by clicking **Connect Wallet**. Once connected, select **Fetch NFT**, and the system will display the number of NFTs linked to your wallet. ### Step 3: Configure rewards After connecting your wallet and fetching the associated NFTs, you'll need to configure the following reward distribution options. These options define how rewards from validation tasks are divided between the Node operator, license delegators, and esMOZ stakers. #### Definition This is the portion of the verification rewards that the Node operator (you) retains as a commission. It is a percentage of the total rewards earned by the Node for performing verification tasks on the network. #### How it works You can set a commission rate (default is 5%). This percentage is deducted from the total verification rewards before the remaining rewards are distributed to other participants (that is, esMOZ stakers and license delegators). #### Example If your Node earns 100 MOZ tokens in rewards and you set a commission of 5%, you'll keep 5 MOZ tokens as your commission, and the remaining 95 MOZ tokens will be split between the stakers and delegators. #### Definition The delegate split is the percentage of the remaining rewards (after your commission is deducted) that is allocated to license delegators. License delegators are users who delegate their licenses to your Node, contributing to its operational capacity. #### How it works After the commission is deducted, the remaining rewards are distributed based on the delegate split percentage. The default value is set to 45%, but you can customize this to a percentage that fits your preference. #### Example If the remaining rewards after your commission are 95 MOZ tokens and you set the delegate split to 45%, then 42.75 MOZ tokens (45% of 95) will be allocated to the license delegators. #### Definition The staking split is the percentage of the remaining rewards allocated to esMOZ stakers. These are users who stake esMOZ tokens to support your Node and help maintain the network's integrity. #### How it works After the commission is deducted, and the delegate split is applied, the staking split determines how much of the remaining rewards are distributed to stakers. The default is set at 50%, but you can modify this to suit your desired allocation. #### Example Using the same 95 MOZ tokens after the commission, if you set the staking split to 50%, then 47.5 MOZ tokens (50% of 95) will go to the esMOZ stakers. > **Tip: The sum of Commission Rewards, Delegate Split, and Staking Split must always equal 100%. For example:** - Commission Rewards: 5% - Delegate Split: 45% - Staking Split: 50% = Total: 100% You can adjust these values to reflect how you wish to distribute the rewards, ensuring that the total percentages across all categories always add up to 100%. ### Step 4: Set up your Node subscription 1. Choose Subscription Duration Select your preferred subscription length. Longer subscriptions offer lower monthly rates. If you have NodePoints or a discount code, you can apply them here. Click Continue to Pay to proceed. 2. Complete Payment > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 5: Delegate your Node Once the payment is complete, you will be redirected to Nodefolio. You'll see your newly created Node with a "Click to Delegate" button. Click this button, and your wallet's NFTs will be displayed. Complete the delegation process by selecting Click to Delegate. Congratulations! Your Lumoz zkVerifier Node is now active. The status of your Node should change to Running. ### Step 6: (Optional) Confirm your Node deployment Within 10-15 seconds, your Nodes should be up and running. You can view your Node under the [My Node](https://quidditch-zkverifiers.lumoz.org/my-node) section. For further assistance or troubleshooting contact our [Discord](https://discord.com/invite/JCZgbSZqaH) help desk. ## Node maintenance Lumoz requires you to update the JSON RPC used by your Node. 1. Login at [verifier.lumoz.org/my-node](https://verifier.lumoz.org/my-node). 2. Click **Verify**. 3. Enter RPC to verify: `https://rpc.lumoz.org` 4. You can now initialize the Node, use the video to follow along: ## FAQ ## What next? - Reach out on Discord if you need further assistance --- ### Nexus > NodeOps provides containerized infrastructure specifically curated for developers and Node operators designed to simplify the development process and operations for Web3 Protocols. URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/nexus [The Nexus Network](https://x.com/NexusLabs) is pioneering the future of verifiable computation by building a hyperscale decentralized supercomputer β€” purpose-built for AI workloads, blockchain applications, and privacy-enhancing technologies. Nexus Testnet III marks the final phase before mainnet launch. It’s your opportunity to explore the network, test tools and applications, and earn rewards by contributing Compute to a decentralized, zero-trust system. ## Prerequisites - EVM-compatible wallet - Sufficient funds or credits for your Node subscription ## Run your Prover Nodes via NodeOps Console This guide supports you in deploying Prover Nodes. Use the video or walkthrough to understand how to set up your Nodes. ## Deploy Nexus Testnet Nodes with NodeOps Console ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node Navigate to **Node Deployment** on the left side menu and select **Nexus**. ### Step 3: Generate CLI Node Id Proceed to [Nexus Dashboard](https://app.nexus.xyz/nodes) and click **Add CLI node**, then copy the Node Id. ### Step 4: Set up your Node subscription Paste the Node Id and pay. Once the Payment is successful, you'll automatically be redirected to the NodeFolio. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 5: (Optional) Verify your deployment Wait for a couple of minutes for the Deployment status to change from Pending to Running. ## FAQ - What's the pricing for deployment? | Duration (Months) | Discount (%) | $ per month cost | $ Total | |-------------------|--------------|------------------|---------| | 1 | N/A | 15.00 | 15.00 | | 3 | 5% | 14.25 | 42.75 | | 6 | 10% | 13.50 | 81.00 | | 12 | 20% | 12.00 | 144.00 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance - Learn more from the [Nexus Documentation](https://docs.nexus.xyz/home) --- ### 0G > Follow this step-by-step guide to deploy your 0G AI Alignment Node on NodeOps Network URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/og-alignment [0G](https://0g.ai/) has created a decentralized AI Layer 1 ecosystem, to support AI with scalability. ### 0G Node NFTs NFTs representing Node license are [available to the 0G community](https://0g.ai/blog/0g-foundation-ai-alignment-node-sale-101-key-details-and-how-to-participate) in order to gain access to operate an AI Alignment Node and earn token emissions for helping to secure the network. With NodeOps Console, you may either: - [Subscribe to deploy a Node and then delegate the NFT to that Node](#run-your-0g-alignment-nodes-with-nodeops-console) - [Delegate the NFT to NodeOps to earn a share in its rewards](#delegate-your-0g-alignment-nft-to-earn-commission) > **Tip: Node Operators who buy 0G NFTs through NodeOps get 2 months free Node hosting. Users who buy through [CoinList](https://coinlist.co/0g-node-sale/) will receive a 15% discount on deployments.** ## Run your 0G Alignment Nodes with NodeOps Console Use the video or walkthrough to understand how to delegate your NFT license and deploy your 0G Alignment Nodes. > Remember, if you are deploying a Node you will **not** use the **Node Delegation** tab. ### Prerequisites - EVM-compatible wallet holding the 0G NFT - Sufficient funds or credits for your Node subscription > **Tip: Commission-based flow available** If you don't want your own dedicated Node, you may [delegate your NFT](/Get-Started/Console/commission-based) and take a share in the commission earned. ### Step 1: Connect Wallet > Remember to either sign in with the wallet that holds your 0G NFT, or to link that wallet to your account. 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Deploy your Node 1. Navigate to **Node Deployment** on the left side menu and select **0G**. **Show me** 2. Click **Fetch NFT** to verify the NFT/s in your wallet before committing to a deployment. **Show me** 3. Select the **duration** of the Node subscription then click **Purchase and Deploy**. **Show me** 4. Apply Promo Codes (if applicable) and complete the payment. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). Allow 3-5 minutes for your Node to deploy to move to Step 3. ### Step 3: Delegate your NFT license to the Node Your Node has its own operator wallet to manage your NFT license, to delegate: 1. Navigate to the NodeFolio page from the left hand menu, and select an 0G Alignment Node instance with **Action Required** status. **Show me** 2. Click **Fetch NFT** and select the NFT to delegate based on its identifier. **Show me** 3. Select **Click to Delegate** and confirm the delegation transaction in your wallet. Congratulations: your Node status will switch from **Action Required** to **Running**. ### Step 4: (Optional) Verify deployment Once the transaction is confirmed, your 0G Alignment Node will be deployed. You can monitor your Node's status through the NodeOps Console. ### FAQ - What is the 0G Alignment Node and how is it useful? > An 0G AI Alignment Node monitors the functionality of 0G’s DA, Storage, Serving, and Validator Nodes, identifies malicious data injection, and supports AI model training by reducing drift. - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## Delegate your 0G Alignment NFT to earn commission > Remember, if you are delegating a Node for commission-based earnings, you will **not** use the **Node Deployment** tab. Use the video or walkthrough to understand how to delegate NodeOps to run a Node with your NFT license. No need to set up or subscribe to run a Node. ### Prerequisites - EVM-compatible wallet with the 0G NFT ### Step 1: Connect Wallet > Remember to either sign in with the wallet that holds your 0G NFT, or to link that wallet to your account. ### Step 2: Delegate your NFT 1. Navigate to **Commissioned Delegation** and select 0G's **Register**. **Show me** 2. Navigate to the **My Delegations** tab then click **Delegate**. **Show me** 3. Select the NFT based on its identifier, and click **Approve**. **Show me** 4. Approve the delegation transaction in your wallet, click **Delegate**, then approve the final transaction. **Show me** Congratulations, your NFT is now earning commission. ### (Optional) Step 3: Review your delegations From the **Node Delegation** page, select the **My Delegations** tab to track your current NFT delegations. ### FAQ - What is the commission rate for delegating my 0G NFT to NodeOps? > You earn 98% of the rewards, while NodeOps earns 2%. ## Gotchas A common gotcha is to muddle up the two paths! If you are deploying a Node you will never need to go to the **Node Delegation** tab. If you are delegating a Node for commission-based earnings, you will never need to go to the **Node Deployment** tab. ## What next? - πŸ”— Learn more [about Alignment Nodes from 0G's docs](https://docs.0g.ai/concepts/ai-alignment?_highlight=alignm#what-are-ai-alignment-nodes) - Reach out on Discord if you need further assistance: see Community link in the footer --- ### OpenPad > Follow this step-by-step guide to deploy your OpenPad Node on NodeOps Network URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/openpad [OpenPad](https://openpad.io/homepage) is leveraging decentralized AI to deliver data-backed investment strategies. ## Prerequisites - EVM-compatible wallet - NFT license - Sufficient funds or credits for your Node subscription ## Run your OpenPad Verifier Nodes with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Connect wallet and fetch NFT - Ensure your wallet is connected to the NodeOps Console. - Fetch your NFT to proceed with delegation. ### Step 3: Enter commission - Set your preferred commission rate. - This allows you to receive commissions when other Node runners delegate their licenses to your operator wallet generated via NodeOps. ### Step 4: Select duration and pay - Choose the duration for your delegation. - Complete the payment to proceed. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 5: Delegate Your Verifier Node - Important: OpenPad's dashboard delegation feature will go live on Feb 8, 2025. - Until then, complete the delegation via the NodeOps Dashboard. ### Step 6: (Optional) Verify your deployment - Once the delegation is complete, verify the logs to ensure successful setup. ## FAQ - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: - What is the subscription cost? | Duration (Months) | Discounts (%) | Price up to 100 licenses (per m) $ | |-------------------|----------------|-------------------------------------| | 1 | NA | (15) 15 | | 3 | 5% | (14.25) 14.25 | | 6 | 10% | (13.50) 13.50 | | 12 | 20% | (12) 12 | - What is the commission rate while deploying? > The commission rate allows NodeOps users to charge delegation fees from Node runners who delegate to their operator wallets. ## What next? - Reach out on Discord if you need further assistance. - Learn more from [OpenPad's documentation](https://docs.openpad.io/) --- ### PlayAI > PlayAI NodeBootstrapping Guide | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/playai [Play AI](https://play.ai/) is revolutionizing consumer intelligence by becoming the AI orchestration layer for data, training, and inference across various consumer-focused products. Play AI's platform enables seamless data access, allowing: β€’ Users to earn rewards β€’ Developers to create enhanced user experiences β€’ Node runners to earn rewards β€’ Partners and KOLs to benefit from referral programs ## Prerequisites - EVM-compatible wallet - PlayAI NFT - Sufficient funds or credits for your Node subscription ## Run your PlayAI Nodes with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node Navigate -> **NodePad** -> **Bootstrapping** page to find the PlayAI Protocol. ### Step 3: Connect Your Wallet Connect your EVM-compatible wallet. This wallet will hold your PlayAI Oasis NFT, which operates on the Base blockchain. ### Step 4: Select Nodes and Choose Deployment Option Choose the number of Nodes you'd like to purchase, then select one of the following deployment options: * Option 1: Purchase and Deploy Let us handle Node operation, including monitoring, updates, and maintenance. This option removes all the technical complexities of Node management. * Option 2: Purchase Only If you prefer to manage and operate your Node independently, choose this option. Note: If you select Option 1, you will also need to specify the duration of your Node operation. ### Step 5: Apply Promo Code (If Applicable) If you have a promo code, enter it now and click "Apply." ### Step 6: Complete Payment Click β€œPay” to start the payment process. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 7: Delegate Your Node Once the payment is confirmed, you'll be redirected to Nodefolio. A unique Node will be created for you. To initiate delegation, click "Click to Delegate." Ensure you connect the same wallet containing your PlayAI NFT that you used during the purchase. Delegation takes place on the Base Sepolia network, so you'll need some ETH on Base Sepolia for gas fees. You can obtain free ETH from a faucet like Alchemy Faucet. ### Step 8: Confirm Node deployment Congratulations! Your PlayAI Oasis Node is now set up. Return to [NodeFolio](https://console.nodeops.network/dashboard) to see your Node's status change from "Click to Delegate" to "Running." For any assistance or troubleshooting, please refer to our support resources or contact our help desk. ## FAQ - Price to deploy PlayAI Oasis Nodes? | Duration (Months) | Discount (%) | 1–10 Keys $ (per m) cost | |-------------------|--------------|---------------------------| | 1 | NA | (9.00) 9.00 | | 3 | 5% | (8.55) 25.65 | | 6 | 10% | (8.10) 48.60 | | 12 | 20% | (7.20) 86.40 | | 24 | 25% | (6.75) 162.00 | | 36 | 30% | (6.30) 226.80 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: - Type and Usage of the Nodes? > Play Oasis Nodes. Oasis Nodes drive the verification and processing of video data within the Play AI ecosystem. In the current version, AI models running on Docker handle the processing to ensure that video data files from users and the community meet specific requirements. - Which network are PlayAI going live on? > Base - Is there an option to buy the native tokens, except earning from the rewards? > $PLAI Tokens are not live, so there is no way to buy. > Users can still earn more rewards through our Play Collective & other upcoming products, being active in the community etc. - Are there any tasks to be completed by the users apart from running the Nodes? > Nodes are a a passive earning opportunity. Apart from Nodes, users can use Play Collective & other upcoming products, be active in the community etc. - Is there any KYC required for claiming the rewards or at any step? > No, there is no KYC steps involved yet at any point of time. - Approx how many rewards does the user receive per day? > Up to 5 $PLAI ## What next? - Reach out on Discord if you need further assistance - View and manage Nodes with the [PlayAI explorer](https://nodeexplorer.playai.network/) where you can check the number of Nodes available in their wallet, Nodes deployed, delegation status, and revoke subscription. > To revoke, users can always see their delegated Nodes and choose to undelegate the Nodes whenever needed. --- ### Rivalz > Rivalz zNode Delegation Guide | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/rivalz [Rivalz](https://rivalz.ai/) introduces an AI Intelligence Layer that powers an ecosystem of modular AI applications. Built on a DePIN (Decentralized Physical Infrastructure Network) framework, Rivalz utilizes Dymension with Celestia and Eigen to operate a RollApp. The AI DePIN layer consists of Light rClients and Validator zNodes. While rClients contribute storage from their devices, zNodes serve as validators, tracking data flows within the DePIN layer and flagging any malicious rNode activity. ## Prerequisites - zNode license (NFT) - EVM-compatible wallet - Sufficient funds or credits for your Node subscription ## Run your Rivalz Nodes with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node 1. Navigate to **Node Deployment** on the left side menu and select **Rivalz**. 2. Update the **Quantity** to determine how many Nodes to deploy. ### Step 3: Set up your Node subscription The "zNode" option should be selected by default. Click "Connect Wallet" to link the wallet that holds your zNode NFT. Once connected, click "Fetch NFT," and the system will automatically display the number of NFTs associated with your wallet. 1. Select your subscription duration Choose your subscription length. Longer subscriptions reduce the monthly cost. If you have NodePoints or a discount code, you can redeem them at this stage. After making your selections, click "Continue to Pay" to proceed. 2. Complete payment. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 4: Delegate Node 1. After completing the payment, you'll be redirected to Nodefolio. The newly deployed Node will be marked with an "Action Required" status. Click "Click to Delegate" to begin the delegation process. 2. Complete the delegation: A pop-up window will display your wallet address and associated NFTs. Click "Click to Delegate" again to confirm and complete the transaction in your wallet. Since the transaction occurs on the Arbitrum Blockchain, a small gas fee may apply. Once successful, you'll see a transaction hash as confirmation. ### Step 5: (Optional) Verify your deployment Congratulations! Your Rivalz zNode is now fully set up. Visit Nodefolio to verify the status, which should change from "Click to Delegate" to "Running". ## FAQ - What's the subscription cost? | Duration (Months) | 1–10 Keys $ (per m) cost | 11–50 Keys $ (per m) cost | 51–100 Keys $ (per m) cost | 100+ Keys $ (per m) cost | 200+ Keys $ (per m) cost | 500+ Keys $ (per m) cost | 1000+ Keys $ (per m) cost | |-------------------|---------------------------|----------------------------|-----------------------------|---------------------------|----------------------------|-----------------------------|------------------------------| | 1 | (3.75) 3.75 | (4.69) 4.69 | (5.63) 5.63 | (7.50) 7.50 | (9.38) 9.38 | (18.75) 18.75 | (37.50) 37.50 | | 3 | (3.56) 10.69 | (4.45) 13.36 | (5.34) 16.03 | (7.13) 21.38 | (8.91) 26.72 | (17.81) 53.44 | (35.63) 106.88 | | 6 | (3.38) 20.25 | (4.22) 25.31 | (5.06) 30.38 | (6.75) 40.50 | (8.44) 50.63 | (16.88) 101.25 | (33.75) 202.50 | | 12 | (3.00) 36.00 | (3.75) 45.00 | (4.50) 54.00 | (6.00) 72.00 | (7.50) 90.00 | (15.00) 180.00 | (30.00) 360.00 | - Which network are they going live on? > Arbitrum - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance - Learn more from the [Rivalz documentation](https://docs.rivalz.ai/) --- ### Sophon commission-based > Step-by-Step tutorial for Sophon Node Delegation via Commission-Based Model on NodeOps Network URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/sophon/commission > **Warning: ⏳ Deadline to Delegate Your Sophon Nodes: January 15th 2025.** ## Prerequisites - Sophon license - EVM-compatible wallet - Sufficient funds or credits for your Node subscription ## Run your Commission-Based Sophon Nodes via NodeOps Console This guide explains how to delegate your Sophon Node using the Commission-Based Model on NodeOps and participate via the NodeOps Network Testnet for a chance to earn more Node Points (NPs). Use the video or walkthrough to understand how to set up your Nodes. ### Step 1: Proceed to NodeOps Testnet and Connect Wallet 1. Visit the [NodeOps Network Testnet](https://cloud.nodeops.network/). 2. Click Connect Wallet to link your preferred wallet. > Ensure your wallet is funded with the necessary tokens for delegation. ### Step 2: Find the "Delegate and Earn" Campaign for Sophon 1. On the NodeOps Network Testnet dashboard, locate the Delegate and Earn campaign for Sophon. 2. Review the campaign details, including rewards and requirements. ### Step 3: Copy the Burner Wallet from the List Provided in "Steps" 1. Within the campaign details, find the burner wallet address assigned to your delegation task. 2. Copy the burner wallet address for use in the next step. ### Step 4: Click on "Delegate" to Redirect to the Sophon Dashboard 1. Click the Delegate button to be redirected to the Sophon Dashboard. 2. Ensure you are on the correct delegation page before proceeding. ### Step 5: Paste the Burner Wallet Address and Complete the Delegation 1. Paste the copied burner wallet address into the designated field on the Sophon Dashboard. 2. Confirm and complete the delegation transaction using your connected wallet. ### Step 6: Check if Your Nodes are Delegated 1. Return to the NodeOps Network Testnet dashboard or the NodeFolio section to verify the status of your delegation. 2. Ensure that the Node is listed as Delegated. ### Step 7: Verify Node deployment 1. If all steps are completed successfully, your Nodes are now active and running. 2. Note: Ignore the Click to Delegate option in the Action Required section as it is not applicable. ## FAQ - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance - Learn more from the [Sophon documentation](https://docs.sophon.xyz/welcome) --- ### Sophon Premium Node Delegation > Step-by-step tutorial for Sophon Premium Node delegation on NodeOps Console. Connect wallet, delegate NFTs, and verify Node deployment. URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/sophon/premium # Sophon Premium Follow this guide to delegate your Sophon Node using the Premium Model on NodeOps Console. This guide ensures a seamless and straightforward delegation process for all users. ### Step 1: Select Sophon Premium and Connect Wallet 1. Log in to the [NodeOps Console](https://console.nodeops.network/deployNode/) and select **Sophon**. 2. Navigate to the Sophon Premium section on the dashboard. 3. Click Connect Wallet to link your preferred wallet. * Ensure your wallet has the required NFT for delegation. ### Step 2: Select Duration and Proceed to Pay 1. Choose the delegation duration that suits your requirements. 2. Review the payment details displayed on the screen. 3. Click Proceed to Pay to confirm your selection and complete the transaction. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 3: Click on NodeFolio and Press β€œClick to Delegate” 1. Once payment is complete, navigate to the NodeFolio section on your dashboard. 2. Locate your Sophon Node and click the Click to Delegate button to initiate the delegation process. ### Step 4: Copy the Burner Wallet Address and Press β€œDelegate Here” 1. A burner wallet address will be generated for your Node delegation. 2. Copy the provided burner wallet address. 3. Press the Delegate Here button to proceed to the next step. ### Step 5: Complete the Delegation 1. Use your connected wallet to confirm the delegation transaction. 2. Ensure the transaction is successfully processed. ### Step 6: Check if Your Nodes are Delegated 1. Return to the NodeFolio section to verify the status of your delegation. 2. Confirm that the Node is listed as Delegated in your dashboard. ### Step 7: Validate Node delpolyment 1. If all steps are completed successfully, your Nodes are now up and running. 2. Note: Ignore the Click to Delegate option in the Action Required section as it's no longer applicable. ## FAQ - What is the cost to run a Sophon Premium Node? | Duration (Months) | Discount (%) | 1–20 Keys $ (per m) cost | 21–40 Keys $ (per m) cost | 41–60 Keys $ (per m) cost | 61–80 Keys $ (per m) cost | 81–100 Keys $ (per m) cost | 100+ Keys $ (per m) cost | 200+ Keys $ (per m) cost | |-------------------|--------------|----------------------------|-----------------------------|-----------------------------|-----------------------------|------------------------------|---------------------------|----------------------------| | 1 | NA | (7.50) 7.50 | (9.38) 9.38 | (11.25) 11.25 | (15) 15 | (18.75) 18.75 | (37.50) 37.50 | (75) 75 | | 3 | 5% | (7.13) 21.38 | (8.91) 26.72 | (10.69) 32.06 | (14.25) 42.75 | (17.81) 53.44 | (35.63) 106.88 | (71.25) 213.75 | | 6 | 10% | (6.75) 40.50 | (8.44) 50.63 | (10.13) 60.75 | (13.50) 81 | (16.88) 101.25 | (33.75) 202.50 | (67.50) 405 | | 12 | 20% | (6) 72 | (7.50) 90 | (9) 108 | (12) 144 | (15) 180 | (30) 360 | (60) 720 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Reach out on Discord if you need further assistance - Learn more from the [Sophon documentation](https://docs.sophon.xyz/welcome) --- ### Sophon > How to Run Your Sophon Node | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/sophon [Sophon](https://ai.sophon.xyz/) supports autonomous AI agents to build an agentic economy with funding, GPU credits, and scaled infrastructure. As Sophon grows it intends to expand beyond DeFi into gaming, social interactions, and new forms of entertainment. > **Warning: ⏳ Deadline to Delegate Your Sophon Nodes: January 15th 2025.** ### Why Delegate Sophon Nodes? Delegating Sophon Nodes is a crucial step for the Sophon use cases. By delegating, you: - Support blockchain scalability and infrastructure. - Earn rewards, including Node Points (NPs) and other benefits. - Join a growing network of contributors powering decentralized technologies. By participating in the NodeOps Testnet campaign, you not only support the Sophon ecosystem but also earn additional Node Points (NPs) as rewards. ### Important Deadline Make sure to complete your delegation before this date to ensure your Nodes are active and eligible for rewards. Don't miss out on this opportunity to participate and contribute to the ecosystem! Welcome to the comprehensive guide for delegating Sophon Nodes on the NodeOps and NodeOps Network platform. Whether you are using the [Premium Model](./premium.mdx) or the [Commission-Based Model](commission.mdx) on NodeOps Console, this documentation will provide step-by-step instructions to ensure a smooth delegation process. ### Available Delegation Models #### 1. Sophon Premium Model A tailored approach for enhanced performance and rewards. Ideal for users looking for a seamless and straightforward delegation experience. #### 2. Sophon Commission-Based Model via NodeOps Network Testnet Participate in a commission-based structure while earning additional Node Points (NPs) through the NodeOps Network Testnet campaign. ### Get Started Today Follow the guides provided in this documentation to delegate your Sophon Nodes and join the NodeOps community in shaping the future of decentralized infrastructure. For any questions or assistance, refer to our support resources or contact us directly. ### FAQ 1. I don't have an NFT, but I deployed a node. Does that mean the Node I paid to deploy has no actual use? β€”> While you need an NFT to deploy a node, your current plan creates a burner wallet that can accept delegations at a set commission rate. Since this burner wallet is associated with NodeOps, you can earn commissions. You can share this burner wallet with Sophon Node holders to earn these commissions. 2. What is commission based model and premium model? β€”> a. Premium: With this subscription model, you pay for Node operations but keep all your rewards. You can also let users delegate to your Node and set your preferred commission rate for license holders who delegate to you. b. Commision-based model: This model has no monthly subscription fees. Instead, NodeOps takes 1% of your rewards to cover Node operation costs. You keep the remaining 99% of your reward tokens, while 1% goes to NodeOps. 3. What is the Pricing for Sophon Premium? | Duration (In Months) | Discounts | 1-20 Keys | 21-40 Keys | 41-60 Keys | 61-80 Keys | 81-100 Keys | | ------------------------ | ------------- | ------------- | -------------- | -------------- | -------------- | --------------- | | 1 | NA | 15 | 18.75 | 22.5 | 30 | 37.5 | | 3 | 5% | 42.75 | 53.4375 | 64.125 | 85.5 | 106.875 | | 6 | 10% | 81 | 101.25 | 121.5 | 162 | 202.5 | | 12 | 20% | 144 | 180 | 216 | 288 | 360 | 4. What is the Commission percentage that NodeOps would charge for Commission-Based model? β€”> NodeOps charge 1% for Sophon Commission-Based Node Delegation and there is no monthly upfront fee 5. I don't have a Sophon NFT but someone delegate their Nodes to my NodeOps operator wallet after buying a premium subscription, where can I see my reward and do i need kyc to receive the reward? β€”> You can check it on Sophon Dashboard and incase Sophon asks for KYC, you will have to do it, since we don't support the prerequisites but only Node running, it would be the best to check with Sophon team for the KYC. --- ### Vemp Horizon > VEMP Horizon Node Bootstrapping Event | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/vemp-horizon [Vemp Horizon](https://www.vemp.xyz/) Horizon is a specialist blockchain rollup for community centric on-chain gaming. For most small game developers, incorporating on-chain assets into their games is often hindered by high gas fees, limited Ethereum Virtual Machine (EVM) compatibility, and a lack of developer-friendly tools. VEMP Horizon eliminates these challenges, providing a seamless way to integrate on-chain assets and economies into any game design. At the heart of VEMP Horizon's success is its rapidly growing decentralized network of Nodes. These Nodes play a crucial role in powering the network, ensuring all transactions are verified and processed accurately. Their decentralized architecture not only prevents slowdowns and bottlenecks but also guarantees smooth and efficient network operations. Beyond transaction processing, these Nodes are vigilant in identifying and resolving issues, including safeguarding against malicious activities like hacking attempts. This ensures the network remains secure, protecting sensitive data while supporting developers in creating cutting-edge on-chain gaming experiences. ## Prerequisites - EVM-compatible wallet - Vemp Horizon NFT - Sufficient funds or credits for your Node subscription ## Participate in the Node Bootstrapping Event with Your Vemp Horizon Node Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node 1. Navigate to the [Node Bootstrapping Event Page](https://console.nodeops.network/bootstrap-event) on the left side menu and select **Vemp Horizon**. ### Step 3: Set up your Node subscription Connect an EVM-compatible wallet to your account. This wallet will store your Vemp Horizon NFT. 1. Select Nodes and Deployment Options Choose the number of Nodes you'd like to purchase and select one of the following deployment options: - a. Purchase and Deploy: Let us handle all Node operations, including monitoring, updates, and maintenance. This option eliminates technical complexities. - b. Purchase Only: If you prefer to manage and operate the Node independently, select this option. Note: If choosing Option a, specify the desired duration for Node operation. 2. (Optional) Apply Promo Code If you have a promo code, enter it in the designated field and click Apply. You can also redeem NodePoints or any discount codes at this stage. After finalizing your choices, click Continue to Pay to proceed. 3. Complete Payment Click Pay to initiate the payment process. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 4: (Optional) Verify your deployment 1. Delegate Your Node After successful payment, you'll be redirected to Nodefolio. A unique Node will be created for you. To delegate your node: - Click **Click to Delegate**. - Connect the same wallet containing your Vemp Horizon NFT used for the purchase. 2. Confirm Setup Once delegation is complete, your Node will begin running. Return to Nodefolio to verify the node's status. It will change from Click to Delegate to Running. ## FAQ - What are the Prices to run the Nodes? | Duration | Discounts | Per license | | -------- | --------- | ----------- | | 1 | NA | 15 | | 3 | 5% | 14.25 | | 6 | 10% | 13.5 | | 12 | 20% | 12 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: - How do I delegate? > In order to run your Nodes, you need to delegate your licences to your wallet running the Nodes. Head to our delegation site [delegate.vemp.xyz](http://delegate.vemp.xyz/). - Type of Node? > Horizon Nodes - How to delegate? > In order to run your Nodes, you need to delegate your licences to your wallet running the Nodes. Head to our delegation site [delegate.vemp.xyz](http://delegate.vemp.xyz/), enter the wallet to delegate your licences too, click the Delegate button, completing the transaction. - Type of Node? > Horizon Node - Approx how many rewards does the user receive per day? > There are a total of 180 million VEMP as Node rewards. More information on the emissions schedule can be found at [https://docs.vemp.xyz](https://docs.vemp.xyz/) - Is there any KYC required for claiming the rewards or at any step? > No KYC is required to purchase or run the Horizon Nodes. - Is there an option to buy the native tokens, except earning from the rewards? > VEMP can be bought on Arbitrum, and bridged over to Horizon. The Arbitrum contract address is 0xaF7E3F16D747e77E927dc94287f86eb95a64d83D.[Access the bridge](https://vemp-horizon.bridge.caldera.xyz/). ## What next? - Reach out on Discord if you need further assistance - Learn more from the [Vemp Horizon docs](https://docs.vemp.xyz/) --- ### XAI > XAI Sentry Nodes | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/xai # XAI NodeOps streamlines the deployment and monitoring of [XAI](https://x.com/xai_games) Sentry Nodes into a few simple steps. Sentry Key holders benefit from automatic upgrades and enhanced uptime with zero additional Cloud subscription costs. ## Prerequisites - EVM-compatible wallet - Sufficient funds or credits for your Node subscription ## Run your Xai Sentry Nodes with NodeOps Console Use the walkthrough to understand how to set up and deploy your Nodes. Choose from two options: 1. [Basic Plan ](xai.md#option-1-basic-plan) 2. [Premium Plan (Dedicated Sentry Operator)](xai.md#option-2-premium-plan) ## Option 1 Basic Plan ### Step 1: Sign up to NodeOps * Log in or sign up at [NodeOps Console](https://console.nodeops.network) * Connect your Wallet * Verify If Sentry Key is Found or Not ### Step 2: Pay the maintenance fee * Select the XAI Node on the dashboard * Connect the wallet holding Sentry Keys (If you want to purchase one, go to: [https://sentry.xai.games/](https://sentry.xai.games/)) Note: Use Code - "IF-GAMES" to redeem 5% Off on your Sentry Node Purchase * Once Sentry Keys are verified, select the number of months and process the payment > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). #### Step 3: Assign Sentry Key Before deploying, you have to assign NodeOps as your Node operator. This requires a signature verification from your wallet and you have to pay a small gas fee. Note: While you assign NodeOps as your Node operator, there won't be any exposure to your private keys and Sentry Keys remain non-transferable. ### Step 4: Deploy the XAI Node & Verify if it is running Once you have assigned a Sentry Key, you'll be redirected to the Xai client interface given below. Click on **Deploy** and wait for a couple of minutes for successful deployment. ### Step 5: Check Node status & Logs Your Node is deployed successfully as the status changes from pending to running. You can see your balance and accrued rewards in this Xai client. ## Option 2 Premium Plan The Basic Plan Consists of a shared Sentry Operator. Via Premium Plan, you get a Dedicated Sentry Operator thus giving much more reliability and control over your Nodes powered by NodeOps. Here is how to subscribe to the premium plan for XAI: Step 1 - Sign in to [NodeOps Console](https://console.nodeops.network) Step 2 - Select XAI Premium, Connect your wallet holding the Sentry Keys Step 3 - Verify the Keys Step 4 - Subscribe via your desired plan Step 5 - Assign your keys/wallet to the Sentry Operator Step 6 - Fund your Sentry Operator Wallet with at least 0.011 ETH on Arbitrium. You'll be given an option to fund the wallet. Step 7 - Restart your Node and you are all set. ## FAQ - What's the subscription cost? | Duration (Months) | 1–100 Keys $ (per m) cost | 101–200 Keys $ (per m) cost | 201–300 Keys $ (per m) cost | 301–400 Keys $ (per m) cost | 400+ Keys $ (per m) cost | 500+ Keys $ (per m) cost | |-------------------|---------------------------|-----------------------------|-----------------------------|----------------------------|---------------------------|---------------------------| | 1 | (15.00) 15.00 | (18.75) 18.75 | (22.50) 22.50 | (26.25) 26.25 | (30.00) 30.00 | (37.50) 37.50 | | 3 | (14.25) 42.75 | (17.81) 53.44 | (21.38) 64.13 | (24.94) 74.81 | (28.50) 85.50 | (35.63) 106.88 | | 6 | (13.50) 81.00 | (16.88) 101.25 | (20.25) 121.50 | (23.63) 141.75 | (27.00) 162.00 | (33.75) 202.50 | | 12 | (12.75) 153.00 | (15.94) 191.25 | (19.13) 229.50 | (22.31) 267.75 | (25.50) 306.00 | (31.88) 382.50 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: ## What next? - Ensure that your Sentry Operator Wallet Assigned always consists of sufficient balance for claiming the rewards & submitting the assertions. It is recommended to keep at least $10 worth of ETH. - You Can Now Connect All of your multiple Wallets to A Singular Email for Better Visibility. - For Existing users, to update from Basic to Premium, you can head over to My Plan & Upgrade to Premium. - Reach out on Discord if you need further assistance - Learn more from the [Xai Network docs](https://xai-foundation.gitbook.io/xai-network) --- ### XProtocol > XProtocol Xardian Node Delegation Guide | Powered by NodeOps URL: https://docs.nodeops.network/Guides/Console/Managed-Nodes/xprotocol [XProtocol](https://xprotocol.org/) is an Entertainment-focused DePIN Superchain. Built on [Base](https://www.base.org/), a Layer 2. XProtocol aims to redefine the digital entertainment landscape by leveraging Superchain technology to create a dynamic, value-driven environment for the mass audience. Xardian Nodes are integral to the XProtocol ecosystem, designed for early supporters to secure the network and earn $KICK rewards. By operating a node, participants enhance the decentralized governance and security of the XProtocol network. ## Prerequisite - EVM-compatible wallet - Sufficient funds or credits for your Node subscription - a Xardian Node license (NFT) to proceed > **Tip: Acquire a [Xardian Node license](https://xprotocol.org/node-sales)** ## Run your XProtocol Xardian Nodes with NodeOps Console Use the video or walkthrough to understand how to set up and deploy your Nodes. ### Step 1: Connect with the Console 1. From the [Console](https://console.nodeops.network), sign up or log in using the **Log In** button; bottom left of the Console. **Show me** 2. Choose your sign in method: - Wallet/Email/Social **Show me sign in methods** Use the tabs to learn more: To sign in with an EVM-compatible wallet, you must approve the connection request in your Wallet. Click **Connect** and **Confirm** the request. **Show me** Sign in with Email and connect a wallet later. **Show me** Sign in with Google and connect a wallet later. **Show me** ### Step 2: Select your Protocol and Node 1. Navigate to **Node Deployment** on the left side menu and select **XProtocol**. 2. Update the **Quantity** to determine how many Nodes to deploy. 3. Review the details and confirm your selection. ### Step 3: Set up your Node subscription 1. Select **Xardian** for the Node type 2. Click **Connect Wallet** to link your wallet containing the "Xardian Node NFT." Once connected, select "Fetch NFT," and the system will automatically retrieve and display the number of NFTs associated with your wallet. 3. Select your subscription duration The longer your subscription, the lower your monthly cost. If you have NodePoints, you can redeem them for a discount, and if you have a discount code, you can apply it here as well. After selecting your subscription and optionally applying your NodePoints and/or discount code, click "Continue to Pay" to proceed with payment. > [Learn more about payment options](/Get-Started/Pay-for-Services/Readme.mdx). ### Step 4: Delegate licence 1. Initiate the Node delegation: After completing your payment, you will be redirected to Nodefolio. You will notice the newly deployed Node marked with an "Action Required" status. To proceed, click on β€œClick to Delegate” to start the delegation process. 2. Complete the delegation: A pop-up window will appear, automatically loading your wallet address and displaying the NFTs associated with it. Click on β€œClick to Delegate” again to complete the delegation process, then confirm the transaction in your wallet. Since the transaction occurs on the Base Blockchain, a small gas fee may be required. Once successful, a transaction hash will be displayed as confirmation Congratulations! Your XProtocol Xardian Node is now fully set up. Go back to Nodefolio to verify the status of your node, which should update from β€œClick to Delegate” to β€œRunning.” ## FAQ - Pricing | Duration (In Months) | Price Per Wallet (In USD) | Total Price (In USD) | | -------------------- | ------------------------- | -------------------- | | 1 | 25.00 | 25 | | 3 | 23.75 | 71.25 | | 6 | 22.50 | 135 | | 12 | 20.00 | 240 | | 24 | 18.75 | 450 | | 36 | 17.50 | 630 | - Do I need to upgrade my Node/s on my own? > No, NodeOps automates deployments and upgrades. - How do I pay for subscriptions? Pay with [fiat, stables, or tokens](../Get-Started/Pay-for-Services/Readme.mdx) via our payment partner, Copperx: - Which network are they going live on? > Base ## What next? - Reach out on Discord if you need further assistance --- ### Console | Node services > Deploy and manage blockchain Nodes with NodeOps Console. Launch Node-as-a-Service subscriptions or delegate NFT licenses with no manual setup. URL: https://docs.nodeops.network/Guides/Console With NodeOps Console, you can launch and maintain Blockchain or Protocol Nodes in seconds. No manual setup needed, no steep learning curve. Choose from: - [Paying a subscription to run a Node](/Get-Started/Console/subscription), or - [Delegating an NFT license to NodeOps](/Get-Started/Console/commission-based) who will take a commission to run the Node Alternatively, you can lock supported NFT licenses into a vault to immediately [extract liquidity](/Get-Started/DeFi-Services/liquidity). ## Simplified Node running [NodeOps Console](https://console.nodeops.network/) revolutionizes Web3 infrastructure by offering Node-as-a-Service (NaaS): simplifying Node operations for everyone, whether you're a technical expert or completely new to blockchain technology. Our mission is to remove the complexities of Node running, enabling anyone to set up and maintain blockchain and Protocol Nodes for the following Protocols with just a few clicks. > **Tip: Use the Console's [Get Started](/Get-Started/Console/README.md) to understand how to use the dashboard or jump straight into the guides below.** ## NodeOps-supported Protocols | Protocol | Keys or license required | NFT delegation supported | |--------------------------|--------------------|--------------------| | [Aethir](/Guides/Console/Managed-Nodes/aethir.mdx) |Y| | | [Avail](/Guides/Console/Managed-Nodes/avail.mdx) |N | | | [Beam](/Guides/Console/Managed-Nodes/beam.mdx) |Y|| | [CARV](/Guides/Console/Managed-Nodes/carv.mdx) |Y | [Y](/Guides/Console/Managed-Nodes/carv#carv-commission-model)| | [Celestia](/Guides/Console/Managed-Nodes/celestia.mdx) |N | | | [Captain & Company](/Guides/Console/Managed-Nodes/capnco.mdx)|Y | | | [DIN](/Guides/Console/Managed-Nodes/din.mdx) |Y | | | [Fuse](/Guides/Console/Managed-Nodes/fuse.mdx) |Y | | | [Huddle01](/Guides/Console/Managed-Nodes/huddle01.md) |Y | | | [Hybrid](/Guides/Console/Managed-Nodes/hybrid.md) |Y | | | [Hychain](/Guides/Console/Managed-Nodes/hychain.md) |Y | | | [iAgent](/Guides/Console/Managed-Nodes/iagent/bootstrapping.md)|Y| | | [KIP](/Guides/Console/Managed-Nodes/kip.md) |Y | | | [Lumoz](/Guides/Console/Managed-Nodes/lumoz.md) |Y | | | [Nexus](/Guides/Console/Managed-Nodes/nexus.md) |N | | | [0G](/Guides/Console/Managed-Nodes/og-alignment.md) |Y | [Y](/Guides/Console/Managed-Nodes/og-alignment#delegate-your-0g-alignment-nft-to-earn-commission)| | [OpenPad](/Guides/Console/Managed-Nodes/openpad.md) |Y | | | [PlayAI](/Guides/Console/Managed-Nodes/playai.md) |Y | | | [Rivalz](/Guides/Console/Managed-Nodes/rivalz.md) |Y | | | [Sophon](/Guides/Console/Managed-Nodes/sophon/README.md) |Y| [Y](/Guides/Console/Managed-Nodes/sophon/commission)| | [Vemp Horizon](/Guides/Console/Managed-Nodes/vemp-horizon.md)|Y | | | [XAI](/Guides/Console/Managed-Nodes/xai.md) |Y |[Y](/Get-Started/Console/commission-based)| | [XProtocol](/Guides/Console/Managed-Nodes/xprotocol.md) |Y | | > **Tip: Use the links to follow the Protocol-specific guides as there are a range of Node running requirements, such as:** - Owning and delegating a licence - Bonding tokens to a Node - Owning the Protocol's tokens ## What next? - [Get Started](/Get-Started/Console/README.md) to understand how to use the Console to become a Node Runner - Familiarize yourself with Console's [Terms & Conditions](https://nodeops.network/terms) - Follow a specific guide for a [supported Protocol](#nodeops-supported-protocols) - Learn more about the [points](/Guides/Community-Incentives/points.md) awarded to Node Runners across the various campaigns --- ### Dockerize your App > Containerize your application with Docker for NodeOps Cloud Marketplace. Step-by-step guide to build, tag, and publish public Docker images. URL: https://docs.nodeops.network/Guides/Marketplace/Configure-Compute/public-docker > **Tip: TL;DR** Containerize your app to make it available via a **public** Docker link. This page details the process of containerizing your app and configuring your template ahead of [submitting the template](/Guides/Marketplace/Configure-Compute/upload-template.md) to enable it to be [deployed at-a-click](/Get-Started/Cloud-Infrastructure/deploy/) from [NodeOps Cloud Marketplace](/Learn/Products/Cloud/README.md), with video and step-by-step guides. ## Prerequisites - Unix environment - If required: enough bandwidth for Docker app download (>500 MB) - App to containerize > Or use our [starter app](https://github.com/NodeOps-app/Nodeops-Template-Example-App). ## Set up Docker ### Step 1. Set up locally If you have an existing account, skip to the next step. 1. Open the Docker app on your local machine, or download it at [docker.com/get-started](https://www.docker.com/get-started). **Show me steps** See full steps if download and setting up account: - Accept Ts&Cs - Use recommended settings - Enter system password - If required, create account ### Step 2. Create personal access token 1. [Signed in to Docker Hub](https://hub.docker.com/), navigate to your profile (top right), and click **Account Settings**. **Show me** 2. Click **Generate new token** and give your new Personal Access Token (PAT): - Description - Expiration - Read and write access **Show me** ### Step 3: Run Docker 1. With Docker Desktop running on your machine, open a terminal window and enter: ```bash docker login -u {your username} ``` 2. Respond to the terminal prompt for your Docker Hub PAT copied previously. ### Step 4. Containerize your app In order to publish a Docker image of your application, your app must have a Dockerfile. > A Dockerfile defines the blueprint to build your Docker image. It specifies the base image (such as, python:3.9 node:18), details how to install dependencies, specifies how to copy your app’s code into the image, and the command to run your application when the container starts. The Dockerfile specification for the [NodeOps Starter Template app](https://github.com/NodeOps-app/Nodeops-Template-Example-App) would, therefore, be: ```Dockerfile # Use Node.js LTS version FROM node:20-slim # Create app directory WORKDIR /usr/src/app # Copy package files COPY package*.json ./ # Install dependencies RUN npm install # Copy app source COPY . . # Expose the port the app runs on EXPOSE 3000 # Command to run the application CMD ["npm", "start"] ``` ### Step 5. Publish to Docker Hub 1. Logged in to Docker, create a Dockerfile in your app's root directory. Build the image with: ```bash docker build --platform linux/amd64 -t {yourusername/yourappname} . ``` > User cherrybloss who has developed the blossom app would run: > `docker build --platform linux/amd64 -t cherrybloss/blossom .` 2. Build and push the image to Docker Hub with: ```bash docker push your_username/template_name:version . --push --platform linux/amd64 ``` **Explain command** | Part | Meaning | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | `docker build` | Build a Docker image | | `-t your_username/template_name:version` | Tag the image (with your Docker Hub username, a name, and a version) | | `.` | Use the current directory (where the Dockerfile is) | | `--push` | Automatically **push the built image** to Docker Hub after it's built | | `--platform linux/amd64` | Build the image for the **[Linux/AMD64 architecture](#gotchas)** (ensures compatibility on Cloud or Linux servers) | ## Gotchas Common reasons that templates fail the review stage is: - The [Docker image](/Learn/Glossary/docker-image) is private - The [Docker tag for architecture is incorrect](/Reference/template-schema#architecture-tags) ## What next? - Call your Docker image [from a template](/Guides/Marketplace/Configure-Compute/upload-template) - [Submit the template](/Guides/Marketplace/Configure-Compute/upload-template) to NodeOps Cloud Marketplace - [Learn about the Template schema](/Reference/template-schema.md) - Update your Docker image: --- ### Templates > Create and configure templates for NodeOps Cloud Marketplace. Define infrastructure, apps, and services using Docker images and YAML specs. URL: https://docs.nodeops.network/Guides/Marketplace/Configure-Compute 🌟 Status: Live on Mainnet > **Tip: TL;DR** Templates allow builders to consume [NodeOps Cloud Compute](/Learn/Products/Cloud/README.md) or offer apps and services to end users from the [Template Marketplace](https://cloud.nodeops.network/). - Templates define Cloud infra, apps, and services - Templates may be kept private or submitted to be considered for listing as a public template in the Cloud Marketplace To consume your own template that leverages a bespoke app you must: - Create a [public Docker image](./public-docker.md) of the app - Create a template that leverages that Docker and [upload it](./upload-template.md) to the Marketplace > **Info: Monetize your templates** In the boostrapping phase of the Network, templates earn 20% of the workload fee. > This allows early template contributors to enjoy a significant incentive should their template prove popular. ## Template specification overview | Specification| Description| Example| Allowable Values | |-------------|------------|--------|------------------| | Docker Image| Specifies the public Docker image used for deployment.| [`nginx:latest`](/Reference/template-schema#example-nginx-template)| Valid [Docker image tags](/Reference/template-schema#architecture-tags) (`name:tag`) for [arch amd64](/Learn/Glossary/cpu-architecture)| | Resource Allocation| Defines `cpu` and `memory` resources allocated to the application.| [`cpu: "500m" memory: "128Mi"`](/Reference/template-schema#example-nginx-template)| CPU (`m` for milli-cores), Memory (`Mi`) | | Environment Variables| Configures environment variables, including placeholders and defaults.| [`env: - name: APP_ENV value: "{{.ENV}}" default: development`](/Reference/template-schema#example-protocol-node-template)| Dynamic (`{{.ENV}}`), Static values | | Internet Exposure| Indicates whether the application should be accessible publicly.| [`expose: true`](/Reference/template-schema#example-protocol-node-template)| `true`, `false` | The template structure is versatile to accommodate all your use cases, use the drop down to learn more: ****Show me the YAML definition**** [See examples and further details](/Reference/template-schema) This means there are few boundaries constraining what you may create and consume from the Cloud Marketplace. Templates state their resource requirements, currently, apps and code may be called via a public Docker image. > 🚧 NodeOps is developing alternative methods for you to set up templates. ## Template constraints > **Important: Template constraints** 1. Maximum of 5 **services**. 2. Only one service per template can be exposed to the public. 3. Only 1 persistent volume is allowed. 4. The total resource usage is limited to **4 Compute Units (CUs)** > calculated as: CU = max(total CPU, total Memory) 5. Upon template interruption, **all** services will be restarted as part of a single pod with multiple containers. ## Update your Docker image To push out an updated version of your NodeOps template, push a new tag to your Docker image with the command: `docker push {username}/{template)name}:tagname` Then, from the NodeOps Marketplace console, navigate to **My Templates** and select your template, update the YAML version number and submit for re-review. ## FAQ - If I make my template public on the Marketplace, does its code and configuration become public? No. Even though the Docker image is public, that doesn't mean that Docker exposes its code. Furthermore, [you decide whether the YAML file that configures you template is made public or hidden](/Guides/Marketplace/Configure-Compute/upload-template#3-set-privacy-levels). This means you may also keep hidden what Docker image you leverage. ## What next? - Learn how to [Dockerize your App](/Guides/Marketplace/Configure-Compute/public-docker) ahead of creating a template - Follow the Guide to [upload a template](/Guides/Marketplace/Configure-Compute/upload-template) to the Marketplace - Learn more about the other [products and services in the NodeOps Ecosystem](/Core-Services#product-and-services) --- ### Upload template > Upload and submit templates to NodeOps Cloud Marketplace. Create public or private templates, set privacy levels, and test deployments. URL: https://docs.nodeops.network/Guides/Marketplace/Configure-Compute/upload-template ## TL;DR - Prepare template for a working app, agent, or an environment or infrastructure configuration - Upload template - Submit for review for entry on the Cloud Marketplace or publish privately > [Provide an email](/Guides/Marketplace/marketplace-account#register-your-email) to receive outcome of a review. > **Info: Deploy templates at-a-click** Before creating templates, consider [understanding how users consume templates](/Get-Started/Cloud-Infrastructure/deploy) from the Marketplace. ## Prerequisites - [NodeOps Marketplace account](https://cloud.nodeops.network/) - Published [public Docker image of your application](/Guides/Marketplace/Configure-Compute/public-docker.md) > **Tip: Public or private?** Decide whether you wish to keep your templates private for personal use, or attempt to monetize them and make them publicly available. ## Submit a public template to the Marketplace ### Step 1: Become a contributor To submit a template to the Marketplace, when logged into the [Cloud Marketplace](https://cloud.nodeops.network/), navigate to **My Templates** and complete the form to become an allowlisted template contributor. **Show me** ### Step 2: Define your template 1. From **My Templates** click **Create Template**. **Show me** 2. Set up template metadata. | Required | |Optional | |--------------------------|-|-----------------------| | Thumbnail image | |Tutorial link | | Template name | |GitHub URL | | Template description | |Socials | | Category | | - X | | Template overview | | - Telegram | | Use cases | | | **Show me** #### 3. Set privacy levels > ⚠️ This step should move to the next page. Use the toggle to determine: - Whether template will be public or private - Whether the YAML file should be private **Show me** 4. Either use the YAML editor provided to define your Cloud Infrastructure or upload an existing file. **Show me** > See the [template schema](/Reference/template-schema.md) which shows examples to understand the template structure further. > **Tip: You may want to save a draft and [test your deployment](/Guides/Marketplace/Configure-Compute/upload-template#optional-test-your-template-deployment) ahead of sending the template for review.** 5. Submit the resource for review by clicking **Send For Review** Verification takes 2-3 days. If it's approved, your template becomes available in the Marketplace. > To receive an email alert, ensure you have [linked an email](/Guides/Marketplace/marketplace-account#register-your-email) to your Marketplace account. ## Create a Private template for personal use ### Step 1: Setup template metadata > Expect to carry out steps in flow required for public templates. This is because the tool is designed to populate the Marketplace, however, you are welcome to fly solo! 1. From the [Cloud Marketplace](https://cloud.nodeops.network), navigate to **My Templates** and complete the form. > This form is essentially redundant for private templates, however, if you never make your template public, this data remains unused. **Show me** 2. Set up template metadata. | Required | |Optional | |--------------------------|-|-----------------------| | Thumbnail image | |Tutorial link | | Template name | |GitHub URL | | Template description | |Socials | | Category | | - X | | Template overview | | - Telegram | | Use cases | | | > This metadata is essentially redundant for private templates, however, if you never make your template public, this data remains unused. **Show me** 3. Set privacy levels > ⚠️ This step should shortly move to the next page. Use the toggle to determine: - Whether template will be public or private - Whether the YAML file should be private **Show me** ### Step 2: Define your template 1 From **My Templates** click **Create Template**. **Show me** 2 Either use the YAML editor provided to define your Cloud Infrastructure or upload an existing file. **Show me** > See the [template schema](/Reference/template-schema). 3 Submit the resource to your profile by clicking **Send For Review**. ## (Optional) Test your template deployment Use the video or walkthrough to understand how to leverage your 3 free 10 minute deployments to test your templates. 1. Navigate to **My Templates** and select a **Draft** or **Under Review** template. **Show me** 2. Click to select a template that you want to test the deployment for. 3. Click **Deploy Preview**. **Show me** ## What next? - Understand more about [template schemas and constraints](/Reference/template-schema.md) - Before using a verified or community template, you may wish to [scan the resource for vulnerabilities](/Get-Started/Cloud-Tools/scan.md) - Learn about how playbooks assist you to [configure your Compute Infrastructure](/Learn/Products/Cloud/Cloud-Infrastructure/README.md) --- ### Farm Compute > Farm $NODE by renting machines on NodeOps Cloud Marketplace. Earn workload revenue share and boost rewards with UNO NFT Compute units. URL: https://docs.nodeops.network/Guides/Marketplace/farm 🌟 Status: Live on Mainnet In the bootstrapping phase of NodeOps Network, you can farm \$NODE by renting a Machine from the Cloud Marketplace and earning a share in its workload revenue. Each machine earns incentives: - Registration reward: Earn [gNODE](/Guides/Community-Incentives/points) for signing up and adding at least 1 machine that provides a minimum of 7 days of uptime - Availability reward: Earn [gNODE](/Guides/Community-Incentives/points) rewards for each machine that maintains service > **Tip: :::** > **Tip: Remember to top up with Arbitrum ETH. ** ## Prerequisites - Wallet with - β‰₯0.01 Arbitrum ETH - [Cloud Marketplace account](https://cloud.nodeops.network/) ## Rent a Machine from the Cloud Marketplace Use the walkthrough or video provided to rent a Machine from NodeOps Cloud Marketplace. **Show me video** 1. Logged in to the [Cloud Marketplace](https://cloud.nodeops.network/) > **Compute** > **+ Farm Compute**. **Show me** 2. Select **Rent Machine**, determine: - How many machines - Number of CUs and click **Continue**. **Show me** 3. Select duration in months and decide [how to pay](/Get-Started/Pay-for-Services#step-2-pay-for-a-subscription-or-service): - Available credits - Promo code - Payment partner and click **Deploy**. **Show me** Congratulations, once the Machine's status updates to active, you may click on it's name and view the monitoring logs. > Learn how to [assign workloads to this Machine](/Guides/Marketplace/Manage-Machines) to improve its yield ## UNO holders UNO holders are [eligible](/Guides/Community-Incentives/uno.mdx) for 2CUs per UNO. #### Claim your 2CUs per UNO 1. Connect your wallet with UNO NFT/s to the [Cloud Marketplace](https://cloud.nodeops.network/). 2. Click **Farm Compute** > You’ll see: "You're eligible for a 2CU machine". 3. Click **Continue**, then **Deploy**. Repeat these steps for each UNO NFT you hold. Remember to renew your machines. **Show me** ## What next? - [Add workloads to your own Machine/s](/Guides/Marketplace/Manage-Machines) to improve their yield - Share your wallet address or Machine's id to encourage others to leverage the Compute you Farm and increase your yield - If you have spare Compute, become a provider: [register the machine](/Get-Started/Cloud-Compute/Provide-Compute/README.md) to NodeOps Network's Cloud Marketplace and put it to work to earn \$NODE - Learn more about the NodeOps Ecosystem [core services](/Core-Services) - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) --- ### Machine statuses > Understand machine statuses on NodeOps Cloud Marketplace β€” active, pending, suspended, and more. Troubleshoot provided and rented Compute. URL: https://docs.nodeops.network/Guides/Marketplace/Manage-Machines/machine-status ## TL;DR - [Provided Machines](/Get-Started/Cloud-Compute/Provide-Compute/README.md) may occupy various states - [Rented Machines](/Get-Started/Cloud-Compute/rent-compute.md) have a different lifecycle > **Tip: Follow the [Get Started](/Get-Started/Cloud-Compute/Provide-Compute/README.md) to provide machines that you own or control.** This guide assists Compute providers to understand the status of their machines on the NodeOps Cloud Marketplace, and to undertake basic troubleshooting. ## Machine status Once you have [registered a machine](/Get-Started/Cloud-Compute/Provide-Compute/README.md) on NodeOps Network, you can log into the [Cloud Marketplace](https://cloud.nodeops.network/) and see the status of your machine/s. Status changes may be initiated by the provider or the Protocol: | Status | Description | Active party | |-------------------|-------------|-------| | Active | Once registered, machines capable of carrying workload move to the active state and are ready to carry workloads | Protocol-managed | | Awaiting Stake | In Testnet, follow the dummy staking flow by signing the required transaction in your wallet. In Mainnet, stake the required \$NODE | Provider | | Configuring| Installing necessary components| Protocol| | Deleted | Machines that have been deleted by the provider | Provider | |Deleting|Protocol is gracefully closing down workloads to prepare Machine for deletion|Protocol-managed| | Draining| Workloads being removed | Protocol| | Inactive | Machines that have been decommissioned by the provider | Provider | | Non-schedulable | Flagged machines liable to be suspended | Provider with failover to Suspended/Protocol-managed | | Pending | A temporary state while the Protocol ensures that the machine with the registered secret identifier complies with the [requirements](/Get-Started/Cloud-Compute/Provide-Compute/README.md#compute-requirements-for-machines-on-nodeops-cloud-marketplace). | Protocol-managed | | Suspended| Machines that fail to comply with the [requirements](/Get-Started/Cloud-Compute/Provide-Compute/README.md#compute-requirements-for-machines-on-nodeops-cloud-marketplace) | Protocol-managed | ## Rented Machines Consumers may rent entire Machines from the network. Renters can monitor the health of Machines. However, they don't have the same perspective over the Machine as the Provider. Notice that a Machine you rent has the **Occupied** label which differentiates it from any Machine that you [provide](/Get-Started/Cloud-Compute/Provide-Compute/README.md) to the Network. **Show me** ## What next? - Browse the [FAQ](/Learn/FAQ/provider.mdx) - If you lack the Compute resources, but want to have a try either: - Follow the guide to [Farm Compute](../farm.md) from the Marketplace - Follow the guide to [set up GCP Compute](../Provide-Compute/provide-gcp-compute.md) in the Marketplace --- ### Manage Machines > Assign and manage Compute workloads on NodeOps Cloud Marketplace. Set machine preferences, reschedule deployments, and designate providers. URL: https://docs.nodeops.network/Guides/Marketplace/Manage-Machines 🚧 Status: Coming soon > **Tip: TL;DR** On the NodeOps Network Cloud Compute Marketplace, you will be able to: - Set preferences for which Machine or Provider workloads are [auto assigned](#option-2-set-up-a-preferred-machine-or-provider) to - [Assign workloads by Machine or Provider identifiers](#option-1-assign-specific-workloads-to-designated-machines), use the tabs in the Guide to discover: - Reassigning existing workloads - Assigning a Machine or Provider for a new workload This guide assists you to specify which Machines have workloads deployed to them in the NodeOps Network Cloud Marketplace. ## Step 1: Collect the Machine or Provider identifier ### Option 1: Get an identifier from a Provider If someone else controls the Machine, they should provide you with one of the following: - Wallet address that controls the Machine - Name of the Machine - Name of the Provider Decide whether you want to assign a single workload to the specified Provider or Machine, or whether you want to specify a preference for future workloads to be auto assigned to that Provider or Machine. ### Option 2: Use your own resources #### Prerequisites - You are a [Provider](/Get-Started/Cloud-Compute/Provide-Compute/README.md) or a [Farmer](/Guides/Marketplace/farm.md) on NodeOps DePIN Cloud Marketplace Use your own Provider name, controlling wallet, or Machine Id for a specific Machine. To identify a specific Machine that you control: 1. Logged into your [Cloud Marketplace](https://cloud.nodeops.network/) account, navigate to the **Compute** page. **Show me** 2. Use the copy button to select the name of the Machine. **Show me** ## Step 2 Set up a preference ### Option 1: Assign specific workloads to designated Machines #### 2.1 Designate where workloads should run #### Prerequisites - [Machine or Provider Id](#step-1-collect-the-machine-or-provider-identifier) - Existing deployment Use the video or walkthrough to understand the steps to nominate an existing workload to a machine by its Id. **Show me video** 1. Navigate to **My deployments** and select the deployment to assign the workload for. **Show me** 2. From the chosen deployment's card, click **Reschedule**. **Show me** 3. Select **Custom** and click **Reschedule**. **Show me** 4. Enter the Machine Id copied in [Step 1](#option-2-use-your-own-resources), the Provider Id or the Provider wallet address into the search field. **Show me** 5. Click **Reschedule**. Congratulations, the deployment is being reassigned to the preferred Provider or Machine. #### Prerequisites - [Machine or Provider Id](#step-1-collect-the-machine-or-provider-identifier) - Sufficient funds for the deployment This guide walks you through assigning workloads to a machine at deployment, this increases the earning potential of that machine. When you select a Template to run, you are given the option to select the Provider or Machine to deploy your Template to. #### 2.2 Set up workloads and pay 1. Logged into the [Compute Marketplace](https://cloud.nodeops.network/), click **Deploy Templates** and select the template you wish to run. > Use the [Get Started](/Get-Started/Cloud-Infrastructure/deploy/) if you are unfamiliar with this flow. 2. Select **Custom** and search for the Machine/Provider to deploy the template's workload on. **Show me** > **Tip: If you select a wallet or Provider that rents/provides multiple Machines, you may choose from their pool of Machines.** 3. Accept the defaults or assign the min/max resource configuration to constrain the template's workload. 4. [Pay](/Get-Started/Pay-for-Services/Readme.mdx) and deploy. Congratulations: your template's workloads are assigned to your designated Provider or Machine. ### Option 2: Set up a preferred Machine or Provider #### Prerequisites Use the video to understand the steps to automate nominating a workload to a designated Machine or Provider. **Show me video** 1. Navigate to the [Profile page](https://console.nodeops.network/profile), click **Advanced Settings**, and click **Add New**. **Show me** 2. Enter the Machine Id copied in [Step 1](#step-1-collect-the-machine-or-provider-identifier) into the search field or search for the Provider by wallet address or Machine Id. Select the Machine/s or Provider you want to assign workloads by default from the filtered results and click **Save Preferences**. **Show me** Congratulations, now when you set up workloads you can auto assign your preference. ## What next? - Learn more about [NodeOps Network templates](/Learn/Products/Cloud/Cloud-Infrastructure/README.md) --- ### Troubleshoot Compute > Troubleshoot Compute issues on NodeOps Cloud Marketplace. Fix machine errors, resolve rejected machines, and debug common provider problems. URL: https://docs.nodeops.network/Guides/Marketplace/Manage-Machines/troubleshoot ## Troubleshooting Q. Can I check why my machine is not transitioning to active state? A. Yes. From the machine terminal, and run the following command to check if you're facing any issue or if you haven't met the requirements. ```shell journalctl -fu nn-provider* ``` ### Copy error An error such as `cannot create regular file '/usr/local/bin/nn-provider': Permission denied` means you didn't create a user account at root for NodeOps Cloud with the correct permissions to run the code. You can get around this on Ubuntu by downloading the script locally and then running these with `sudo`. That means: ``` curl -L | sh -s - ZxEsuA******************zAJ6 ``` becomes ``` curl -L -o nn-installer.sh chmod +x ./nn-installer.sh sudo sh nn-installer.sh ZxEsuA******************zAJ6 ``` ### Rejected machines Your machine will be rejected if: - It runs workloads in addition to the NodeOps Network assigned loads - If [SWAP](https://wiki.archlinux.org/title/Swap) is enabled ## What next? - Browse the [FAQ](../../../Learn/FAQ/provider.mdx) - If you lack the Compute resources, but want to have a try, follow the guide to [set up GCP Compute](../Provide-Compute/provide-gcp-compute.md) in the Marketplace --- ### Marketplace account > Manage your NodeOps Marketplace account β€” deploy templates, provide Compute, unbond $NODE, delete machines, view rewards, and redeem gNODE. URL: https://docs.nodeops.network/Guides/Marketplace/marketplace-account 🌟 Status: Live on Mainnet > **Note: From your account on the NodeOps Network Cloud Compute Marketplace, you can:** ##### Infra - [Deploy a template](/Get-Started/Cloud-Infrastructure/deploy) - [Delete a template deployment](#delete-a-deployment) ##### Compute - [Assign workloads to a machine](/Guides/Marketplace/Manage-Machines) - [Farm Compute on the Cloud Marketplace](/Guides/Marketplace/farm) - Renew rentals - Provide Compute to the Cloud Marketplace: - [Register as a provider and bond \$NODE](/Get-Started/Cloud-Compute/Provide-Compute/register-to-provide) - [Register Compute and bond \$NODE](/Get-Started/Cloud-Compute/Provide-Compute/register-a-machine) - Remove Compute from the Cloud Marketplace: - [Delete a Machine](#delete-compute-from-the-marketplace) - [Unbond \$NODE](#unbond-node) from Compute - View Machine details - Share Machine details ##### Profile - Create an account: - Log into an account - Log out of an account - Manage profile: - Add/edit [username](#username) - Register an [email](#register-your-email) - [Pay for services](/Get-Started/Pay-for-Services#payment-within-nodeops) - Rewards: - [View rewards](#view-rewards) - [Convert gNODE rewards to \$NODE](#redeem-gnode) and more ... ## Infra ### Delete a deployment #### Prerequisites - An active template deployed Use the video or walkthrough to delete a template deployed in the NodeOps DePIN Cloud Marketplace. **Show me video** 1. Logged into your [Marketplace account](https://cloud.nodeops.network/deployments), navigate to **My Deployments**. 2. Select the card for the instance you wish to delete, click the hamburger menu, and select **Remove**. **Show me** ## Manage profile ### Username 1. Logged into your [Marketplace account](https://cloud.nodeops.network/profile), navigate to your **Profile** to add or edit your username. ### Register your email 1. Logged into the [Marketplace](https://cloud.nodeops.network/profile), navigate to the **Profile** to add and register your email. 2. Click the edit icon and enter/update your email address. **Show me** ### Delete Compute from the Marketplace #### Prerequisites - An inactive machine registered to the Marketplace Use the video or walkthrough to delete Compute you provide to the NodeOps DePIN Cloud Marketplace. **Show me video** 1. Logged into your [Marketplace](https://cloud.nodeops.network/) account, navigate to the **Compute** page. **Show me** 2. Click the hamburger menu for the Machine you wish to delete and click **Delete**. **Show me** Don't forget to Unbond your \$NODE once it's released from the Machine. ### Unbond \$NODE #### Prerequisites - \$NODE [bonded to Compute](/Get-Started/Cloud-Compute/Provide-Compute/register-a-machine) becoming available - Arbitrum \$ETH for gas fee Use the video or walkthrough to unbond your \$NODE that was previously bound to Compute on NodeOps DePIN Cloud Marketplace. **Show me video** 1. Logged into your [Marketplace](https://cloud.nodeops.network/profile) account, navigate to your **Profile**. **Show me** 2. Click **Unbond** to start the release of available \$NODE. **Show me** 3. Confirm the spending cap and transaction in your wallet. 4. (Optional) Click **View All** to see the unbonding countdown. **Show me** > **Tip: The Protocol takes a period to fully release the bonded \$NODE.** ## Rewards ### View rewards #### Prerequisites - Existing account 1. Logged into your [Marketplace](https://cloud.nodeops.network/profile) account, navigate to your **Profile**. **Show me** 2. View your gNODE balance. **Show me** ### Redeem gNODE #### Prerequisites - Existing account that's earned gNODE 1. Logged into your [Marketplace](https://cloud.nodeops.network/profile) account, navigate to your **Profile**. **Show me** 2. Click **Claim**. **Show me** 3. Continue your claim in the [NodeOps Portal app](/Guides/Portal#redeem-gnode-with-nodeops-portal). ## What next? - Learn about the full set of [products and services](/Core-Services#product-and-services) offered across the NodeOps ecosystem - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) --- ### AnythingLLM > How to run AnythingLLM from the NodeOps Template Marketplace URL: https://docs.nodeops.network/Guides/Marketplace/Marketplace-Templates/anything-llm ## Overview AnythingLLM is a self-hosted app that, unlike general-purpose AIs served through public endpoints, you can configure it so that they data remains your own. ## Why Use NodeOps Cloud for AnythingLLM? - The NodeOps [AnythingLLM template](https://cloud.nodeops.network/marketplace/d0sq1m09p29s73eo974g) makes setup easy and scalable - NodeOps provides the cost-effective Compute your LLM model's needs (4–32 GB RAM is typical) - You can [leverage your own Machine](/Guides/Marketplace/Manage-Machines) as the server or those of trusted allies - You earn [gNODE](/Guides/Community-Incentives/points) when you participate in the NodeOps ecosystem > **Warning: The guide provides an LLM frontend hosted on NodeOps DePIN Cloud that sends request to the LLM provider's servers. Your [data security depends upon your key's settings](/Learn/Academy/API-Fundamentals/api-key-plus-data) and that of the NodeOps Machine. A forthcoming guide will explain how to connect that frontend to a LLM instance also hosted by you on NodeOps infrastructure.** ## Deploy AnythingLLM Use the video or walkthrough to understand how to deploy a frontend for AnythingLLM at-a-click with no setup overhead. ### Prerequisites - API Key for the AI model provider - A [Cloud Marketplace account](https://cloud.nodeops.network/) - Sufficient funds for the Compute 1. Use the [Cloud Compute Marketplace AnythingLLM link](https://cloud.nodeops.network/marketplace/d0sq1m09p29s73eo974g), or log in, navigate to **Template Marketplace**, and search for AnythingLLM. 2. Click **Deploy Template**, and select which Machine to run the workload on, or **Auto assign**. 3. Enter the API key, decide whether to leave CPU values as default or customize them, click **Next**. 4. Pay for the template deployment. You are now ready to chat with the LLM, upload documents, or customize the LLM. ## Use AnythingLLM 1. Logged into the [Cloud Marketplace](https://cloud.nodeops.network/deployments), navigate to **My Deployments**. 2. Click on the AnythingLLM card and click **Endpoints** for your instance's URL. 3. Click **Get Started** and choose the LLM model for which you provided the key. 4. Follow the rest of the prompts. You can now customize your LLM settings, upload documents, and start interacting with the AI. ## Troubleshooting - If your app crashes, consider increasing CPU/memory values - For delayed deployments, contact the NodeOps support team with your workload name ## What next? - Access your app - Monitor your deployment - Manage your instance --- ### Dria Testnet (GPU) > How to run a Dria Testnet (GPU) Node from the NodeOps Template Marketplace URL: https://docs.nodeops.network/Guides/Marketplace/Marketplace-Templates/dria-testnet-gpu ## Overview [Dria](https://dria.co) is a decentralized AI compute network where thousands of agents collaborate to generate and validate synthetic data, enhancing AI and machine learning models. Each Compute Node in the Dria network performs computational tasks that power this ecosystem β€” from simple mathematical operations to complex reasoning using large language models (LLMs). The GPU-powered Dria Compute Node delivers high-performance model inference and validation using powerful GPUs and a range of advanced open-weight LLMs. Running your node with GPU capability and multiple models increases your chance of receiving more tasks and rewards, as the Dria scheduler prioritizes nodes with diverse model availability. ## Why run a Dria Testnet (GPU) Node? - Flexible, powerful infrastructure for AI agents tailored to your domain and performance needs - Earn Dria rewards for operating Nodes - Control your own Node instances - Access to your own AI agent interface hosted on a Node you control: own your own data - Earn [gNODE](/Guides/Community-Incentives/points) when you participate in the NodeOps ecosystem > **Tip: Skip the technical headaches β€” with NodeOps templates, you can instantly deploy Nodes and start contributing to Dria. Join the network, support decentralization, and unlock the opportunity to earn token incentives directly from Dria.** ⚠️ Disclaimer: NodeOps does not control or guarantee rewards. Incentives, if any, are issued solely by Dria based on their rules. ## Deploy a Dria Testnet (GPU) Node on NodeOps DePIN Cloud Use the video or walkthrough to understand how to deploy and operate a Dria Testnet (GPU) Node at-a-click with no setup overhead. ### Prerequisites - Sufficient funds for the GPU deployment ### Step 1: Create the deployment 1. Follow [Cloud.NodeOps.Network/Marketplace/dria-testnet-computenode](https://cloud.nodeops.network/marketplace/dria-testnet-computenode), or [log in](https://cloud.nodeops.network/) and navigate to the **Template Marketplace**, and search for **Dria Testnet (GPU)**. > You can filter by **GPU** and other filters on the right hand side of the dash to refine the search set. 2. Click **Deploy Template**, and select: - GPU type - Plan (7-day or 30-day) **GPU options** - RTX 3090 - Released 2020 - Architecture: Ampere - Perfomance: High VRAM (24 GB GDDR6X), strong 4K performance, well-suited for creative workloads - Features: Offers exceptional rendering and AI capability - RTX 4090 - October 2022 - Architecture: Ada Lovelace, using TSMC 4N process - Performance: Offers 50% to 100% better performance than the RTX 3090 across benchmarks, creative workloads, and 4K gaming - Features: Superior ray-tracing, DLSS 3, more CUDA/Tensor/RT cores, significantly improved efficiency - RTX 5090 - Q1 2025 - Architecture: Blackwell (RTX 50-series) - Performance: Upgraded core counts: ~21,760 CUDA cores vs. 16,384 on the 4090. VRAM: 32 GB GDDR7 on a 512-bit bus, offering significant bandwidth boost > RTX 5090 comparison: > - Compared to RTX 4090: ~27–35% average performance improvement in gaming and AI workloads [source](https://www.corsair.com/us/en/explorer/gamer/gaming-pcs/rtx-5090-vs-4090-whats-the-difference/) > - Compared to RTX 3090: Massive leap in performanceβ€”benchmarks show 69–97% higher FPS across resolutions [source](https://www.club386.com/nvidia-geforce-rtx-5090-vs-rtx-3090/) 3. Click **Next**, complete payment, and click **Deploy**. ### Step 2: Monitor Node with Dria Testnet 1. **After deploying your Dria Compute Node**, retrieve your **private key** from the **NodeOps Cloud deployment page** and import it into your preferred Web3 wallet, such as **MetaMask** or **Rabby** 2. Open [Dria Node](https://dria.co/edge-ai/my-node) and **connect the imported wallet**. 3. Once connected, you can **view your node’s activity status, completed tasks, and reward progress** directly from the Dria dashboard. 4. If your node shows as **INACTIVE**, it’s simply waiting for the next assigned task. It will automatically switch to **ACTIVE** once it begins processing a task ### Step 3: How to Earn Rewards - **Completed Tasks** – Each successful workflow your node completes (generation, validation, or computation) adds to your reward balance. - **Model Diversity & Performance** – GPU nodes running multiple high-performance models (like **llama3**, **gemma3**, **qwen3**, **mistral-nemo**) are prioritized for more workflows, leading to higher rewards. 1. Rewards are sent **directly to your connected wallet** and distributed periodically based on Dria’s **on-chain reward system**. 2. You will be **eligible for rewards only if your node ranks within the top 50% of provers**. 3. It may take some time to start earning rewards as your performance score improves and your ranking changes. 4. Please keep your node running continuously until you become eligible for rewards. ### Tips to Maximize Rewards - Keep your node running **24/7**. - Follow official announcements in the **Dria Discord** for reward and network updates. ### (Optional) Step 4: Monitor Node deployments - Monitor a Node deployment: - From [NodeOps Cloud Marketplace](https://cloud.nodeops.network/), navigate to the **My Deployments** page and select the Node instance you want to monitor - From [Dria](https://dria.co/edge-ai/my-node), sign in with the same wallet you imported from NodeOps Cloud, and navigate to the **My Nodes** page ## Gotchas - After deploying your Node, **wait a little while** before checking its status. - This is because the node will begin **downloading the required models**, and it may take some time for this to be reflected on your **My Node** page on Dria. - Once you start seeing logs similar to the example shown below, it means your node has **finished downloading the models**, is now **active**, **earning points**, and you can also check **which top percentage category** your node currently ranks in. **Show me** ## What next? - Check out [Dria's documentation](https://node-guide.dria.co/introduction) for more info about rewards distribution --- ### GaiaNet > How to run a GaiaNet Mainnet Node from the NodeOps Template Marketplace URL: https://docs.nodeops.network/Guides/Marketplace/Marketplace-Templates/gaia-mainnet ## Overview [GaiaNet](https://www.gaianet.ai) is a decentralized ecosystem supporting AI applications that learn, improve, and grow over time. GiaNet's' decentralized computing infrastructure enables individuals and businesses to create, deploy, scale, and monetize their own AI services using proprietary data. GPU-based Gaia Nodes are fully-featured AI agent servers optimized for high performance. ## Why run a GaiaNet Mainnet GPU Node? - Flexible, powerful infrastructure for AI agents tailored to your domain and performance needs - Earn Gaia rewards for operating Nodes - Control your own Node instances - Access to your own AI agent interface hosted on a Node you control: own your own data - Earn [gNODE](/Guides/Community-Incentives/points) when you participate in the NodeOps ecosystem > **Tip: Skip the technical headaches β€” with NodeOps templates, you can instantly deploy Nodes and start contributing to GaiaNet. Join the network, support decentralization, and unlock the opportunity to earn token incentives directly from GaiaNet.** ⚠️ Disclaimer: NodeOps does not control or guarantee rewards. Incentives, if any, are issued solely by GaiaNet based on their rules. ## Deploy a GaiaNet Mainnet GPU Node on NodeOps DePIN Cloud Use the video or walkthrough to understand how to deploy and operate a GaiaNet Mainnet GPU Node at-a-click with no setup overhead. ### Prerequisites - Sufficient funds for the GPU deployment ### Step 1: Create the deployment 1. Follow [Cloud.NodeOps.Network/Marketplace/gaia-mainnet-agent](https://cloud.nodeops.network/marketplace/gaia-mainnet-agent), or [log in](https://cloud.nodeops.network/) and navigate to the **Template Marketplace**, and search for **Gaia Mainnet (GPU)**. > You can filter by **GPU** and other filters on the right hand side of the dash to refine the search set. 2. Click **Deploy Template**, and select: - GPU type - Plan (7-day or 30-day) - LLM model **GPU options** - RTX 3090 - Released 2020 - Architecture: Ampere - Perfomance: High VRAM (24 GB GDDR6X), strong 4K performance, well-suited for creative workloads - Features: Offers exceptional rendering and AI capability - RTX 4090 - October 2022 - Architecture: Ada Lovelace, using TSMC 4N process - Performance: Offers 50% to 100% better performance than the RTX 3090 across benchmarks, creative workloads, and 4K gaming - Features: Superior ray-tracing, DLSS 3, more CUDA/Tensor/RT cores, significantly improved efficiency - RTX 5090 - Q1 2025 - Architecture: Blackwell (RTX 50-series) - Performance: Upgraded core counts: ~21,760 CUDA cores vs. 16,384 on the 4090. VRAM: 32 GB GDDR7 on a 512-bit bus, offering significant bandwidth boost > RTX 5090 comparison: > - Compared to RTX 4090: ~27–35% average performance improvement in gaming and AI workloads [source](https://www.corsair.com/us/en/explorer/gamer/gaming-pcs/rtx-5090-vs-4090-whats-the-difference/) > - Compared to RTX 3090: Massive leap in performanceβ€”benchmarks show 69–97% higher FPS across resolutions [source](https://www.club386.com/nvidia-geforce-rtx-5090-vs-rtx-3090/) **Available LLM Models** Each of these LLM models is provided in quantized format (Q5_K_M), which trades some precision for smaller memory footprint and faster inference, making them GPU-friendly. - EXAONE-3.5-24B-Instruct-Q5_K_M: - Large-scale 24B parameter instruct model - Optimized quantization (Q5_K_M) for efficiency - General-purpose reasoning and task completion - Qwen2.5-7B-Instruct-Q5_K_M: - 7B parameter instruct model from Alibaba’s Qwen series - Balanced for chat, summarization, and Q&A - Quantized for faster inference with moderate memory usage - Llama-3.2-3B-Instruct-Q5_K_M - Meta’s Llama 3.2 model (3B parameters) - Lightweight, efficient for instruction following - Good choice for smaller tasks and resource-limited runs - Qwen2.5-Coder-3B-Instruct-Q5_K_M - Specialized 3B model for code understanding & generation - Optimized for programming tasks (Python, JS, etc.) - Small footprint for cost-effective code inference - DeepSeek-R1-Distill-Llama-8B-Q5_K_M - Distilled 8B parameter model, derived from Llama - Balanced between speed and quality - Great for chatbots and general AI applications - Qwen2-0.5B-Instruct-Q5_K_M - Tiny 0.5B instruct model - Ultra-lightweight, very fast and cheap to run - Suitable for simple Q&A or rule-based inference 3. Click **Next**, complete payment, and click **Deploy**. ### Step 2: Register your Node with GaiaNet 1. Follow [GaiaNet.ai/Setting/Nodes](https://www.gaianet.ai/setting/nodes), and click **Connect**. Remember to connect the same wallet you use to for NodeOps Cloud. 2. Review and accept the terms of service. 3. Click **Connect New Node**, copy/paste the Node ID and Device ID from the NodeOps dash to the GaiaNet Node registration form and click **Join**. 4. Open the Node menu and select **Join Domain**. 5. Click Next Step and choose a Gaia domain matching your LLM model. 6. Verify your Node status and domain match, then click **Complete**. Congratulations your AI agent is active. Choose how you want to use this: - [Add this Node to GiaNet](#optional-step-3-join-the-gaianet-protocol-to-earn-rewards) to serve other end users and earn GaiaNet rewards - [Leverage your own AI Agent](#optional-step-4-access-your-gaianet-ai-agent) ### (Optional) Step 3: Join the GaiaNet Protocol to earn rewards Use the video or walkthrough to understand how to register your Node on GaiaNet Mainnet to start earning rewards. 1. Log into [GaiaNet.ai/domain-explore](https://www.gaianet.ai/domain-explore) with the same wallet you use for NodeOps Cloud. 2. Identify a Gaia Domain that leverages the LLM model your Node runs, click **Join Now** and **Next Step**. 3. Select a Node that's: - Online - Not already associated with a domain - Provides the required LLM model and click **Next Step**. Congratulations, you are now contributing GPU resources to the GaiaNet Mainnet. ### (Optional) Step 4: Access your GaiaNet AI agent As the host of the AI Agent Node, you have access to your Agent through a public URL or through [API](https://docs.gaianet.ai/getting-started/authentication/). Use the video to understand how to chat via the URL. Notice that you can update the system prompt to tune the agent to your needs. ### (Optional) Step 5: Monitor Node deployments - Monitor a Node deployment: - From [NodeOps Cloud Marketplace](https://cloud.nodeops.network/), navigate to the **My Deployments** page and select the Node instance you want to monitor - From [GaiaNet.ai/Setting/Nodes](https://www.gaianet.ai/setting/nodes), sign in with the same wallet you use on NodeOps Cloud, and navigate to the **Nodes** page - Monitor the GaiaNet rewards your Node earns from [GaiaNet.ai/reward-summary](https://www.gaianet.ai/reward-summary) ## Gotchas 1. If your Node is not fully deployed, then GaiaNet may reject your attempt to register in [Step 2](#step-2-register-your-node-with-gaianet). Ensure there are workload logs before attempting this again. **Show me** 2. Gaia creates intermediate IDs that are returned in the workload logs, don't apply these at [Step 2](#step-2-register-your-node-with-gaianet), use the values displayed in the main dashboard. **Show me** ## What next? - Chat with your favourite domain from [GaiaNet.ai/Chat](https://www.gaianet.ai/chat) - Explore the AI cookbook from [GaiaNet-AI/Gaia-Cookbook](https://github.com/GaiaNet-AI/gaia-cookbook) - Check out [GaiaNet's documentation](https://developer.gaianet.ai/) - Check out the [recording of a live X space with the Gaia and NodeOps devrels](https://x.com/i/broadcasts/1eaKbjDRalYKX) --- ### Gensyn > How to run Gensyn from the NodeOps Template Marketplace URL: https://docs.nodeops.network/Guides/Marketplace/Marketplace-Templates/gensyn-gpu ## Overview [Gensyn](https://www.gensyn.ai/) is a Protocol for Machine Learning (ML) computation. It provides a standardised way to execute ML tasks across any device, aggregating computing supply into a single network. It does this by leveraging [RL Swarm](https://github.com/gensyn-ai/rl-swarm), a peer-to-peer system for reinforcement learning. It allows you to train models collaboratively with others in the swarm, leveraging their collective intelligence. The Gensyn Protocol aims to support AI systems at far greater scale than is possible today by providing a Reinforcement Learning (RL) swarm. It's fully open source and permissionless, meaning anyone can contribute to the Network or use it. You can also connect your model to the Gensyn Testnet to receive an onchain identity that tracks your progress over time. ## Why use NodeOps Cloud for Gensyn Testnet Swarm? - Contribute to the Gensyn RL Swarm - Earn [gNODE](/Guides/Community-Incentives/points) when you participate in the NodeOps ecosystem - Earn Gensyn Testnet rewards by running RL Swarm Nodes - Allow researchers to experiment with multi-agent reinforcement learning - Improve model performance via collective training - Verify and attribute training rounds publicly - Democratize access to AI training across heterogeneous hardware > **Tip: Skip the technical headaches β€” with NodeOps templates, you can instantly deploy Nodes and start contributing to Gensyn. Join the network, support decentralization, and unlock the opportunity to earn token incentives directly from Gensyn.** ⚠️ Disclaimer: NodeOps does not control or guarantee rewards. Incentives, if any, are issued solely by Gensyn based on their rules. ## Join the Gensyn RL Swarm Use the video or walkthrough to understand how to deploy a Gensyn Node at-a-click with no setup overhead. ### Prerequisites - A [Cloud Marketplace account](https://cloud.nodeops.network/) - Sufficient funds for the Compute ### Step 1: Deploy your Testnet Gensyn RL Swarm Node 1. Use the [Template Marketplace Gensyn link](https://cloud.nodeops.network/marketplace/gensyn-testnet-rlswarm), or log in, navigate to **Template Marketplace**, and search for Gensyn RL Swarm Node (Testnet). 2. Click **Deploy Template**, and select the GPU and duration of this Node instance, click **Next**. 3. Pay for the template deployment. ### Step 2: Register your Node with Gensyn 1. Logged into the [Cloud Marketplace](https://cloud.nodeops.network/deployments), navigate to **My Deployments**. 2. Wait for the template to deploy and click your unique endpoint when it becomes available. > Reload the page to refresh the state if necessary. 3. Link your Node to Gensyn by authenticating an email address. 4. Visit [Dashboard.Gensyn.ai](https://dashboard.gensyn.ai/) and log in with the same email. > The dashboard shows your Node's status once it begins contributing to the swarm. Allow several hours. ## Gotchas - Reload the page if your endpoint does not appear after 20 minutes at Step 2 - Use the same email to register and login to Gensyn with - If the GPU provider resets the Node, you will need to repeat Steps 2.3 and 2.4 ## FAQ - Can I access my Gensyn Node? > No, this Node contributes to the Gensyn swarm, it is not an end-user facing Node. You can review the workloads by clicking on the deployment's card. - How do I manage my instance? > - Click into your deployed instance to view **workload logs** > - Check for errors > - Use **Restart Workload** or **Reschedule** if needed (move to a different server) ## What next? - See the [Gensyn documentation](https://docs.gensyn.ai/) - Discover more [Marketplace template guides](/Guides/Marketplace/Marketplace-Templates) - See all the [products and services](/Core-Services#product-and-services) offered in the NodeOps ecosystem --- ### Hyperspace aiOS > How to run an Inference Devnet Node from the NodeOps Template Marketplace URL: https://docs.nodeops.network/Guides/Marketplace/Marketplace-Templates/hyperspace-gpu ## Overview [Hyperspace](https://hyper.space/) is a generative browser built on a peer-to-peer AI network. It’s designed to transform how you search, explore, and analyze information online by combining multiple AI models and computational powers distributed across the network. Hyperspace positions itself as **Everyone’s Personal Supercomputer**. It aims to significantly elevate web research, exploration, and AI-assisted interaction, all run from within your own browser environment. ## Why run a Hyperspace aiOS Testnet Node? - Decentralized AI participation: Supply GPU to a global peer-to-peer AI network and democratize access to powerful models - Economic incentives: Earn cryptocurrency rewards for providing GPU and maintaining network integrity - Open access: Enable free and censorship-resistant use of AI apps for worldwide users - Early phase opportunity: Become an alpha participant influencing platform features and enjoying early adopter benefits - Earn [gNODE](/Guides/Community-Incentives/points) when you participate in the NodeOps ecosystem > **Tip: Skip the technical headaches β€” with NodeOps templates, you can instantly deploy Nodes and start contributing to Hyperspace. Join the network, support decentralization, and unlock the opportunity to earn token incentives directly from Hyperspace.** ⚠️ Disclaimer: NodeOps does not control or guarantee rewards. Incentives, if any, are issued solely by Hyperspace based on their rules. ## Deploy a Hyperspace aiOS Testnet Node on NodeOps DePIN Cloud Use the video or walkthrough to understand how to deploy and operate a Hyperspace aiOS Node at-a-click with no setup overhead. ### Prerequisites - Sufficient funds for the GPU deployment ### Step 1: Deploy a Hyperspace Testnet aiOS Node 1. Follow [Cloud.NodeOps.Network/Marketplace/Hyperspace-Testnet-aios](https://cloud.nodeops.network/marketplace/hyperspace-testnet-aiOS), or [log in](https://cloud.nodeops.network/) and navigate to the **Template Marketplace**, and search for **Hyperspace**. > You can filter by **GPU** and other filters on the right hand side of the dash to refine the search set. 2. Click **Deploy Template**, and pick your preferred GPU and plan (7-day or 30-day). 3. Click **Next**, complete payment, and click **Deploy**. Congratulations, you are now contributing GPU resources to the Hyperspace Testnet. ### (Optional) Step 2: View your Node's workloads You can always monitor a Node deployment from NodeOps Cloud Marketplace. Navigate to the **My Deployments** page and select the Node instance you want to monitor. ## What next? - View your points by importing your wallet into the Hyperspace website at [Node.Hyper.Space/](https://node.hyper.space/) - Checkout [Hyperspace aiOS on GitHub](https://github.com/hyperspaceai/hyperspace-node) --- ### Inference Devnet > How to run an Inference Devnet Node from the NodeOps Template Marketplace URL: https://docs.nodeops.network/Guides/Marketplace/Marketplace-Templates/inference ## Overview The [Inference Devnet](https://devnet.inference.net/) is a globally distributed network made up of GPU operators who provide Compute resources to run AI inference tasks on large language models like Llama 3, DeepSeek, and others. By decentralizing inference, the network lowers costs, increases availability, and creates an open marketplace for AI Compute, enabling more scalable, efficient AI application delivery. ## Why run an Inference Devnet Node? By renting GPU from the NodeOps Cloud Marketplace and to run an Inference Node, you get the opportunity to earn devnet $INT token rewards proportional to the Compute power you contribute and the performance of your Node/s. - Contribute GPU Compute to the Inference Devnet to run AI inference tasks (such as DeepSeek R1, Gemma3, Llama 3.3 70b) and earn $INT points - Stake test $INT-DEV tokens on Solana Devnet - Manage operator pools to increase job allocation and rewards - Participate in network security via inference verification - Maintain GPU uptime and integrity to stay compliant and avoid slashing - Earn [gNODE](/Guides/Community-Incentives/points) when you participate in the NodeOps ecosystem > **Tip: Skip the technical headaches β€” with NodeOps templates, you can instantly deploy Nodes and start contributing to Inference. Join the network, support decentralization, and unlock the opportunity to earn token incentives directly from Inference.** ⚠️ Disclaimer: NodeOps does not control or guarantee rewards. Incentives, if any, are issued solely by Inference based on their rules. ## Deploy an Inference Devnet operator Node on NodeOps DePIN Cloud Use the video or walkthrough to understand how to deploy and operate an Inference.net Devnet GPU Node at-a-click with no setup overhead. ### Prerequisites - Sufficient funds for the GPU deployment ### Step 1: Get your Worker Code 1. Create an account at [Devnet.Inference.Net/dashboard/workers](https://devnet.inference.net/dashboard/workers). 2. Click **Create Worker**, accept default **Install Type** as CLI. 3. From the command box (Step 2), copy the code shown after the `--code` flag. ### Step 2: Deploy your Inference Devnet operator Node on NodeOps 1. Use the [Cloud Compute Marketplace Inference link](https://cloud.nodeops.network/marketplace/inference-devnet-operator), or log in and navigate to the **Template Marketplace**, and search for **Inference**. > You can filter by **GPU** and other filters on the right hand side of the dash to refine the search set. 3. Paste the Worker Code copied in Step 1 into the template field. 4. Pick your preferred GPU and plan (7-day or 30-day). 5. Click **Next**, complete payment, and click **Deploy**. Congratulations, you are now contributing GPU resources to the Inference.net Devnet. ## What next? - Checkout [Inference on X](https://x.com/inference_net) - Learn more from the [Inference docs](https://docs.devnet.inference.net/getting-started/introduction) --- ### n8n > How to run an n8n instance from the NodeOps Template Marketplace URL: https://docs.nodeops.network/Guides/Marketplace/Marketplace-Templates/n8n ## Overview [n8n](https://n8n.io/) is an opensource workflow automation tool that lets you connect apps/services and automate tasks without writing code. Build workflows by chaining together components (each representing an action, trigger, or transformation), which lets you build integrations, automations, and pipelines in a visual way. ## Why run a n8n template? - Automation power, no heavy dev overhead: Quickly automate repetitive tasks (like polling APIs, moving files, sending messages) without needing to build full-scale services - Efficient workflow contribution: Maintain your own workflows, test new integrations, or share common workflow templates with your community - Cost & time savings: Using templates reduces setup cost and effort; you don’t start from scratch - Earn [gNODE](/Guides/Community-Incentives/points) when you participate in the NodeOps ecosystem ## Deploy an n8n instance on NodeOps DePIN Cloud Use the video or walkthrough to understand how to deploy and operate an n8n instance at-a-click with no setup overhead. ### Prerequisites - Sufficient funds for the template deployment ### Step 1: Deploy an n8n instance 1. Logged into [Cloud.NodeOps.Network/Marketplace/](https://cloud.nodeops.network/marketplace/), navigate to the **Template Marketplace**, and search for **n8n**. > You can filter by **CPU** and other filters on the right hand side of the dash to refine the search set. 2. Click **Deploy Template** and configure: - Your provider (auto assign if you have no preferences) - The CPU resources, or accept the defaults - The duration of this n8n instance 3. Click **Next**, complete payment, and click **Deploy**. ### Step 2: Access n8n 1. Navigate to the **My Deployments** page and select your n8n template. 2. Click **Endpoints** > If you recently deployed, check the workload logs: once the β€œEditor is now accessible” notification appears, your n8n instance is ready. 3. Complete the n8n registration flow. Congratulations, you are ready to [build your agentic workflows](https://docs.n8n.io/workflows/). ## What next? - Checkout [n8n's docs](https://docs.n8n.io/) - Follow our DevRel from deploying the template to connecting and configuring an n8n that integrates with her Google workspace - Consider our ecosystem-contributor article on [what you need to know about low-code and no-code platforms](/Learn/Academy/Automation-Platforms/low-code-platforms-what-you-need-to-know) --- ### Discover Templates > Browse and deploy templates from the NodeOps Cloud Marketplace. Launch apps, blockchain Nodes, AI agents, and infrastructure at a click. URL: https://docs.nodeops.network/Guides/Marketplace/Marketplace-Templates With NodeOps Cloud Marketplace, you can launch templates that define: - Apps - Blockchain or Protocol Nodes - Infrastructure - Environments and more. All at-a-click. A selection of the supported templates are highlighted here, to browse all the available templates, log into the [Cloud Marketplace](https://cloud.nodeops.network/marketplace). ## What is the Template Marketplace? The Template Marketplace simplifies Cloud operations for everyone, whether you're a technical expert or completely new to Cloud technology. Instead of worrying about firewalls, container recovery, and Compute requirements, you can deploy the workloads you need all from an intuitive UI. ## Highlighted templates Discover more about a selection of the templates available from the [Cloud Marketplace](https://cloud.nodeops.network/marketplace): | Name | GPU or CPU | Description | |--------------------------|--------------------|--------------------| |[Task Manager](/Get-Started/Cloud-Infrastructure/deploy) |CPU|Free demo template | |[AnythingLLM](/Guides/Marketplace/Marketplace-Templates/anything-llm.md)|CPU|Self-hosted LLM environment| |[GaiaNet](/Guides/Marketplace/Marketplace-Templates/gaia-mainnet.md)|GPU|Decentralized AI Compute power| |[Gensyn](/Guides/Marketplace/Marketplace-Templates/gensyn-gpu.md)|GPU|Decentralized AI Compute swarm| |[Hyperspace aiOS](/Guides/Marketplace/Marketplace-Templates/hyperspace-gpu.md)|GPU|Decentralized AI Compute power| |[Inference Devnet Operator](/Guides/Marketplace/Marketplace-Templates/inference.md)|GPU|Decentralized AI Compute power| |[n8n](/Guides/Marketplace/Marketplace-Templates/n8n)|CPU|Automated integrated agentic workflows| ## What next? - Follow the [Get Started](/Get-Started/Cloud-Infrastructure/deploy) to deploy your first template for free - Learn more about the NodeOps Ecosystem [core services](/Core-Services) --- ### Manage scans > Manage vulnerability and SBOM scans on NodeOps Security Hub. Create, view, organize, download reports and set up automated scan alerts. URL: https://docs.nodeops.network/Guides/Marketplace/Monitor-Infrastructure/manage-scans > **Note: From the NodeOps Security Hub, you may:** - [Create vulnerability reports](./manage-scans.md#create-reports) - [Create SBOM reports](./manage-scans.md#create-reports) - [View reports](./manage-scans.md#view-reports) - [Organize reports](./manage-scans.md#organize-reports) - [Download reports](./manage-scans.md#download-reports) - [Set up alerts](./manage-scans.md#be-alerted) - [Manually rescan](./manage-scans.md#manually-rescan) - Automate scans ## Prerequisites - An account on NodeOps [Marketplace](https://cloud.nodeops.network/scan). - For alerts and recurring scans, that account is linked to an email This guide will assume you start logged in. Follow the links or watch the [video](./manage-scans.md#what-next) at the end of the page to understand how to manage reports. ## Create reports Follow the [Get Started](/Get-Started/Cloud-Tools/scan.md) guide to create your first report. ## View reports ### Step 1: Select report type Select **Vulnerabilities** or **SBOM** tab according to the report you need. **Show me** ### Step 2: Select the report 1. Click on the name of the resource to expand the details. **Show me** 2. Click the summary block to deep dive into the scan details. **Show me** ## Organize reports From the [scan's report page](./manage-scans#step-2-select-the-report), you have options to sort/and or filter. Use the tabs below to learn more. Sort your reports by: - Vulnerability ID - Severity - Status - Package - Installed Version - Fixed Version - Last Modified **Show me** From the right hand side of the scan report, select your filter options. **Show me** > **Tip: Remove filters by clicking **Clear filters**.** **Show me** ## Download reports From the [scan's report page](./manage-scans#step-2-select-the-report) page, you have the option to download the report as a PDF or a JSON file. **Show me** ## Manually rescan From the [scan overview page](./manage-scans#step-2-select-the-report) page, click **Rescan** to run a new scan. **Show me** ## Be alerted By default you will receive notifications in app. Alternatively, you may choose to be alerted by email, via your machine, or via your browser. In the Request Scan window, check the box to receive notification scans. You will automatically receive an email notification when the scan has been completed. **Show me** By default you will receive notifications in app. **Show me** ## What next? - Follow the [Get Started](/Get-Started/Cloud-Tools/scan.md) guide to create your first report. - [Learn about Security Hub](/Learn/Products/Cloud/security.md) - Watch a quick video covering some of these features: --- ### Monitor Infrastructure > Monitor your NodeOps Cloud deployments and scan for vulnerabilities. Ensure stability, reliability, and security of your DePIN infrastructure. URL: https://docs.nodeops.network/Guides/Marketplace/Monitor-Infrastructure It's vital to ensure that all your instances have the stability and reliability you need. Learn how to: - 🚧 Monitor your deployments - [Scan for vulnerabilities](./manage-scans.md) --- ### Provide GCP Compute > Register Google Cloud Platform Compute with NodeOps Network. Step-by-step guide to configure GCP VMs, set firewall rules, and earn gNODE rewards. URL: https://docs.nodeops.network/Guides/Marketplace/Provide-Compute/provide-gcp-compute # Register your GCP Compute with NodeOps Network Compute comes in all shapes and sizes. Cloud providers such as the Google Cloud Platform are a great way to spin up Compute with little effort. This guide demonstrates how you can use your GCP-powered Compute and register it with NodeOps Network. > **Tip: GCP hands out credits to new users. This means that anyone can provide Compute and earn gNODE in the NodeOps Network!** ## Prerequisites - Gmail account - Wallet - GCP credits or billing to support a VM of the minimum requirements **Requirements** Apply storage in the correct ratio to the number of vCPUs provided to a mimimum: > **Info: Machines **must**** Comply with the minimum hardware and port requirements: - CPUs or vCPUs: β‰₯2 - GB RAM: β‰₯4 - SSD storage: β‰₯80GB NVMe Storage - Network bandwidth: β‰₯1Gbps unlimited - Uptime: β‰₯ 99% - OS: Debian (12+) or Ubuntu (22.04+) installation with: - Linux kernel 6.7+ - Latest security patches - Allow traffic on ports: - UDP 8472,51820 - TCP 10250 - Public static IPv4 address - Run the Protocol at root > **Warning: Machines **must not**:** - Run additional workloads - Have third-party applications or monitoring agents installed - Enable [SWAP](https://wiki.archlinux.org/title/Swap) - Be exposed to intervention with the workload or machines > **Info: Run at root** NodeOps Network's integration must be run directly on a machine at root: - You can't run it in Docker - Don't run it on a homelab ## Step 1. Prepare the network rules 1.1 [Sign up](https://console.cloud.google.com/freetrial) or [log in](https://cloud.google.com/_d/signin) to your Google Cloud account and create a new project. 1.2 Navigate to **Firewall policies** and click **Create firewall rule**. **Show me** 1.3 Name the policy and give it a useful description, click **Create**. **Show me** 1.4 Click **Create Firewall rule**. **Show me** 1.5 Set the following configuration and click **Create**. #### Example firewall configuration: - Name: nodeops-firewall or your alt - Targets: All instances in the network - Priority: 100 else your alt - Source filter: IPv4 ranges - Source IP ranges: 0.0.0.0/0 - Specified protocols and ports: - TCP: 10250 - UDP: 8472,51820 Leave the other properties as default: - Network: default - Direction: Ingress - Action on match: Allow **Show me** > **Info: Setting IPV4 ranges to **0.0.0.0/0** on ingress allows **all** inbound traffic. Specifying the ports restricts the allowed traffic to only the services or Protocols that use these ports. Unless you scope the rule using network tags or source ranges, it will apply to all instances in the same VPC (Virtual Private Cloud), which may expose unintended services. We DO NOT recommend using this GCP project for any critical purpose as, without further configuration.** ## Step 2. Create the Compute 2.1 Navigate to **Compute Engine**. **Show me** 2.2 Navigate to **VM instances** and click **+Create Instance**. **Show me** 2.3 From **Machine configuration**, select for example, **E2**. > Setup a machine to meet the [minimum requirements](provide-gcp-compute#prerequisites). **Show me** 2.4 Click **Change** and add storage and boot disk to [minimum requirements](provide-gcp-compute#prerequisites). **Show me** 2.5 Click **Create** ## Step 3. Register on NodeOps Marketplace ### 3a. Register a as a provider To register as a provider, follow the [Get Started](/Get-Started/Cloud-Compute/Provide-Compute/register-to-provide.md) or stop for 2 minutes to watch a video of this and all the following steps. **Show me video** ### 3b. Register a machine 1. Logged in to the [Cloud Marketplace](https://cloud.nodeops.network/) > **Compute** > **+ Farm Compute**. **Show me** 2. Select **Add My Own Machine** > **Continue** > Determine how many machines > **Continue**. **Show me** 3. Sign the 2 transaction requests in your wallet. Congratulations, the Protocol has registered your Machine and provided it with a unique identifier. 4. Copy the setup code: from the **All** or the **Pending** tab, click **Setup** > **Copy**. > Refresh the page if your Machine doesn't appear in the tab. **Show me** ## Step 4. Connect NodeOps Network to your GCP Compute 4.1 Add `sudo` to your command to allow NodeOps Network read and write access to your GCP machine. ```curl -L https://get.atlasnetwork.dev | sh -s - 9zvmdvJ****SECRET*****w9PHZwP``` > becomes ```sudo curl -L https://get.atlasnetwork.dev | sudo sh -s - 9zvmdvJ****SECRET*****w9PHZwP``` 4.2 From the GCP dashboard, navigate to **VM instances**, click **SSH** and **Authorize** to SSH-in-browser connect to your VM. **Show me** 4.3 Paste your edited code snippet in the terminal provided and press **Enter** on your keyboard to run. **Show me** ## Step 5. Activate your machine on NodeOps Network 5.1 From the [NodeOps Network dashboard](https://cloud.nodeops.network/), find your GCP machine in the "AWAITING-STAKE" state. 5.2 Continue by clicking "Stake." **Show me** 5.3 Confirm the transaction in your wallet. **Show me** 5.4 Your Machine's state changes to "CONFIGURING" and then to "ACTIVE." Congratulations, you're providing decentralized Compute orchestrated by NodeOps Network's Protocol on Arbitrum. ## Troubleshooting Q. Can I check why my machine is not transitioning to active state? A. Yes. From the machine terminal, and run the following command to check if you're facing any issue or if you haven't met the requirements. ```shell journalctl -fu nn-provider* ``` ## What next? - Learn about the various [statuses](/Guides/Marketplace/Manage-Machines/machine-status.md) Compute may occupy - Learn about the [gNODE](/Guides/Community-Incentives/points) rewards that providers earn - Learn more about [\$NODE](/Tokenomics/node) that gNODE converts to --- ### Add Compute > Add and provide Compute resources to the NodeOps Cloud Marketplace. Earn $NODE rewards by registering machines and supplying DePIN Compute. URL: https://docs.nodeops.network/Guides/Marketplace/Provide-Compute ## Earn rewards for providing Compute Each 2CU provided earns up to 10 \$NODE per day: - Base reward: 8 \$NODE - Performance rewards: up to 2 \$NODE **Show me video** ## Provide VM Compute NodeOps Network's Compute Marketplace is intended to support providers who own and register machines they control. However, it doesn't differentiate between a virtual machine (VM) or a piece of hardware. This means that it can support VM resellers. While it's unlikely that you have idle reserved VM instances, if you do, you certainly don't want them to cost rather than earn. You can configure VMs and add them to the Marketplace as this [GCP tutorial](./provide-gcp-compute.md) demonstrates. ## What next? - [Provide VM Compute](./provide-gcp-compute.md) - Understand the [Compute requirements](/Get-Started/Cloud-Compute/Provide-Compute/README.md) - Become a [Compute provider](/Get-Started/Cloud-Compute/Provide-Compute/register-to-provide.md) - Learn how to [unbond your \$NODE](/Guides/Marketplace/marketplace-account#unbond-node) --- ### Compute Marketplace > Navigate the NodeOps Compute Marketplace dashboard. Deploy templates, manage Compute infrastructure, provide resources, and track deployments. URL: https://docs.nodeops.network/Guides/Marketplace > **Tip: TL;DR** Whether you're a developer or Node operator, the Marketplace has everything you need to start building. ## Prerequisites - [NodeOps Marketplace](https://cloud.nodeops.network/) account ### Marketplace overview - [Main](./README.md#main) - [Account](./README.md#account) - [Profile](./README.md#profile) ### Marketplace menus #### Main Dashboard area 1, the top left hand side menu facilitates access to decentralized, coordinated **Cloud Compute** that you can [supply](/Get-Started/Cloud-Compute/Provide-Compute/README.md) or consume. You consume Compute by: 1. [Running workloads from the **Template Marketplace**](/Get-Started/Cloud-Infrastructure/deploy), you utilize existing: - Agents - Apps - Custom workloads - Custom development environments - Protocol or Blockchain Nodes 2. Creating and deploying [custom templates to run custom workloads](/Guides/Marketplace/Configure-Compute/upload-template). 3. Deploying [private, custom workloads](/Guides/Marketplace/Configure-Compute/upload-template). 4. Using the products that NodeOps Network releases to keep builders focused on what matters, such as: - [Security Hub](/Get-Started/Cloud-Tools/scan.md) - [Agent Terminal](/Get-Started/Cloud-Tools/agent-terminal) #### Account Dashboard area 2, the mid left hand side menu facilitates access to: - **My Deployments**: Track all your active deployments here. Click on any active deployment to monitor key metrics such as CPU usage, memory, machine details, network usage, and workload logs. This is the cockpit for managing your Nodes. - **My Plans**: Provides an overview of your Compute rentals, including the number of Nodes, their statuses, deployment dates, and expiry dates. - **My Templates**: Provides an overview of your deployed and custom templates, whether their status be draft, under review, live, or declined. #### Profile Under **Account** > **Profile** is your personal section where you can track your total number of Nodes deployed, total referrals, points earned, and personal referral link. Dashboard area 3, the bottom left hand side menu extends the profile section by facilitating access to: - Support - [Credit top up](/Get-Started/Pay-for-Services) - [Profile data](/Guides/Marketplace/marketplace-account) - Logging out ## What next? - Learn more about [managing your account](/Guides/Marketplace/marketplace-account) - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) - Consider our [FAQ](/Learn/FAQ/faq.mdx) section for answers to common queries --- ### Portal | DeFi Services > Use NodeOps Portal for DeFi services β€” stake $NODE, bridge tokens, redeem gNODE, manage UNO NFTs, and vote on governance proposals. URL: https://docs.nodeops.network/Guides/Portal 🌟 Status: Live > **Note: [NodeOps Network Portal](https://portal.nodeops.network), lets you:** #### Work with $NODE - [Bridge](#bridge-with-nodeops-portal) \$NODE - [Claim \$NODE staking rewards](#claim-your-node-staking-rewards) - Claim and restake \$NODE staking rewards - [Convert](#redeem-gnode-with-nodeops-portal) gNODE to \$NODE - Claim the \$NODE gNODE rewards - Stake: - [$NODE](#stake-node-with-nodeops-portal) - [Supported tokens](#stake-supported-tokens-with-nodeops-portal) - Swap your \$NODE - Top up credits - [Transfer](#transfer-with-nodeops-portal) \$NODE - [Unstake tokens](#unstake-your-tokens) - View your [\$NODE balance](#view-node-in-your-wallet) - View your [staked balance/s](#view-your-stakes) #### Work with UNO - Mint an UNO - [Undelegate an UNO](#undelegate-your-uno-nft) #### Vote on Protocol Improvement Proposals - [Vote](/Tokenomics/governance#vote-on-governance-proposals) ## Bridge with NodeOps Portal This guide walks you through bridging \$NODE accross different chains. Use the video or walkthrough to understand how to bridge your \$NODE. **Show me video** > **Info: Finality and fees differ** - **Ethereum ↔ Arbitrum:** Native bridge (up to 15-minute finality) - **Ethereum ↔ BSC:** Official BSC bridge (7-day withdrawal) - **Arbitrum ↔ BSC:** Third-party bridge via LayerZero (up to 15-minute finality) The gas fee to bridge is always dynamic: based on network congestion. #### Prerequisites - EVM-compatible wallet containing \$NODE - Gas funds - You are logged into the [NodeOps Portal](https://portal.nodeops.network). 1. From the **Bridge** tab, choose your source and destination chains. **Show me** > **Important: Ensure your wallet is connected to the source chain and has enough funds for gas on that chain.** 2. Enter amount: specify how much \$NODE you want to bridge or use **Max**, review the transaction details, and confirm in your wallet. > Note that the dashboard displays your \$NODE balance based on the origin chain. **Show me** 3. Click **Bridge Tokens**. Wait for completion: the bridge process may take a few minutes. #### (Optional) verify the transfer Either: - Switch your wallet to the destination chain and check your balance to confirm the bridged \$NODE - Click **View on explorer** to examine the onchain record of the transaction ## View \$NODE in your wallet **Show me video** 1. Log in to the [portal.nodeops.network/transfer](https://portal.nodeops.network/transfer) with your [relevant wallet](/Learn/Products/DeFi-Services/staking#supported-wallets). 2. Select the chain your \$NODE is on. > The airdropped \$NODE is on Arbitrum One. **Show me** 3. You balance now shows at the top right of the dashboard. **Show me** ## Claim your $NODE staking rewards #### Prerequisites - You have unclaimed \$NODE earned from staking - Arbitrum ETH for gas fees Use the video or walkthrough to understand how to claim $NODE staking rewards. **Show me video** 1. Logged into [Portal.NodeOps.Network/Stake](https://portal.nodeops.network/stake), from the **Stake** tab, ensure you are on the **Arbitrum One** network and click **\$NODE**. **Show me** 2. To extract the \$NODE to your wallet, click **Claim only**. > Alternatively, you may choose to restake the \$NODE. **Show me** 3. Confirm the transaction in your wallet, noting the gas fee. Congratulations, the \$NODE is now in your wallet. ## View your stakes #### Prerequisites - You have staked tokens with NodeOps Portal 1. Logged into [Portal.NodeOps.Network](https://portal.nodeops.network/stakinghub), from the **Stake** tab, click **\$NODE** or **Other Assets** to review your active stakes. **Show me** 2. Review the details. ## Redeem gNODE with NodeOps Portal > **Tip: TL;DR** [NodeOps Portal](https://portal.nodeops.network) allows you to convert the [gNODE](/Guides/Community-Incentives/points) you earn across the NodeOps ecosystem into $NODE. Use the video or walkthrough to understand how to redeem gNODE for \$NODE. **Show me video** #### Prerequisites - You are logged into [NodeOps Portal](https://portal.nodeops.network/rewards) - EVM-compatible wallet linked to a NodeOps app that has earned gNODE > Remember to use a wallet that is linked to one of the NodeOps [Core Services](/Core-Services) that has earned gNODE. 1. From [Portal's **My Rewards**](https://portal.nodeops.network/rewards) tab, click **Redeem gNODE**. **Show me** 2. Choose how much of your gNODE pot to convert, or select MAX to convert all. **Show me** 3. Choose the redemption period, the time over which the gNODE is converted to \$NODE. > **Info: The longer the period you set, the better the conversion rate:** **Show me** 4. Click **Redeem gNODE** to confirm your choices. Congratulations, your reward points are converting to \$NODE. ## Stake \$NODE with NodeOps Portal You may stake \$NODE on: - Arbitrum - Binance Smart Chain Follow the YouTube video, or the [Get Started](/Get-Started/DeFi-Services/stake#stake-node-with-nodeops-portal) walkthrough. **Show me video** ## Stake supported tokens with NodeOps Portal **Show me supported tokens** - **$ATH** Mainnet > 100 K gNode pool | ends 4th October, 2025 - **$POL** on Ethereum Mainnet > 2 mil gNODE pool | ends 28th July, 2026 NodeOps is working hard to make our vision a reality: - $HYPE Mainnet - $ETH EigenLayer Mainnet - $BEAM Mainnet - **$HYPE** Testnet Follow the YouTube video, or the [Get Started](/Get-Started/DeFi-Services/stake#stake-supported-tokens-with-nodeops-portal) walkthrough. **Show me video** Testnet $HYPE is used in this example, the flow is identical for other tokens. ## Transfer with NodeOps Portal This guide walks you through transferring \$NODE. Use the video or walkthrough to understand how to transfer \$NODE across chains. **Show me video** #### Prerequisites - Wallets: - Sending wallet: EVM-compatible wallet containing \$NODE - Receiving wallet: EVM-compatible wallet - Funds for gas on the chain your $NODE sits on - You are logged into the [NodeOps Portal](https://portal.nodeops.network) with the sending wallet containing your \$NODE 1. Click **Transfer** on the left hand menu. **Show me** 2. Enter the amount of \$NODE to move. 3. Enter the destination wallet. 4. Click **Transfer**, review the transaction details, and confirm in your wallet. **Show me** #### (Optional) verify the transfer Click **View on explorer** to examine the onchain record of the transaction. Congratulations, the \$NODE has been transferred via the same chain as the original sending wallet's \$NODE. ## Unstake your tokens Use the video or walkthrough to understand how to unstake your tokens. **Show me video** #### Prerequisites - EVM-compatible wallet linked to a NodeOps Portal account that has previously staked - You are logged into [NodeOps Portal](https://portal.nodeops.network/rewards) > **Warning: Remember that many Protocols apply a cool-down period for unstaking to protect their network.** For example, it takes 21 days to unstake the Beam Node token (license) or BEAM token. 1. Click **Stake** on the left hand side of the dashboard, then select **\$NODE** or **Other Assets** and click the **Unstake** tab. **Show me** 2. Review and confirm the transaction request in your wallet. Congratulations, you should received an **Unstake successful** alert and may now close the form. ## Undelegate your UNO NFT Use the video or walkthrough to understand how to release your UNO NFT from the Operator Node that forms the [Arbitrum L3 Protocol verification network for the NodeOps Protocol](/Learn/Ecosystem/nodeorchestrator). **Show me video** #### Prerequisites - UNO NFT delegated to an [Orchestrator Node](/Get-Started/Cloud-Compute/node-orchestrator) 1. Logged into [Portal.NodeOps.Network](https://portal.nodeops.network/uno), navigate to the UNO page. **Show me** 2. Select the **Manage UNO** tab and click **Undelegate**. **Show me** 3. Congratulations, your UNO NFT is no longer bound to the Operator Node. ## What next? - [Delegate an UNO](/Get-Started/Cloud-Compute/node-orchestrator) to verify the Protocol - Learn about the [\$NODE tokenomics](/Tokenomics/node) - Learn more about the NodeOps Ecosystem [core services](/Core-Services) - Browse the [Portal FAQ](/Learn/FAQ/portal) - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) --- ### Stake $ATH > Stake $ATH and $NODE in a 1:1 ratio on NodeOps Portal to earn dual staking rewards. Step-by-step guide to wrap, stake, and earn on Ethereum. URL: https://docs.nodeops.network/Guides/Portal/stake-aethir 🌟 Status: Live on Mainnet ## TL;DR - Stake stATH and $NODE in equal ratio - On the Ethereum network - From [Portal.NodeOps.Network](https://portal.nodeops.network/) ## Earn dual staking incentives with $ATH This guide walks you through staking \$ATH and \$NODE to earn rewards. Use the video or walkthrough to understand how to dual stake. **Show me video** ### Prerequisites - EVM-compatible wallet containing - stATH or $ATH on Ethereum - $NODE on Ethereum - Gas funds ### Step 1: Wrap ATH > If your wallet already contains stATH in the Gaming Pool, jump to [Step 3](#step-3-stake-with-nodeops). 1. Log into the [Aethir User Portal](https://user.aethir.com/profile/account). 2. (Optional) Navigate to the **Stake** tab and connect your EVM-compatible wallet to confirm your stATH holdings. **Show me** 3. From the **Wrap** tab, enter the amount of $ATH to convert, click **Approve**, and confirm the transaction in your wallet. **Show me** 4. Click **Wrap** and confirm the transaction in your wallet. **Show me** > You should receive a "Wrapping Successful" message once the event has finalized. ### Step 2: Stake the wrapped $ATH > If your wallet already contains stATH in the Gaming Pool, jump to [Step 3](#step-3-stake-with-nodeops). 1. Logged into the [Aethir User Portal](https://user.aethir.com/profile/account), from the **Stake** tab, select **Aethir Native Staking - Gaming Pool**. **Show me** 2. Enter the amount of veATH to stake, click **Approve**, and confirm the transaction/s in your wallet. > Note that the lock in period doesn't matter from the dual reward perspective for NodeOps staking in Step 3. **Show me** 2. (Optional) use the Etherscan link and verify the transaction. **Show me** ### Step 3: Stake with NodeOps 1. Connect the same wallet at [Portal.NodeOps.Network](https://portal.nodeops.network/). 2. Ensure that your $NODE is on the Ethereum network. > For assistance, see the [bridging guide](/Guides/Portal#bridge-with-nodeops-portal) and return here. 3. Select to **Stake** on Aethir Mainnet and confirm the transaction in your wallet. **Show me** 4. Match your stATH balance with your \$NODE balance, click **Stake**, and confirm the transaction/s in your wallet. > This campaign requires you to stake \$NODE: Aethir in a 1:1 ratio. **Show me** Congratulations, you are earning dual incentives. ## What next? - Learn more about [NodeOps Portal's](/Guides/Portal) functions --- ### Telegram bot > Use the NodeOps Telegram bot to deploy Nodes, farm Compute, check gNODE balance, redeem $NODE, top up credits, and manage your account. URL: https://docs.nodeops.network/Guides/tg-bot 🌟 Status: Live > **Note: - [Connect your account](#connect-your-account)** - [Reconnect with the bot](#reconnect-with-the-bot) From the NodeOps Telegram bot, you may: - Account: - [View your plans](#view-your-plans) - Funds: - [Check your credit balance](#check-your-credit-balance) - [Top up credits](#top-up-credits) - Rewards: - [Check your gNODE balance](#check-gnode-balance) - [Convert gNODE to \$NODE](#convert-gnode-to-node) - Services: - [Deploy Compute farming](#deploy-compute-farming) - [Deploy Protocol Nodes](#deploy-protocol-nodes) - [Deploy Marketplace templates](#deploy-marketplace-templates) ## Bot commands **Show me the supported commands** `/start` > Start the bot `/credits` > [Check your current credits](#check-your-credit-balance) `mygNODE` > Get your [gNODE balance](#check-gnode-balance) `/redeemNODE` > [Convert gNODE](#convert-gnode-to-node) `/deploynodes` > Deploy supported [Protocol and Blockchain Nodes](#deploy-protocol-nodes) `myplans` > Retrieve your [deployed templates, rented Compute, and/or deployed Nodes](#view-your-plans) `/deploytemplates` > Deploy supported [Cloud Marketplace templates](#deploy-marketplace-templates) `/deploycompute` > [Farm Compute](#deploy-compute-farming) `/topup` > [Top up your Console account with credits](#top-up-credits) `/help` > Show help information ## Manage your account ### View your plans #### Prerequisites - [Telegram bot is enabled](#connect-your-account) 1. Start typing the command and tab to autocomplete or complete typing in full. 1. Use the hamburger menu and click to select your command. **Show me** **Command**: `/myplans` ## Manage funds ### Check your credit balance #### Prerequisites - [Telegram bot is enabled](#connect-your-account) 1. Start typing the command and tab to autocomplete or complete typing in full. 1. Use the hamburger menu and click to select your command. **Show me** **Command**: `/credits` **Show me** ### Top up credits #### Prerequisites - [Telegram bot is enabled](#connect-your-account) - Supported card or tokens **Show me accepted stables and tokens** You can convert $NODE to credits, convert other supported stables or tokens to credits, or pay with supported cards or tokens: [Source](https://copperx.io/payment-methods). 1. Start typing the command and tab to autocomplete or complete typing in full. 1. Use the hamburger menu and click to select your command. **Show me** **Command**: `/topup` ## View rewards ### Check gNODE balance #### Prerequisites - [Telegram bot is enabled](#connect-your-account) 1. Start typing the command and tab to autocomplete or complete typing in full. 1. Use the hamburger menu and click to select your command. **Show me** **Command**: `/mygNODE` **Show me** ### Convert gNODE to \$NODE Use the walkthrough or video provided to redeem your [gNODE](/Guides/Community-Incentives/points) balance directly from Telegram. **Show me video** #### Prerequisites - [Telegram bot is enabled](#connect-your-account) - [gNODE balance exists](#check-gnode-balance) - You wish to redeem your full gNODE balance 1. Start typing the command and tab to autocomplete or complete typing in full. 1. Use the hamburger menu and click to select your command. **Show me** **Command**: `/redeemNODE` 2. Select **Max** or **cancel** the request. **Show me** 3. Select your redemption duration according to the reward ratio you are targeting: - 100%: 150 days - 50%: 90 days - 25%: 30 days - 10%: 15 days **Show me** ## Deploy Compute farming Use the walkthrough or video provided to [farm Compute](/Guides/Marketplace/farm) directly from Telegram. **Show me video** #### Prerequisites - [Telegram bot is enabled](#connect-your-account) - Sufficient credits or supported card or tokens **Show me accepted stables and tokens** You can convert $NODE to credits, convert other supported stables or tokens to credits, or pay with supported cards or tokens: [Source](https://copperx.io/payment-methods). 1. Start typing the command and tab to autocomplete or complete typing in full. 1. Use the hamburger menu and click to select your command. **Show me** **Command**: `farmcompute` 2. Select the number of [CUs](/Learn/Glossary/compute-unit) for your Machine. 3. Enter the subscription duration, and confirm the request. 4. Review and confirm your plan. ## Deploy Protocol Nodes Use the walkthrough or video provided to setup a Node subscription directly from Telegram. **Show me video** #### Prerequisites - [Telegram bot is enabled](#connect-your-account) - Sufficient credits or supported card or tokens **Show me accepted stables and tokens** You can convert $NODE to credits, convert other supported stables or tokens to credits, or pay with supported cards or tokens: [Source](https://copperx.io/payment-methods). 1. Start typing the command and tab to autocomplete or complete typing in full. 1. Use the hamburger menu and click to select your command. **Show me** **Command**: `/deploynodes` 2. Select the Node you wish to deploy, and confirm the request. 3. Enter the number of Node instances to deploy, and confirm the request. 4. Enter the subscription duration, and confirm the request. ## Deploy Marketplace templates #### Prerequisites - [Telegram bot is enabled](#connect-your-account) > The bot supports a subset of the Marketplace services. The team will be constantly updating this set. 1. Start typing the command and tab to autocomplete or complete typing in full. 1. Use the hamburger menu and click to select your command. **Show me** **Command**: `/deploytemplates` 2. Follow the prompts for the template you select. > Different templates have different requirements. Browse the [highlighted templates](/Guides/Marketplace/Marketplace-Templates) from the Marketplace to discover guides. ## Connect your account #### Prerequisites - [Console](https://console.nodeops.network/profile) or [Marketplace](https://cloud.nodeops.network/profile) account - Personal Telegram app is active #### Setup a connection to the bot To use this bot, you need to connect your Telegram account: 1. From your: [NodeOps Console profile](https://console.nodeops.network/profile), or your [NodeOps Marketplace profile](https://cloud.nodeops.network/profile), click **Connect Telegram**. **Show me** 2. Copy your OTP, and click the **exit** icon to move to the Telegram app. **Show me** 3. Enter the OTP code in the TG bot chat. > If you return to your profile dashboard, you will see "Your telegram is connected". > > **Show me** > > In Telegram, you will see: "βœ… Telegram account connected successfully!"" You can now use all the bot's features. Congratulations, you can now manage your NodeOps account and services directly from Telegram. ## Reconnect with the bot #### Prerequisites - [Telegram bot is enabled](#connect-your-account) Lost the bot in Telegram? Don't worry! Either: - Search Telegram for `@UseNodeOpsBot` - Connect again from your profile page in the [Console](https://console.nodeops.network/profile) or [Marketplace](https://cloud.nodeops.network/profile) dashboard. **Show me** ## What next? - Learn more about the NodeOps Ecosystem [core services](/Core-Services) - [Discover NodeOps Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates) --- --- ## Learn ### Implications of using API keys > Learn how API keys work with LLMs, what data you share, and best practices for secure API key management on NodeOps Network. URL: https://docs.nodeops.network/Learn/Academy/API-Fundamentals/api-key-plus-data This academy page covers whether using API keys and sharing your data can be decoupled. Answer: yes. > **Tip: TL;DR** Using an API key with an LLM (Large Language Model) doesn’t mean exposing your private data. The key’s simply a credential that proves you’re authorized to access the service. The real risk is if your key gets leaked, allowing others to use your account. > **Important: NodeOps handles API keys so that you don't have to when running your [products and services on the Cloud Marketplace](/Core-Services).** ## Are API Keys Safe? What You Really Share With LLM Providers Once you have API keys, it's kinda on you to protect those keys, understand your provider’s data policy, and choose local models if your context demands maximum security. When people first experiment with large language models (LLMs), one of the first hurdles they encounter is the mysterious API key. You paste it into your app or notebook, press β€œrun,” and suddenly the AI is at your fingertips. But then comes the concern: Wait… by giving the model my API key, am I also giving away my data? This is a common misconception. To set the record straight, let’s unpack what API keys are, how they work with LLMs, and why using one doesn’t mean you’re handing over all your private information. ### What is an API key? [An API key](/Learn/Glossary/api-key) is like a digital credential. It's a way for services to recognize that you’re authorized to use them. Think of it like a password used by machines. For example, when your app wants to access an AI model, it includes your API key in the request. The provider checks the key, confirms your account, and then processes your request. Without the key, your request wouldn’t be allowed in. ### What happens when you use an LLM API? When you send a request to an LLM like OpenAI’s GPT or Anthropic’s Claude, two key things go out from your side: 1. Your prompt (the input text you want the model to process). 2. Your API key (so the system knows it’s you making the request). The provider’s servers then process your prompt, generate a response, and send it back. That’s the whole exchange, the API key only proves to the AI provider that you’re an authorized user. It determines IF you get access and, if yes, exactly to what. In the case of LLMs, the API dataload is the prompt you sent. is what the model reads to generate a response. ### Data handling: what happens behind the scenes Understandably, many people worry about what happens to the text they send into an LLM. Do providers store everything you type forever? The answer depends on the provider’s policies. Some providers may keep temporary logs for debugging or abuse detection. Others allow you to opt out of data retention entirely. Reputable companies (such as OpenAI, Anthropic, or Cohere) publish clear policies on how your prompts are handledβ€”for example, see [OpenAPI](https://openai.com/enterprise-privacy), and [Anthropic](https://www.anthropic.com/consumer-privacy-notice). That means you’re not β€œgiving away your data” by default. Instead, your data is processed according to transparent rules, and in many cases, you can control how much is stored. ### The real risk: leaking your API key If there’s a genuine danger, it’s not that the provider steals your data when you use their API. The real risk is much simpler: someone else getting hold of your API key. Imagine leaving your Netflix password on a public forum. Strangers could start watching shows under your accountβ€”racking up usage while you foot the bill. API keys work the same way. If you accidentally publish your API key online, say by posting it in a ChatGPT conversation where the data is collected, someone else could use it to send requests on your account. That could burn through your usage allowance, cost you money, or even trigger rate limits that block your access. ### Best practices for safe API key usage So how do you protect yourself? A few simple habits go a long way: - ❌ Don't: Paste [secrets](/Learn/Glossary/secrets) into code, chats, or sites that others access - βœ… Do: Use [environment variables](/Learn/Glossary/environment-variables) or secure vaults to store secrets If you want to keep your data your own, then it's on you to know your provider’s policy. Always think about your use case. For casual exploration, Cloud APIs are convenient and safe. But for highly sensitive or regulated data, you may prefer running a local model or a model hosted on servers that you control. ## What next? - Consider [launching a GaiaNet Node from NodeOps Cloud Marketplace](/Guides/Marketplace/Marketplace-Templates/gaia-mainnet) and own your data on that Node: no API key needed, just provide the Compute that your [LLM model](/Reference/llms-supported) needs --- ### Implications of using low code platforms > Explore the pros, cons, and key considerations of low-code and no-code platforms for Web3 and blockchain app development. URL: https://docs.nodeops.network/Learn/Academy/Automation-Platforms/low-code-platforms-what-you-need-to-know # What do you need to know before you low-code an app? You must have heard about the rise of the low-code and no-code platforms. So, what are the realities of taking part in the low-code revolution? Before establishing a foundational understanding of what low-code development entails, it is essential to clarify the distinction between low-code and no-code. Low-code is for individuals who understand programming but want more flexibility, while no-code is for those with no coding experience. They don't know how programming software works, but want something simple and quick. Just as these platforms are gaining traction in Web2, we are now seeing their equivalents emerge in Web3 through visual interfaces and automation tools designed to accelerate blockchain application deployment. # What is low-code development? Low-code development involves building applications using prebuilt tools and features that require minimal coding effort, but it still demands an understanding of programming intricacies. With low-code development, developers can create applications in weeks or days, tasks that would normally take months if coded from scratch. These platforms are becoming widespread and rapidly gaining traction in the tech space, including in Web3. After all, who wouldn’t appreciate faster development with less stress? The main goal is to accelerate application development and delivery while lowering the barrier to creating software solutions. # What are the pros and cons of low-code development platforms? Now, let’s get to the most interesting part of low-code development platforms: how they benefit developers and businesses. ## Pros 1. Saves cost Comparing the number of developers hired in traditional teams to what is required today [shows a significant cost impact](https://www.index.dev/blog/no-code-low-code-statistics). Companies no longer need large developer teams because low-code/no-code tools enable one developer to do the work of several. Over the long term, businesses hire fewer developers skilled in these platforms, which reduces overall hiring costs. 2. Speed Every CEO and developer wants to launch MVPs quickly. Low-code and no-code tools allow the rapid building and deployment of websites and applications with minimal effort. Today, speed and time to value are decisive factors for project success. 3. Flexibility Low-code tools offer teams much greater flexibility, let’s double-click on some of the immediate wins: - Fully coding an MVP requires skilled developers to create and build applications. However, with low-code/no-code tools, individuals from diverse technical backgrounds, such as project managers, business developers, and product designers, can easily prototype ideas and build applications without requiring deep coding expertise. - In terms of integration with other systems, low-code tools offer the flexibility of prebuilt connectors and [RESTful API](https://aws.amazon.com/what-is/restful-api/) services, which are far easier and less prone to errors than writing custom API connectors. - Another important aspect is the seamless flexibility these platforms provide; when plans change, you can update your application’s design quickly and easily with just a few clicks. 4. Automated scaling Some low-code platforms handle app deployment and automate app scaling. This enables your app or workflow to scale as neededβ€”no heavy lifting or complex DevOps. As more people use your tool or you collect more data, the platform adds resources and keeps things running smoothly. You don’t have to worry about performance drops, even when things get busy. It’s built to handle whatever comes next, hassle-free 5. Low latency Similarly, some low-code deployment platforms offer low latency serving of data and media. When an automation or request runs, the platform routes the request to the node or data center nearest the user. This means no annoying delays. If the process is really complex or under heavy use, you might see a slight lag, but for most everyday tasks, it feels close to instant. ## Cons No solution is 100% perfect. While low-code platforms offer many benefits, they also present potential shortcomings: 1. Customization limitations When platforms are designed to serve a wide range of businesses, they are inherently generic in nature. When your business has unique, complex, or highly specific requirements, you may find the platform unable to accommodate them. Always test whether the components and logic provided by the vendor support your needs without forcing you into suboptimal workarounds. 2. Citizen developer reality The idea that business users can independently build complex applications is often overstated. Without proper engineering discipline, these users may create fragile, poorly structured spaghetti workflows that are hard to debug, maintain, or scale. When such workflows break, IT teams are left to clean up the resulting mess. Ensure you invite the experts in early enough in the product development lifecycle to ensure the maintainability and security of your application. 3. Rising costs Although these tools reduce hiring costs, their adoption and usage fees could continue to rise. Some platforms charge monthly based on resource usage, so as your business scales, costs increase and can potentially exceed the cost of building applications from scratch. Do your research and ensure you choose a platform with transparent fees and a commitment to never locking users in. 4. Steep learning curve Low-code does not mean non-technical users can simply drag and drop to build robust applications. The simple visual interfaces can be deceptive; building scalable, secure integrations requires deep knowledge of system architecture, APIs, and data modeling. Often, significant training or IT involvement is still necessary. 5. Vendor lock-in Building applications on a specific low-code platform ties you to that platform’s pricing, feature set, and ecosystem. Migrating to another platform later can be difficult and costly, limiting your long-term flexibility. 6. Collaboration and developer workflow Low-code tools often lack mature collaboration features that professional software teams depend on, such as Git version control. This limitation makes it difficult for multiple developers to work simultaneously, track changes, perform code reviews, and maintain a clean audit trail. This can lead to chaos in larger or more complex projects. ## FAQs about low-code/no-code platforms #### What's the real difference between low-code and no-code? While the lines can blur, the core difference is the target user. No-code platforms are designed for citizen developers (business analysts, marketers, etc.) with no programming skills, offering a completely visual, drag-and-drop building experience. Low-code platforms are aimed at professional developers, providing a visual environment to speed up development but allowing them to drop down into traditional code for complex logic, custom integrations, and unique functionality. #### Will low-code/no-code platforms make traditional software developers obsolete? The prevailing consensus is no. Instead, they change the developer's role. These platforms automate and accelerate routine tasks (such as basic CRUD app creation), freeing professional developers to focus on complex, business-critical problems, architecture, system integration, and writing custom code for features that the platforms cannot handle. They act as a force multiplier, not a replacement. #### What are the main limitations of Low Code/ No Code Tools? The key limitations are: * Scalability: Can the application handle a massive increase in users or data? * Customization: Platforms can hit a complexity wall where highly specific or unique business logic is impossible to implement visually. * Vendor Lock-in: It can be very difficult to move an application off the platform if you switch vendors or decide to build in-house. * Integration: While many offer connectors, integrating with legacy or highly specialized third-party systems can be a major challenge. * Security: The most vital component of any system that handles PII (Personal Identifiable Information) or accepts payments is security. It’s never advisable to rely on anyone else’s definition of secure. #### How secure are low-code/no-code applications? Security is a shared responsibility. The platform vendor is responsible for the security of the platform (infrastructure, runtime). However, the developer is still responsible for security in the application, for example, configuring user access rights, data validation, and business logic flows. It's crucial to ask vendors about their security certifications, such as [SOC 2](https://secureframe.com/hub/soc-2/what-is-soc-2), [ISO 27001,](https://www.iso.org/standard/27001) and review their shared responsibility model. #### Are these platforms only good for simple internal apps and prototypes? While they excel at those tasks, some of the better modern low-code platforms are robust enough for customer-facing, enterprise-grade applications. However, this requires careful planning and often involves professional developers to extend the platform with code where necessary. They are not a one-size-fits-all solution and should be evaluated based on the specific project requirements. #### What is vendor lock-in, and why is it a concern? Vendor lock-in means that your application is so tightly coupled to a proprietary platform that it cannot be easily migrated to another system. If the vendor raises prices, goes out of business, or discontinues a feature, your business could face significant risk and cost to rebuild the application from scratch. It's a primary concern for long-term, mission-critical projects. #### How do you handle complex data and business logic with a visual tool? This is a common point of friction. Simple logic can be handled with visual workflow builders. For more complex scenarios, low-code platforms (as opposed to strict no-code) allow developers to write custom scripts, APIs, or backend code to handle the complex logic and then integrate it with the visual front-end. This is often where the low-code portion is critical. #### What should I ask a vendor before selecting a low-code/no-code platform? Key questions include: * Can I export my data and app easily? * How well does it scale and perform? * Is there a test or staging area? * How do you manage updates and versions? * Which security certifications do you have? #### If someone wants to be a serious developer, should they avoid no-code/low-code solutions entirely? It depends on your goal, but for learning core programming, you should focus on code. Using no-code tools does not teach you the fundamentals of software development. In addition, understanding the code vs. the syntax of a programming language. Reading syntax is a small part of programming; the real challenge is understanding what the code does and how to think computationally. No-code tools don't teach this. #### Which low-code development platform is the best for your Web3 project? Many of the well-known low-code platforms have been improving to handle Web3 and blockchain app need, supporting everything from complex smart contracts to DeFi (decentralized finance) apps and NFT marketplaces. These tools keep things simple and enable teams to move quickly, while also incorporating features such as automation and smart workflows powered by AI. This makes it easier than ever to tackle complex blockchain projects without getting bogged down. Alongside these trends, several platforms stand out as great options for anyone building on Web3 today. For example: * [Thirdweb](https://thirdweb.com/) is fantastic if you want to deploy smart contracts easily and create NFT projects without hassle. * [Bubble](https://bubble.io/) offers a general no-code app builder experience, but with useful Web3 plugins that open up blockchain capabilities. * [Directual](https://www.directual.com/) is a full-stack no-code platform that supports blockchain integration, making it handy for building more comprehensive solutions. * [Kalp Studio](https://www.kalp.studio/) focuses on helping you build Web3 apps faster with its low-code features. ## What next? Ready to have a go with an open-source workflow automation tool for connecting apps and automating tasksβ€”no coding needed? [Deploy an n8n instance with NodeOps Cloud Marketplace](/Guides/Marketplace/Marketplace-Templates/n8n.md) to build powerful workflows via a visual workspace that links actions, triggers, and data transforms to create custom integrations and pipelines in minutes. ## About the Author This article was written by Judith Etugbo, a technical writer specializing in developer documentation, API documentation, and content writing. Find her on [LinkedIn](https://www.linkedin.com/in/etugbo-judith-984545236). --- ### Node Orchestrators > Learn how UNO Node Orchestrators monitor Compute providers, verify workloads, and earn rewards on NodeOps Network. URL: https://docs.nodeops.network/Learn/Ecosystem/nodeorchestrator # Node Orchestrators 🌟 Status: Live > **Tip: TL;DR** You may [delegate your UNO NFT](/Get-Started/Cloud-Compute/node-orchestrator.md) to run an [Orchestrator Node](/Learn/Ecosystem/nodeorchestrator) and earn [gNODE](/Guides/Community-Incentives/points.md). The gNODE rewards you earn are based on the Orchestrator Node's responsiveness, which is tracked across 24 epochs per day. If the Node actively participates and responds during these epochs, the license holder receives rewards β€” up to a set amount per day per license. The more consistently the operator performs, the more rewards are distributed. > Learn about the [current campaign for Node Orchestrator rewards](/Learn/FAQ/UNO#current-uno-node-operator-campaign). ## Overview UNO (Universal Node Orchestrators) are coordinating Nodes embedded into the core of the NodeOps Protocol. They monitor Compute providers and verify workload jobs. This orchestration layer is key to enforcing performance standards. Universal Orchestrator Nodes ensure that every job is executed correctly, every provider is accountable, and every decision is backed by verifiable data. By combining technical enforcement, economic alignment, and governance rights, UNO Nodes are key to NodeOps autonomous and decentralized Compute coordination layer. [UNOs NFT](/Guides/Community-Incentives/uno) holders are eligible to run UNO Nodes, UNO are available to the public for sale from [NodeOps Portal](https://portal.nodeops.network/). UNO Nodes ensure that every workload running through NodeOps, from AI inference to RPC endpoints, are handled with trust, accuracy, and transparency. > [Get started](/Get-Started/Cloud-Compute/node-orchestrator.md) verifying Compute as a Node Orchestrator. ## What are UNO Nodes? UNO Nodes are decentralized orchestrator Nodes that help maintain the health and trust of the entire NodeOps infrastructure. Think of them as decentralized inspectors or auditors who: - Constantly check if Compute providers are online and providing a service - Verify that jobs are being completed correctly - Collect data about system behavior - 🚧 Enforce penalties when providers misbehave - 🚧 Participate in important governance decisions Orchestrator Nodes are the gatekeepers of trust and performance in a decentralized system that is otherwise hard to monitor from a central point. ## Built on Arbitrum’s Orbit stack The Node Orchestrator Network is built on Arbitrum Orbit, a framework of custom Layer 3 blockchains optimized for specific use cases. This enables: 1. High throughput and low latency: Orbit supports fast, scalable communication between modules like Compute Nodes. 2. Custom rules: NodeOps applies its own enforcement logic and validation workflows directly at the Protocol level. 3. Security: Orbit inherits security from Ethereum while offering sovereignty to the NodeOps Network ecosystem. By using Orbit, NodeOps embeds UNO Nodes into the foundation of its infrastructure, ensuring verifiable coordination across the Compute Network. ## How UNO Nodes work UNO Nodes operate through the following core functions: ### 1. Monitoring Compute providers UNO holders may delegate their license to an Orchestrator Node to earn gNODE rewards. The Orchestrator Node performs the following services: - Uptime checks: Are providers online and responsive? - Performance benchmarks: Are machines delivering promised CPU/GPU speeds and reliability? - Job validation: Did a provider complete a job as expected? - SLA enforcement: Are service-level agreements being honored? ### 2. Logging and pattern recognition - Telemetry Collection: UNO Nodes record system activity like job runs, failures, and resource usage - Anomaly Detection: If a provider underperforms or behaves oddly, UNO Nodes flag this - Historical Scores: Over time, UNO Nodes build trust profiles for providers based on their track record ### 3. 🚧 Slashing and penalties - If a provider fails to adhere to the SLA, UNO Nodes trigger automated penalties: - Slashing staked assets - Lowering workload priority - Temporary or permanent suspension ### 4. 🚧 Governance participation - Voting rights: Participate in Protocol governance to help define and evolve the rules around slashing, job validation, reward distribution, and emission schedules and additional feature and product addition to the Network - Protocol enforcement: Ensure Compute providers and other actors adhere to approved Network policies and standards ## Where are UNO Nodes used in the NodeOps Network? UNO Nodes are integrated across every product and module of the NodeOps ecosystem: | NodeOps Module | What UNO Nodes Do | | --- | --- | | Cloud | Check Compute reliability and job accuracy | | Console | Validate deployments and SLA metrics | | Staking Hub | Confirm validator Node performance and uptime | | Security Hub | Provide trusted telemetry for vulnerability scanning | | Agent Terminal | Verify AI agent outcomes and resource consumption | | RPC Services | Measure uptime, latency, and usage for API endpoints | | Governance engine| Execute Protocol-level voting, policy enforcement | This deep integration makes UNO Nodes essential to every operation running via NodeOps Protocol. ## Why UNO Nodes are strategically important As NodeOps scales, relying on a central team to monitor and enforce standards would create **bottlenecks, single points of failure, and trust issues**. U NO Nodes solve this by: ### 1. Decentralizing enforcement Rather than having a central authority decide what's right or wrong, UNO Nodes act independently and verifiably, using transparent data and Protocol rules to make decisions. ### 2. Improving reliability If something failsβ€”whether it’s a machine, a job, or an entire regionβ€”UNO Nodes detect it quickly. This improves uptime and overall trust in the Network. ### 3. Raising accountability When providers know they’re being monitored, they perform better. UNO Nodes ensure that no provider can cheat the system or slack off without consequences. ### 4. Enabling a modular and autonomous future As the Network expands into **AI orchestration, real-time inference, and autonomous agents**, UNO Nodes will guarantee that every task and agent is operating under verified, auditable conditions. ## UNO Node operator rewards Running a UNO Node comes with significant rewards: ### Economic rewards - Protocol rewards - Bonus payouts for uptime, SLA verification, and governance participation - Receive a quarterly share of profits from the NodeOps Network ### Governance rights - Vote on Protocol decisions alongside $NODE holders - Propose updates backed by real data from the Network - Help shape the long-term vision and operations of NodeOps ### Access and platform privileges - Early access to ecosystem launches and Console projects - Receive discounts on Node deployments, infrastructure migration, and staking services - Be recognized as a core contributor to the NodeOps ecosystem ### Token-based incentives - Favorable $NODE unlocks and better vesting schedules - Auto-bonding: if you’re also a Compute provider, the system bonds $NODE on your behalf to reduce friction and speed up activation ## Use cases and functional domains UNO Nodes support multiple types of operations: - Protocol monitoring: Confirm if all parts of the Network are behaving correctly - Compute auditing: Measure performance and job accuracy - Security logging: Track threats, anomalies, and bad actors - Slashing: Penalize underperformers or cheaters - Governance: Drive forward Protocol upgrades and ecosystem-wide changes With the support of Arbitrum’s Orbit stack, UNO Nodes help NodeOps serve not only blockchain infrastructure, but also the emerging world of AI agents, decentralized inference, and sovereign AI ecosystems. You may view the transaction events on the Arbitrum L3 with [Explorer.NodeOps.Network](https://explorer.nodeops.network) ## What next? - Learn more about [UNO NFTs](/Guides/Community-Incentives/uno) - [Delegate your UNO](/Get-Started/Cloud-Compute/node-orchestrator.md) to run an Orchestrator Node and earn gNODE --- ### Compute Providers > Learn how to become a NodeOps Compute provider, including machine requirements, bonding, Compute units, and reward structure. URL: https://docs.nodeops.network/Learn/Ecosystem/providers 🌟 Status: Live on Mainnet ## Overview Providers form the core of the NodeOps Network and are responsible for contributing CPU resources to a shared pool. This section provides all the information required for providers, including technical and staking requirements, as well as a step-by-step guide on onboarding as a provider. ## Prerequisites To provide machines, you must be [registered](/Get-Started/Cloud-Compute/Provide-Compute/register-to-provide.md) and satisfy the following requirements. ## Requirements - Dedicated machine satisfying the following minimum requirements: > **Info: Machines **must**** Comply with the minimum hardware and port requirements: - CPUs or vCPUs: β‰₯2 - GB RAM: β‰₯4 - SSD storage: β‰₯80GB NVMe Storage - Network bandwidth: β‰₯1Gbps unlimited - Uptime: β‰₯ 99% - OS: Debian (12+) or Ubuntu (22.04+) installation with: - Linux kernel 6.7+ - Latest security patches - Allow traffic on ports: - UDP 8472,51820 - TCP 10250 - Public static IPv4 address - Run the Protocol at root > **Warning: Machines **must not**:** - Run additional workloads - Have third-party applications or monitoring agents installed - Enable [SWAP](https://wiki.archlinux.org/title/Swap) - Be exposed to intervention with the workload or machines > **Info: Run at root** NodeOps Network's integration must be run directly on a machine at root: - You can't run it in Docker - Don't run it on a homelab ## Commitment Providing Compute is a commitment. Your Compute must be from a **standalone** machine which you're **not** using for anything else. That means a personal computer will not qualify. Compute may be provided by a desktop, laptop, VM or server instance on a centralized or decentralized Cloud. Apart from requiring you to open specified ports, NodeOps Network will handle the firewall. In NodeOps Network, every provider must bond: > **Danger: Failing to meet these prerequisites may result in:** - slashing - the suspension of the provider's wallet - the machine being banned ## Provider Capacity In NodeOps Network, the capacity that every provider adds to the pool is measured in a unit called a Compute Unit (CU). ### NodeOps Cloud Compute Units One CU is defined as: 1CU = 1 vCPU, 2GB RAM, 30GB NVMe Disk Every machine a provider provisions gets broken down into the number of CUs; the total of all the CUs is the provider capacity. #### Example 1 One provider brings three machines to the pool. - Machine1: 1 CPU | 4 GB RAM | 100 GB Storage - Machine2: 2 CPU | 4 GB RAM | 200 GB Storage - Machine3: 4 CPU | 8 GB RAM | 500 GB Storage ##### Calculation - CU of Machine1: min(1 | 2 | 3.3) \= 1 - CU of Machine2: min(2 | 2 | 6.6) \= 2 - CU of Machine3: min(4 | 4 | 16.6) \= 4 The provider capacity \= 1+2+4 \= 7 #### Example 2 Consider a machine with this spec: - 4 CPU | 7.57 GB RAM | 150.16 GB Storage ##### Calculation CU: min (4 | 3 | 5\) \= 3 In the above example, the provider bonds 2000 \$NODE for provider onboarding and bond 200, 400, & 800 \$NODE for each machine. ## Node scheduling and deployment Node operators can choose from several options for their Node deployment; for details, refer to [Node Operators](/Get-Started/Console/README.md). Every auto-assign workload deployment is deployed to a machine best suited for it. The NodeOps Network Scheduler is responsible for finding the best machine whenever a new auto-assign workload is added to the pipeline. ![Auto-assign deployment flow](/img/autoassigndeploymentflow.png "Auto-assign deployment flow") The scheduler logic works in three stages: 1. It searches for all the machines among all the providers with free CUs that are more than or equal to the CU requirement for the workload. 2. Next, the scheduler picks the least utilized machine among all these machines. 3. Finally, the machine with the most uptime gets selected from this group for the workload deployment. The second condition ensures that the workload deployment distribution is fair and does not become concentrated among a few providers. Uptime is a crucial metric for all providers and their machines. It measures the amount(%) of time the machine has been available in the provider pool. In NodeOps Network, we want to put machines with the highest uptime ahead in the workload deployment queue. Since rewards are also dependent on running workloads, providers are incentivized to have machines with the maximum uptime they can. ![Machine Uptime](/img/Uptimescreenshot.png "Machine Uptime") If more than one machine passes the third condition, the logic will randomly select one machine from this group. Once the final machine is selected, the NodeOps Network client receives a deployment request, which triggers the actual deployment process. ## Service Level Agreement (SLA) Since provider machines will run Nodes of various Protocols, they must have a high uptime. Providers must ensure that their machines have 99% or more uptime annually. Machines that meet this requirement are chosen for Node deployments, which means having a less uptime machine will impact the earning potential. To maintain a robust network, machines with less than 99% uptime could be removed. ## Rewards and slashing Each 2CU provided earns up to 10 \$NODE per day: - Base reward: 8 \$NODE - Performance rewards: up to 2 \$NODE 🚧 Slashing details to follow. ## What next? - If you are ready to become a provider, follow our [Get Started](/Get-Started/Cloud-Compute/Provide-Compute/register-to-provide.md) guide - Understand more about [managing a machine](/Guides/Marketplace/Manage-Machines/README.md) --- ### Ecosystem participants > Discover the roles within the NodeOps Network ecosystem, including Compute providers, Node orchestrators, and the coordination protocol. URL: https://docs.nodeops.network/Learn/Ecosystem Learn about the different roles available within the NodeOps Network ecosystem. ## A coordinating Protocol NodeOps Networks' decentralized coordination Protocol automates the onboarding, of Compute providers and coordinates the monitoring of machines, the Node Orchestrators that monitor Machine uptime, and rewards providers for the supplied Compute power or slashes the bonded \$NODE. --- ### Restaking Operators > Understand how restaking operators provide cryptoeconomic security to the NodeOps Network via EigenLayer, Babylon, and Solayer. URL: https://docs.nodeops.network/Learn/Ecosystem/restakers # Overview Restaking Operators bring the much needed economic security and verifiability to any off chain service. Restaking platforms like EigenLayer, Babylon, Solayer and others have created a marketplace where the trust within the top public blockchains like Bitcoin, Ethereum, and Solana can be reused to secure off-chain applications. In NodeOps Network, the stake that these operators bring is used to ensure the robustness of the network by providing an additional layer of cryptoeconomic security to Node networks. Critical tasks like payment verification, rewards calculation, and Node score calculation are done by these operators. # Operator onboarding Please follow this link to the [GitHub repo](https://github.com/NodeOps-app/atlas-operator/tree/main) for steps to onboard as an operator on the NodeOps Network. --- ### Community rewards > Learn about NodeOps community rewards including gNODE points, $NODE airdrops, campaign history, and redemption schedules. URL: https://docs.nodeops.network/Learn/FAQ/community-rewards ### Is there a vesting schedule for airdropped \$NODE holders? No, as soon as the airdropped \$NODE is in your wallets it's yours. ## gNODE ### What is gNODE? [gNODE](/Guides/Community-Incentives/points) is the reward layer used within the NodeOps Network to distribute incentives. gNODE Points represent earned rewards that can be redeemed for \$NODE, but is not transferable or tradable on its own. ### How do you convert gNODE to NODE? [gNODE](/Guides/Community-Incentives/points) can be redeemed for \$NODE based on a time-based redemption schedule. The longer you wait to redeem, the higher the percentage of \$NODE you receive: - 100%: 150 days - 50%: 90 days - 25%: 30 days - 10%: 15 days ## Campaigns ⚑ Status: Current [gNODE](./community-rewards.md#what-is-gnode) is the coordinating Protocol's reward: used within the NodeOps Network to distribute incentives. Status: Completed Wave-2 Points Program concluded on December 11th 2024 as the snapshot date. For Wave-2, our Points Program was denominated in NPs. Every dollar spent within the Apps [NodeOps Network](https://cloud.nodeops.network/) and [NodeOps Console](https://console.nodeops.network/), earns 0.5 NPs. #### Past point collection opportunities - Stake & Earn: when you [stake $HYPE](/Get-Started/DeFi-Services/stake.md) with a NodeOps Validator Node. - Stake & Earn: when you [stake $BEAM](/Get-Started/DeFi-Services/stake.md) with a NodeOps Validator Node. - Restake & Earn: 250 NPs when you [delegate to NodeOps on EigenLayer](https://app.eigenlayer.xyz/operator/0xb5ead7a953052da8212da7e9462d65f91205d06d). - Sign up: Earn NPs by subscribing for Nodes on our [Console](https://console.nodeops.network/) - By completing the _Sign Up_ quest on the NodeOps Network Testnet, you'll receive 10 NPs. - **Connect Email** and receive 10 NPs. * **Refer & Earn** * Complete the _Refer & Earn quest_ on the NodeOps Network Testnet to receive 10 NPs. * Tell your friends about NodeOps and receive 10 NPs per referral. * **Signal Amplifier**Pass Privado ID verification * Complete _The_ _Signal Amplifier_ quest on the NodeOps Network Testnet and earn 7 NPs. * **Rate Us** * Complete the _Rate Us_ quest on the NodeOps Network Testnet and earn 10 NPs. #### Registration * **Register as a Provider** * Complete the _Register as a Machine Provider_ quest on the NodeOps Network Testnet and earn 1,000 NPs. * **Register as an AVS Operator** * Complete the _Register as an AVS Operator_ quest on the NodeOps Network Testnet and earn 25,000 NPs. * **Register as a Vendor** * Complete the _Register as a Vendor_ quest on the NodeOps Network Testnet and earn 2,000 NPs. #### Deployment * **Add a Machine** * Complete the _Add a Machine_ quest on the NodeOps Network Testnet and earn 2,500 NPs. You will be rewarded only for the first machine you add. * **Add a Template** * Complete the _Add a Template_ quest on the NodeOps Network Testnet and earn 3,000 NPs. You will be rewarded only for the first template you create. * **Deploy Nodes** * On the NodeOps Network Testnet, deploy Nodes with some of our ecosystem partners and earn NPs. Each partner will offer specific rewards for deployment. * **Deploy Template** * Complete the _Deploy a Template_ quest on the NodeOps Network Testnet and earn 500 NPs. Status: Completed Wave 1 Points Program concluded on December 11th 2024 as the snapshot date. For Wave 1, our Points Program was denominated in Node Points. For every dollar spent on our platform, you would receive 1 Node Point. #### **How to Collect Node Points?** You received Node Points for carrying out any of the following actions on our platform: * **Sign Up & Earn** * By signing up on our [Console](https://console.nodeops.network/), you would receive 10 Node Points. * **Complete Quests & Earn** * Complete our quests on [Intract](https://quest.intract.io/project/nodeops-flri4u) and you would stand to receive 250 Node Points. * **Invest & Earn -** The more you invested on the platform, the more you stood to earn. * For every dollar invested, you would receive a Node Point. * **Refer & Earn -** You were rewarded for telling your friends about NodeOps. * For your referral, they got 5% off on their first purchase and if they paid \$100, you got 100 Node Points. * **Restake & Earn** - Delegate to [NodeOps](https://app.eigenlayer.xyz/operator/0xb5ead7a953052da8212da7e9462d65f91205d06d) on EigenLayer. Rewards structured as follows: * 100 Node Points for one-time registration. * 10 Node Points per ETH per day for restaking. * 50 Node Points as a one-time referral reward. * 1 Node Point per ETH per day for referrals. * **Vote & Earn** - At NodeOps, we value user participation in [governance proposals](https://console.nodeops.network/governance) to ensure every vote counts. * For every vote, you earned 25 Node Points. * **Deploy Nodes and Earn** * You earned 1 Node Point for each new deployment on our Console. #### Node Points Tiers Our loyalty system was divided into four different tiers. Tiers are ranked, from top to bottom, in the following order: **Platinum**, **Gold**, **Silver**, and **Bronze**. Each tier has a specific multiplier. As you earned more Node Points and progressed through the tiers, the multiplier increased to enhance your rewards. Find below a detailed breakdown of the four tiers, their multipliers, and Allowlist Sale Eligibility. Additionally, the figure illustrates the four discount tiers: 1. Burn 799 Node Points to receive a 5% discount. 2. Burn 1,999 Node Points to receive a 10% discount. 3. Burn 3,499 Node Points to receive a 15% discount. 4. Burn 4,999 Node Points to receive a 20% discount. #### Results Wave 1 Node Points program concluded on December 11th 2024 as the snapshot date. It was a unilateral success and the numbers speak for themselves: * 11,400,000 Node distributed by 11th December, 2024. * 25,000 wallets eligible. * Airdrop Pool of 30,000,000 Wave 1 airdropped \$NODE allocated as claims. #### Wave3 Campaign: Genesis Airdrop #### Airdrop Status: 🏁 Completed **Show me the Previous airdrop campaigns** ##### What is the token address for Wave-1 airdrop \$NODE? Wave-1 airdrop \$NODE was the first non-transferrable community reward token [at token address 0xc0d2af6d32240494742ae486b9b73ec6dcc54aa1](https://etherscan.io/token/0xc0d2af6d32240494742ae486b9b73ec6dcc54aa1). It's made redundant by the new [\$NODE contract](/Tokenomics/node.md) and included in the airdrop allocations at a 1:1 ratio. ##### How do I earn the 25% airdrop bonus? UNO holders may deploy a [Orchestrator Node](/Get-Started/Cloud-Compute/node-orchestrator.md) to earn an additional 25% on the final 50% airdrop. > **Warning: Do not use a promo code to deploy the [Orchestrator Node](/Get-Started/Cloud-Compute/node-orchestrator.md), the system will only register the airdrop bonus if the spend is greater than 0.** ##### When will the \$NODE airdrop be distributed? [Eligibility checker](https://nodeops.network/case-studies/the-node-genesis-airdrop-proof-of-coordination) was activated 2025/06/16. The airdrop itself went live 2025/06/30 [NodeOps.Network/Airdrop](http://nodeops.network/airdrop). ##### Can I increase my airdrop share now? No. However, you can increase your [gNODE](/Guides/Community-Incentives/points) points by participating in the ecosystem. Once the airdrop page is live, you can no longer qualify. Don't worry though, this airdrop is 80% of the total airdrop allocation, reserving 20% for future airdrops. Also, you can still earn [gNODE](/Guides/Community-Incentives/points.md) by participating. Earn by [deploying Nodes](/Get-Started/Console/README.md), staking in the [Staking Hub](/Get-Started/DeFi-Services/stake.md), and [consuming](/Get-Started/Cloud-Compute/rent-compute.md) or [providing Cloud](/Get-Started/Cloud-Compute/Provide-Compute/register-to-provide.md) Compute. ##### How do referrals impact airdrop eligibility? If you’ve invited new users to NodeOps using your referral link and they’ve been active, your gNODE collection increases and hence your chances for more \$NODE. ##### Which wallet should I use to receive the airdrop? Use the EVM-compatible wallet connected to your NodeOps account. Make sure your wallet is funded with Arbitrum ETH for gas when claiming. ##### How do referrals impact airdrop eligibility? If you’ve invited new users to NodeOps using your referral link and they’ve been active, your [gNODE](/Guides/Community-Incentives/points) awards increase and hence your chances for more \$NODE. ##### What are the eligibility criteria for the NodeOps airdrop? Eligibility for the Airdrop spans six categories of participants, each of whom made verifiable contributions to the NodeOps Network before TGE: 1. NodeOps Users: includes both Wave-1 and Wave-2 Node Points (NPs) holders - Wave-1 Node Points holder: the earliest users of the NodeOps Network. As part of the Genesis Airdrop, you’ll receive the same \$NODE allocation previously received during the Wave-1 claim. - Wave-2 Node Points (NPs) holders: contributed during the Testnet phase by deploying workloads, onboarding machines, staking assets, and completing quests. Allocations for this group are based on their recorded on-chain activity across those key areas. 2. [UNO NFT](./UNO.mdx) holders: participants who minted a Universal Node Orchestrator (UNO) NFT. Eligibility and allocation depend on the amount of \$NODE used to mint, the number of minting phases joined, and the minting timestamp. Early minters benefit from accelerated vesting. 3. Compute providers: contributors who registered machines and maintained high uptime. Rewards were distributed across three tiers: - Registration Rewards for signing up as a provider - Machine onboarding rewards for machines with 99% uptime over at least 3 days - Performance rewards for maintaining that uptime over 7 days 4. AVS operators: users who [Actively Validated Services](/Learn/Glossary/avs) Nodes via EigenLayer on the NodeOps Network. These operators are eligible based on the number of AVS Nodes deployed. 5. [Staking Hub](/Get-Started/DeFi-Services/stake.md) participants: users who joined Stakedrop campaigns through the NodeOps Staking Hub by staking native or restaked assets. Rewards are based on the amount staked and the duration of participation. 6. NodeOps Social Community: individuals who participated in verified social quests and partner campaigns. ##### Do I have to claim my airdrop allocation? Yes, verified users will automatically receive the initial 10% in airdrop by completing the Privado ID step. The remainder of the allocation can be unlocked through various activities detailed on the [claim page](http://nodeops.network/airdrop). ##### Can I claim the airdrop from multiple wallets if I used more than one? No, you cannot claim from multiple wallet. Only one EVM compatible wallet which is associated with NodeOps can be used. ##### How do I claim my airdropped $NODE? You can claim it from the [airdrop claims page](http://nodeops.network/airdrop). ##### Do I need to pay the gas fee for the airdrop? Yes, you to claim the \$NODE you have to pay the gas fee in Arbitrum ETH. ##### On which network can I claim airdropped \$NODE? You can claim your \$NODE on Arbitrum. ##### Can I claim airdropped \$NODE? on mobile or only on desktop? You can claim from both. ##### I think my airdropped \$NODE? points/allocation are wrong β€” what can I do? The allocations should all be correct, but if you think you have still not received your allocation then please feel free to create a new ticket. ##### What if I missed airdropped \$NODE? verification but contributed? You will need to still complete the verification to claim the \$NODE allocation. ##### Can someone else claim airdropped \$NODE? tokens on my behalf? No, you cannot claim someone else's token or allow anyone else to claim on your behalf. ##### Is there a deadline to claim airdropped \$NODE? Yes, there's a 60 day claim window for airdropped \$NODE soon. We will share an update on our communication channels about the deadline, stay updated. ##### How does NodeOps prevent Sybil activity? NodeOps has implemented a robust, multi-layered [Sybil resistance](/Learn/Glossary/sybils) framework to ensure the airdrop goes to real contributors, not bots or opportunistic exploiters. This system combines behavioral clustering (KNN), interaction fingerprinting, metadata correlation, reputation-based scoring, and chain distribution analysis. Sybil-to-user association mapping further enhances detection. The result is a highly curated airdrop that protects the network’s integrity and rewards legitimate participation. ##### Is it safe to connect my wallet to the Airdrop site? Yes, as long as you use the official site. Always verify the URL: [http://nodeops.network/airdrop](http://nodeops.network/airdrop) NodeOps will never request your private keys or ask you to sign any suspicious transactions. Be cautious of phishing links or impersonator accounts across social media platforms. ##### Is $NODE claimable right now? Yes, the $NODE genesis airdrop is now live. ##### Is there a list of restricted countries? Yes. $NODE is not available to individuals or entities located in, under the control of, residents, or nationals of the following restricted jurisdictions: Afghanistan, Canada, China, Iran, Iraq, North Korea, Pakistan, Syria, Ukraine, the United States, the United States Minor Outlying Islands, and the US Virgin Islands. Additionally, \$NODE is unavailable to any individual or entity subject to sanctions or listed on any sanctions list maintained by the United Nations, the United States (including OFAC’s SDN and Entity Lists), the European Union or its Member States, the United Kingdom, or any other applicable governmental authority β€” regardless of location. For additional information, ensure to thoroughly review our [Terms and Conditions of the \$NODE airdrop](https://nodeops-public.hel1.your-objectstorage.com/airdrop-TnC.pdf). ##### What is an airdrop? An airdrop is a pre-allocated percentage of the project’s official token distributed to early supporters and community contributors. ##### When will the remaining 50% airdropped \$NODE? allocation be unlocked? In less than 2 weeks after TGE, you can unlock the remaining 50% allocation. ##### Can I still get the unlocked airdropped \$NODE? without participating in the campaigns? No, you only get 10% of your total allocation in your wallet, the remainder is unlocked by the campaigns associated with it. ##### Anything else I should know about the airdrop? Yes, here are some final reminders to ensure a smooth airdrop claim experience: - Use the **same wallet** for all airdrop-eligible actions and for claiming. - Once your wallet is registered, no changes can be made. Double-check before proceeding. - Only trust links from the official NodeOps domain: [nodeops.network/airdrop/checker](http://nodeops.network/airdrop). - All rewards are subject to NodeOps’ Sybil detection system to ensure fairness and ecosystem alignment. If you have any questions about your eligibility for the Genesis Airdrop, visit our [Terms and Conditions](https://nodeops.network/airdrop-TnC). ##### How can I become eligible if I am not eligible yet? The first Airdrop's eligibility season is complete. If you’re not eligible now, you can still participate in the NodeOps ecosystem and earn [gNODE](/Guides/Community-Incentives/points). Earn when you: - Become a [Template developer](/Guides/Marketplace/Configure-Compute/upload-template) and earn rewards when users run workloads via your code - [Provide Compute](/Get-Started/Cloud-Compute/Provide-Compute/README.md) - Earn higher rewards when you assign your machine/s workloads - [Verify the Protocol](/Get-Started/Cloud-Compute/node-orchestrator.md) - [Top up with credits](/Get-Started/Pay-for-Services/Readme.mdx): Burn \$10 or more \$NODE to earn Credits and unlock multipliers that boost your future rewards - [Deploy Nodes](/Get-Started/Console/README.md): Use the [NodeOps Console](https://console.nodeops.network/) to deploy Nodes or workloads - [Farm Compute](/Guides/Marketplace/farm) / [rent a machine](/Get-Started/Cloud-Compute/rent-compute.md): Lease Compute from the Marketplace - [Mint a UNO NFT](/Guides/Community-Incentives/uno#mint-uno): Mint a UNO NFT to gain ecosystem perks, future governance access, and airdrop eligibility - [Stake](/Get-Started/DeFi-Services/stake.md) \$NODE or supported tokens with [NodeOps Portal](https://portal.nodeops.network/) - [Launch UNO-enabled CU](/Guides/Community-Incentives/uno#uno-available-cu) ##### What do I need to claim airdropped \$NODE? You must: - Be eligible to claim - Connect your EVM-compatible wallet with enough Arbitrum ETH for gas at [nodeops.network/airdrop](http://nodeops.network/airdrop) - Pass the Privado ID verification ##### How do I claim the airdrop? 1. Connect your wallet at [http://nodeops.network/airdrop](http://nodeops.network/airdrop/) 2. If you are eligible, your $NODE allocation will display 3. Verify your eligibility with Privdo ID and start unlocking your allocation ##### What is the $NODE Genesis Airdrop? The \$NODE [Genesis Airdrop](http://nodeops.network/airdrop) is the token distribution event of the NodeOps Network. It has been designed to reward genuine contributors who helped build and grow the Network before the Token Generation Event (TGE). Rather than rely on arbitrary criteria or opportunistic campaigns, this Airdrop is rooted in Proof of Coordination β€” a principle that ties token rewards directly to meaningful actions taken across the NodeOps ecosystem. #### Past token reward waves ##### I already participated in Wave-1, what should I do next? You need to claim again. The current check page includes the allocation from Wave-1. Wave-1 \$NODE would be burned as the contracts have changed. Users who claimed during Wave-1 will receive the same \$NODE allocation as they did previously. Wave-1 points program refers to the first phase of our \$NODE activations for our earliest loyal users. ##### I already participated in Wave-2, what should I do next? You need to claim again. The current check page includes the allocation from Wave-2. Users who claimed during Wave-2 will receive the same \$NODE allocation as they did previously. Wave-2 points program refers to the second phase of our \$NODE activations for our earliest loyal users. ##### Will those who claimed $NODE in Wave-1 need to claim again? Yes, you need to claim again. The current check page includes the allocation from Wave-1 & -2. Wave-1 \$NODE will be burned as the contracts have changed. ##### How do I check if I have Wave-1 \$NODE? Wave 1 \$NODE was the first airdrop to early community participants. Use the drop-down to learn how to check your wallet for Wave 1 \$NODE. **Check your wallet for Wave 1 \$NODE ** 1. Ensure your wallet is connected with the Ethereum L1 Network. **Show me in MetaMask** 1.1 Sign in to your wallet and verify if **Ethereum Mainnet** is available in the network dropdown at the top of the MetaMask interface. 1.2 If Ethereum Mainnet is not listed, visit [ChainList](https://chainlist.org/) to add it: - Search for Ethereum Mainnet - Expand the drop-down arrow on Ethereum Mainnet's card - Select an RPC provider with good score and privacy (two green ticks) - Click **Add to MetaMask** - Approve the request **Show me** 2. Set up your wallet to display \$NODE: search for the \$NODE token, if you don't find it, manually Add \$NODE to your wallet. **Show me in MetaMask** 2.1 Open your MetaMask wallet, ensure you are on the Ethereum Network, and navigate to the **Tokens** tab. 2.2 Click the hamburger menu and click **+ Import tokens**. **Show me** 2.3 Select the **Custom Token** tab. 2.4 Enter the following details in **Token Contract address**: - **Token Contract Address**: `0xc0d2af6d32240494742ae486b9b73ec6dcc54aa1` - **Token symbol**: \$NODE 2.5 Click **Next**, then confirm by clicking **Import**. **Show me** ##### Can I convert Wave-1 $NODE to credits? No, the campaign is completed. Use the drop-down below to discover the details of the Wave-1 NODE to credits campaign. **Show me campaign details** > **Important: Purchase services with $NODE** During the campaign, Wave-1 airdrop $NODE could be exchanged for credits for use in NodeOps Console and the Marketplace. ##### $NODE to credit conversion decision matrix 1. Time decay: $r_{\max}(t) = 0.75 \times \exp\!\Bigl(-\ln(7.5)\frac{t}{T}\Bigr)$ 2. Rolling 24-Hour redemption volume $R_{24}(t) = \sum_{\tau = t - 24h}^{t} \text{USD\_disbursed}(\tau)$ 3. Linear Feedback (Raw): ${ \mathrm{raw}(t) = r_{\mathrm{base}} + \bigl(r_{\max}(t) - r_{\mathrm{base}}\bigr)\Bigl(1 - \frac{R_{24}(t)}{50{,}000}\Bigr) }$ 4. Final Conversion Rate: $r(t) = \max\!\Bigl(r_{\mathrm{base}}, \min\!\bigl(\text{raw}(t), r_{\max}(t)\bigr)\Bigr)$ ##### Conversion rate logic - **At any second** $t$, calculate the exponential decay maximum $r_{\max}(t)$ - **Measure** the last 24 hours’ redemption total $R_{24}(t)$ - **Calculate** the raw rate, clamp it between the base $r_{\mathrm{base}}$ and $r_{\max}(t)$ ###### Outcome - **Early in the Program**: $r_{\max}(0) = 0.75$. If redemptions are modest (< 50 k in the past 24h), the rate can stay near 0.75 - **Over Time**: $r_{\max}(t)$ decays to 0.10 at $t = T$ - **High Redemptions**: If the 24-hour sum $R_{24}(t)$ approaches 50 k, the rate is pushed toward the base rate 0.10 This system provides a dynamic, gamified conversion rate that both encourages participation when redemption is low and naturally tapers if redemption is high, while also enforcing a time-based decay from 0.75 to 0.10 USD. **Detailed Derivation of $NODE to USD Credits Conversion Model** ###### $NODE to USD credits conversion model The conversion rate in the standard model is calculated based on **time-dependent decay** and **daily claim volume**, ensuring that USD credits do not exceed the $5M daily limit. The main goals are to: - Start with a higher maximum conversion rate early in the program and decay it down to a lower rate over time - Adjust the actual conversion rate within that allowable range based on recent (24-hour) redemption volume ###### Element 1: Time decay We want the maximum allowable conversion rate $r_{\max}(t)$ to decay from an initial value $0.75$ USD/token at $t=0$ to a final value $0.10$ USD/token at $t = T$, where $T$ is the total program duration (e.g. 60 days in seconds). ###### Exponential Decay Form An exponential decay function is typically: $r_{\max}(t) = r_{\max}(0)\exp\!\bigl(-k\,t\bigr)$ where $k$ is chosen so that $r_{\max}(T) = r_{\max}(0)\exp\!\bigl(-k\,T\bigr) = r_{\min}$ Given: - $r_{\max}(0) = 0.75$ - $r_{\min} = 0.10$ - $T$ = total program length in seconds We solve for $k$: $$ 0.10 = 0.75 \exp(-k\,T) \quad\Longrightarrow\quad \exp(-k\,T) = \frac{0.10}{0.75} = \frac{1}{7.5} \quad\Longrightarrow\quad -k\,T = \ln\!\bigl(\tfrac{1}{7.5}\bigr) = -\ln(7.5) \quad\Longrightarrow\quad k = \frac{\ln(7.5)}{T} $$ Hence, ${r_{\max}(t) = 0.75 \exp\!\Bigl(-\ln(7.5)\frac{t}{T}\Bigr)}$ At $t=0$: $r_{\max}(0) = 0.75 \exp(0) = 0.75$ and at $t=T$: $r_{\max}(T) = 0.75 \exp\!\bigl(-\ln(7.5)\bigr) = 0.75 \times \frac{1}{7.5} = 0.10$ ###### Element 2: Daily redemption control We introduce a rolling 24-hour redemption volume function, denoted $R_{24}(t)$. This is the sum of USD disbursed from time $t-24\,\text{hours}$ to $t$. If $R_{24}(t)$ is small (less than 50,000 USD), we want the conversion rate to be closer to $r_{\max}(t)$; if $R_{24}(t)$ is large (β‰₯ 50,000 USD), we want the rate to drop toward a base rate $r_{\mathrm{base}}$. We define: - **Base Rate:** $r_{\mathrm{base}} = 0.10$ USD/token (the absolute floor) - **Current Max:** $r_{\max}(t)$ (the time-based maximum from above) - **24h Threshold:** 50,000 USD ###### 2.1 Linear Interpolation We can interpolate linearly between $r_{\mathrm{base}}$ and $r_{\max}(t)$ based on the fraction: $frac{R_{24}(t)}{50{,}000}$ - If $R_{24}(t) = 0$, we want $r(t) = r_{\max}(t)$ - If $R_{24}(t) = 50{,}000$, we want $r(t) = r_{\mathrm{base}}$ - For intermediate values, we interpolate linearly Thus the raw conversion rate before clamping is: $text{raw}(t) = r_{\mathrm{base}} + \bigl(r_{\max}(t) - r_{\mathrm{base}}\bigr)\Bigl(1 - \frac{R_{24}(t)}{50{,}000}\Bigr)$ ###### 2.2 Clamping We then clamp the result so it never goes below $r_{\mathrm{base}}$ or above $r_{\max}(t)$: ${r(t) = \max\!\Bigl(r_{\mathrm{base}}, \min\!\bigl(\mathrm{raw}(t), r_{\max}(t)\bigr)\Bigr)}$ Hence, the complete formula for $r(t)$ is: ${r(t) = \max\!\Bigl(r_{\mathrm{base}}, \min\!\Bigl( r_{\mathrm{base}} + \bigl(r_{\max}(t) - r_{\mathrm{base}}\bigr)\Bigl(1 - \frac{R_{24}(t)}{50{,}000}\Bigr), r_{\max}(t) \Bigr)\Bigr)}$ ## Can I earn NodeOps Points? Yes and no. Yes, in that [gNODE](./community-rewards.md#what-is-gnode) replaces all previous points. No, in that, all previous NodeOps Points programs are completed. The NodeOps Points programs offered users the opportunity to earn rewards for interacting and engaging with the NodeOps Console and the incentivized Testnet campaign, NodeOps Network. Points are an integral part of the NodeOps Network economy and have transitioned to gNODE. ## Can I earn NPs, and stNODE? No, the previous Points programs are all completed. The rewards previously included: - Node Points: Now sunsetted platform economy credits for the NodeOps Network - stNODE: A non-tradable and non-transferrable reward that was earned through staking exchanged for [$NODE](/Tokenomics/node.md), now replaced by [gNODE](./community-rewards.md#what-is-gnode) --- ### NodeOps FAQ > Find answers to common questions about NodeOps Network, including Node deployment, earning rewards, credits, and the Cloud Marketplace. URL: https://docs.nodeops.network/Learn/FAQ/faq ## How do I earn participation rewards on NodeOps? Any purchases you make in NodeOps earn [gNODE](/Learn/FAQ/community-rewards#gnode) rewards because, if you use a DePIN network, then you are the DePIN network. gNODE converts to [\$NODE](/Tokenomics) over time. This means that the longer you stick around, the more you ask the Network to do for you, the more you get back. What you can do depends on what you like. Deeply into dev and you will find (currently in closed beta) some interesting working environments. We have already released freemium tools such as [Security Hub](/Get-Started/Cloud-Tools/scan) as a taster. Wanna at-a-click only? We have tons for y'all. For example, you can [farm \$NODE](/Guides/Marketplace/farm) by renting a Machine from the Cloud Marketplace and earning a share in its workload revenue. Each machine earns incentives: - Registration reward: Earn [gNODE](/Guides/Community-Incentives/points) for signing up and adding at least 1 machine that provides a minimum of 7 days of uptime - Availability reward: Earn [gNODE](/Guides/Community-Incentives/points) rewards for each machine that maintains service > **Tip: :::** > Learn about all NodeOps' [core products and services](/Core-Services) and get involved. ## How do I deploy a Node on NodeOps? Great question. - To subscribe to deploy a Blockchain or Protocol Node at-a-click, use [NodeOps Console](https://console.nodeops.network/) and be sure you have everything you need such as any required NFT license or native tokens - To subscribe to deploy a template at-a-click, use the [NodeOps Cloud Marketplace](https://cloud.nodeops.network/) The Marketplace serves templates that will run Blockchain and Protocol Nodes, in fact what you will find in the Marketplace is limitless. You see, pretty much every product and service you select from NodeOps runs as a Node. You have a full DevOps team under the hood when you run your workloads, leaving you to concentrate on what matters to you! ## \$NODE ### What will I get with \$NODE staking? Stake \$NODE to earn \$NODE with [NodeOps Portal](Learn/Products/DeFi-Services/staking.md). ## NodeOps Console ### What does NaaS mean in terms of Node delegation? NaaS stands for Node-as-a-Service. Typically, running a digital Node requires specific hardware, reliable internet connectivity, and technical knowledge (Windows or Linux). With NaaS, particularly with NodeOps, you can outsource all these technical requirements. [NodeOps Console](/Guides/Console/README.md) handles hardware, Node installation, and updates, and ensures 100% uptime. With just a few clicks, your Node will be up and running without any technical expertise needed. ### Can I ensure 100% uptime using NodeOps as a NaaS provider? Asolutely. With several years of experience in blockchain and Node management, NodeOps maintains [thousands of Nodes](https://dune.com/nodeops/stats). We offer dedicated customer support and high-spec hardware to ensure smooth Node operations and 100% uptime. ### Why should I choose NodeOps Console to run Nodes? By running your Node with NodeOps, you earn Node Points, which can be redeemed later. ### I'm a complete novice, can I still set up a Node? Absolutely. We provide [comprehensive tutorials](/Guides/Console/README.md) in text and video formats to help you set up your Node without issues. Additionally, our support team is available via email and our ticketing system. We also offer 1-on-1 meetings with Node operators if needed. ### My Node expired and I cannot see it in my plans You have a 7-day grace period after your Node expires before it gets deleted. Once it's deleted, you’ll need to purchase a new plan from the Node Deployment section and complete the delegation process again. ## NodeOps Cloud Marketplace ### Are the deployments on NodeOps Network as same as Node Deployments on Console? Yes they are very similar, the difference being that the onboarding of partners and you, the user, is handled by contracts on Arbitrum rather than a centralized service in the case of Console. ### I cannot see the referral points getting updated You will see the points updating every hour. ## General queries ### Where did my credits go? I had credits in my account and tried making a payment, but couldn’t complete it, now I do not see the credits, what should I do? Wait for approximately 30 mins. The initiated payment session needs to go through the full fall-back cycle for the credits to register in your dashboard again. ### Can I withdraw credits from the NodeOps Dashboard? No, credits cannot be withdrawn from the platform. They can only be used for services offered within the NodeOps ecosystem. ### What happened to Atlas Network? The proof of concept campaign, Atlas Network, was so successful that NodeOps decided to take the plunge and bring the concept in-house rather than separate the business risks. We are in it to win it peeps! GM NodeOps Network. ### Why does some of the docs content mention Atlas Network? Atlas Network was a proof of concept campaign run by NodeOps. Bear with us as we rebrand this campaign to be an in-house effort. ### Why does some of the code mention Atlas Network? Atlas Network was a proof of concept campaign run by NodeOps. Bear with us as we rebrand this campaign to be an in-house effort. ## What next? - Consider learning more about the [UNO NFTs](./UNO.mdx) - Consider learning more about the role of [\$NODE](/Tokenomics/node.md) --- ### NodeOps Portal FAQ > Get answers about NodeOps Portal features including $NODE staking, bridging, governance voting, gNODE redemption, and UNO minting. URL: https://docs.nodeops.network/Learn/FAQ/portal ## What is the NodeOps Portal for? The [NodeOps Portal](/Guides/Portal/) lets you work with \$NODE. You can: - [Vote on governance proposals](/Tokenomics/governance#vote-on-governance-proposals) - [Stake](/Get-Started/DeFi-Services/stake) - [Transfer](/Guides/Portal#transfer-with-nodeops-portal) - [Bridge](/Guides/Portal#bridge-with-nodeops-portal) - [Mint UNO](/Guides/Portal#work-with-uno) ## Do I need to pay transaction gas fees in Portal? Yes, you have to pay the gas fee to sign the transactions. ## Are there any extra incentives to bridge, stake and transfer $NODE via this portal? There are rewards for [staking](/Get-Started/DeFi-Services/stake) and [converting $NODE to credits](/Get-Started/Pay-for-Services#step-1-optional-top-up-your-credits). ## How much APY do I earn when staking $NODE via the Portal? The APY is set when you stake $NODE. While it may differ over different campaigns, the APY you lock at is fixed. ## Staking with Portal ### What is stakedrop? Stakedrop is a novel dual incentive program from the NodeOps team which brought you state of the art [NaaS](/Guides/Console/README.md), [Compute](/Learn/Products/Cloud/README.md), and RPC services. [Portal](Learn/Products/DeFi-Services/staking.md) is a platform where you can stake your supported tokens, and receive a stake drop. This means that, while earning the associated APR, you also earn [gNODE](/Guides/Community-Incentives/points.md) which can later be redeemed for [\$NODE](/Tokenomics/node.md) tokens. ### How long do staking campaigns last? Each campaign with the integrated projects will have their own timeline. For example, each Hyperliquid campaign will last for 120 days while each campaign with Beam is for 16 days. ### How do I participate in the staking campaigns? To participate: - Connect with your non-custodial wallet containing the said token - Register on the Portal at [Portal.NodeOps.network/](https://portal.nodeops.network/) ### Do I need technical knowledge to participate in a staking campaign? No, you don’t need advanced technical knowledge. The process is straightforward: you stake your tokens on a NodeOps Validator by registering on the [Portal.NodeOps.network/](https://portal.nodeops.network/). The Portal guides you with its intuitive flow, these docs provide [step-by-step instructions](/Get-Started/DeFi-Services/stake.md), and support is available if you encounter issues. ### Is there a minimum or maximum amount of tokens I need to stake? There's no specified minimum or maximum amount of tokens to stake in this campaign. However, the more tokens you stake, the more [gNODE](/Guides/Community-Incentives/points.md) points you can earn, increasing your potential [\$NODE](/Tokenomics/node.md) rewards. ### Can I unstake my tokens during the campaign? Each campaign has its own period, and staked tokens are typically locked for the duration to earn [gNODE](/Guides/Community-Incentives/points.md) points. After the campaign ends, you can redeem your gNODE points based on the unlock schedule. Check the [Portal](https://portal.nodeops.network/) for specific unstaking policies. ### What are gNODE points? [gNODE points](/Guides/Community-Incentives/points.md) are rewards earned by staking your tokens during a campaign. These points can be redeemed for $NODE tokens after the campaign concludes. ### What is the total reward pool for the campaign? The total reward pool is dependent on the partner. For Hyperliquid we offered 1,000,000 gNODE points for the first 120 days campaign while for Beam we offered 500,000 gNODE points for Beam's epoch 1 (which ran for 30 Days; ending May 1st 2025). ### When can I redeem my gNODE points for \$NODE? Redemption of [gNODE points](/Guides/Community-Incentives/points.md) to [\$NODE](/Tokenomics/node.md) will begin after the conclusion of the respective campaign/s. ### What is the redemption cycle for gNODE to \$NODE? The redemption of [gNODE points](/Guides/Community-Incentives/points.md) to [\$NODE](/Tokenomics/node.md) follows a tiered unlock schedule: - 100%: 150 days - 50%: 90 days - 25%: 30 days - 10%: 15 days ### Can I redeem all my gNODE points at once? No, redemption follows the unlock schedule above. You can redeem a portion of your [gNODE points](/Guides/Community-Incentives/points.md) based on the time elapsed since the campaign ends, with full redemption available after 150 days. ### What is \$NODE, and why is it valuable? [\$NODE](/Tokenomics/node.md) is the native token of the NodeOps ecosystem, which may be used for governance, rewards, or other functionalities in the future. By earning [gNODE points](/Guides/Community-Incentives/points.md), you’re positioning yourself to receive [\$NODE](/Tokenomics/node.md) tokens, which could have value as the NodeOps platform grows. ### Where can I get more information or support? Visit the Portal at [Portal.NodeOps.network/](https://portal.nodeops.network/), leverage the [Portal guides](/Guides/Portal/), or contact the NodeOps team through official channels listed in the footer of this site for further assistance. ### How do I unstake my $BEAM? Follow the [unstaking guide](/Guides/Portal/README.md#unstake-your-tokens) to understand the unstaking flow. ## What next? - Follow the [Get Started guide](/Get-Started/DeFi-Services/stake.md) to stake - Follow the [Admin guide](/Guides/Portal) to manage your stakes and your \$NODE - Learn more about [HyperLiquid](https://hyperfoundation.org/) - Learn more about [Beam](https://nodes.onbeam.com/) --- ### Compute provider > FAQ for NodeOps Compute providers covering machine registration, bonding requirements, workload status, and troubleshooting. URL: https://docs.nodeops.network/Learn/FAQ/provider ### Where is the provider dashboard? Once you have [registered a machine](/Get-Started/Cloud-Compute/Provide-Compute/register-a-machine.md), you may log into the [provider dashboard](https://cloud.nodeops.network/). ### After adding a machine, why is it in Pending/Configuring status? You need to do the setup txn, please ensure you have enough ETH on Arbitrum for gas fees. ### Why is my machine rejected? Your machine will be rejected if: - It runs workloads in addition to the NodeOps Network assigned loads - If [SWAP](https://wiki.archlinux.org/title/Swap) is enabled ### Why there is no workload on my machine? In the early stages of NodeOps Network, we are testing the Compute onboarding process. The next stage will add workload on the provided Compute. ### When will I get deployments on my machine? In the early stages of NodeOps Network, we are testing the Compute onboarding process. We are rolling out workloads on the provided Compute. ### Why am I getting a copy error? An error such as `cannot create regular file '/usr/local/bin/nn-provider': Permission denied` means you didn't create a user account at root for NodeOps Cloud with the correct permissions to run the code. You can get around this on Ubuntu by downloading the script locally and then running these with `sudo`. That means: ``` curl -L | sh -s - ZxEsuA******************zAJ6 ``` becomes ``` curl -L -o nn-installer.sh chmod +x ./nn-installer.sh sudo sh nn-installer.sh ZxEsuA******************zAJ6 ``` ### Why do I have a "non-schedulable" status? Machines that successfully onboarded, but since then are not working correctly are moved to "non-schedulable" status. The underlying reason is often due to networking issues on the provider's side. See all the possible [machine statuses](../../Guides/Marketplace/Manage-Machines/machine-status.md). ### Why do I have to bond to become a provider? For Mainnet, bonding \$NODE is an economic security measure that ensures only earnest Compute providers can contribute to the NodeOps Network. It also ensures providers act in the best interest of the NodeOps Network by adding reliability and efficiency. ### How much do I have to bond to become a provider on NodeOps Cloud Marketplace? - 2000 \$NODE + 200 \$NODE for every CU ### What are the minimum requirements for machines on NodeOps Cloud Marketplace? > **Info: Machines **must**** Comply with the minimum hardware and port requirements: - CPUs or vCPUs: β‰₯2 - GB RAM: β‰₯4 - SSD storage: β‰₯80GB NVMe Storage - Network bandwidth: β‰₯1Gbps unlimited - Uptime: β‰₯ 99% - OS: Debian (12+) or Ubuntu (22.04+) installation with: - Linux kernel 6.7+ - Latest security patches - Allow traffic on ports: - UDP 8472,51820 - TCP 10250 - Public static IPv4 address - Run the Protocol at root > **Warning: Machines **must not**:** - Run additional workloads - Have third-party applications or monitoring agents installed - Enable [SWAP](https://wiki.archlinux.org/title/Swap) - Be exposed to intervention with the workload or machines > **Info: Run at root** NodeOps Network's integration must be run directly on a machine at root: - You can't run it in Docker - Don't run it on a homelab --- ### Compute Templates FAQ > Answers to common questions about NodeOps Cloud templates, including pricing, resource allocation, Docker images, and publishing. URL: https://docs.nodeops.network/Learn/FAQ/templates ### How do developers earn with templates? > **Info: Monetize your templates** In the boostrapping phase of the Network, templates earn 20% of the workload fee. > This allows early template contributors to enjoy a significant incentive should their template prove popular. ### How do I submit a template? [Learn how to submit templates for consideration](/Guides/Marketplace/Configure-Compute/upload-template.md). ### Can a template expose an application to the internet? Yes. If you set **expose: true** for a port in your template, the application will be accessible externally. Example: ``` ports: - containerPort: 8888 protocol: TCP expose: true ``` This means users can access the application via a generated URL after deployment. > **Important: Service limitation** Only **one service per template** can be exposed externally. ### How can I allow users to provide input values in my template? You can use **placeholders** `({{.ENV}})` in your template to allow users to provide values during deployment. Example: ``` env: - name: APP_ENV value: "{{.ENV}}" ``` When a user deploys this template, they will be prompted to provide a value for APP_ENV. Use this approach for any configuration that varies per deployment such as: - API keys - Wallet addresses - Database credentials ### What resources can I define in my template? You can specify **CPU and memory allocations** under `resourceUsage`. Example: ``` resourceUsage: idle: cpu: 200 # 0.2 CPU cores memory: 400 # 400MB RAM ``` This defines the minimum required resources when the application is idle. ### Are there template upgrade constraints? Yes, upgrades don't include: - Adding new services - Modifying resource allocations for existing services Such amendments require resubmission of a template as a new entitiy. ### Can users modify my template after deploying it? No, users can't modify the template itself after deployment. However, they can provide values for placeholders `({{.ENV}})` during deployment. ### How do I price my template? The pricing is linked to **resource usage** (CPU & memory). You can define minimum resource requirements in your template, which will determine the cost. ### What happens if my template uses a private Docker image? Your template **must use a public Docker image**. Private images **cannot be pulled** by users. If you are using the Private Docker Images you should provide us with the credentials to access those images. ### What happens if my template does not specify a public port? If `expose: false` or no port is defined, the application will run **internally** but will **not** be accessible from the internet. This is useful for background services. ### Can I specify default environment variables in my template? Yes, you can define **both static and user-provided environment variables**. Example: ``` env: - name: STATIC_ENV value: "fixed_value" - name: DYNAMIC_ENV value: "{{.USER_INPUT}}" ``` - STATIC_ENV has a fixed value - DYNAMIC_ENV will be set by the user during deployment ### What happens if a user provides invalid values for placeholders? The system will **validate user inputs** before deployment. If a required value is missing or invalid, the user will be asked to correct it. ### Can I provide documentation with my template? Yes! It's recommended to include **a README or metadata** explaining: - What the template does - Required user inputs - Expected behavior after deployment This improves usability for those deploying your template. ### How can I test my template before publishing it? Before publishing your template, you should **deploy and test it** in the Marketplace to ensure: - It **runs correctly** without errors - **Placeholder variables** `({{.ENV}})` are correctly substituted during deployment - **Resource constraints** (CPU, memory) are within allowed limits and function as expected > **Tip: Additionally, a **playground for contributors** will soon be available, allowing you to conduct thorough testing before publishing your template. This feature will help you validate your template in a controlled environment before making it publicly available. πŸš€** ### What should I do if my template fails to deploy? - Check if the Docker image is publicly accessible - Verify placeholder variables `({{.ENV}})` are correctly defined - Ensure resource constraints (CPU, memory) are within allowed limits If issues persist, review logs or update your template. ### Can I remove my template after publishing? Yes, you can **remove or archive** your template from the Marketplace if it's no longer needed. ### Can I update a template after publishing? Yes. To push out an updated version of your NodeOps template, push a new tag to your Docker image with the command: `docker push {username}/{template)name}:tagname` Then, from the NodeOps Marketplace console, navigate to **My Templates** and select your template, update the YAML version number and submit for re-review. --- ### $NODE Token FAQ > Everything about the $NODE token: utility, contract address, exchanges, staking, governance, burn mechanics, and earning methods. URL: https://docs.nodeops.network/Learn/FAQ/token ## FAQ ## What is $NODE? [\$NODE](/Tokenomics/node.md) is the native utility token of the NodeOps Network. ## What is the utility of \$NODE? \$NODE is the native utility token of the NodeOps Network. It's part of the coordination layer enabling [Node deployments](/Get-Started/Console/README.md), [Compute purchases](/Get-Started/Cloud-Compute/rent-compute.md), [staking incentives](/Get-Started/DeFi-Services/stake.md), [governance](/Tokenomics/governance), and [more](/Core-Services). ## What is \$NODE's contract address? | **Contract details** | **Address** | | --- | --- | | $NODE Token Contract: Ethereum (ERC-20) | [`0x2f714d7b9a035d4ce24af8d9b6091c07e37f43fb`](https://etherscan.io/token/0x2F714d7b9A035d4ce24af8d9b6091c07E37f43Fb) | | $NODE Token Contract: Arbitrum (LayerZero) | [`0x2F714d7b9A035d4ce24af8d9b6091c07E37f43Fb`](https://arbiscan.io/token/0x2F714d7b9A035d4ce24af8d9b6091c07E37f43Fb) | | $NODE Token Contract: Binance Smart Chain (LayerZero) | [`0x2F714d7b9A035d4ce24af8d9b6091c07E37f43Fb`](https://bscscan.com/token/0x2F714d7b9A035d4ce24af8d9b6091c07E37f43Fb) | ## Where can I lean about \$NODE from a third-party source? [CoinMarketCap](https://coinmarketcap.com/currencies/nodeops/) details \$NODE and NodeOps. ## What CEX support \$NODE? \$NODE may be traded on several popular exchanges, including: - [Binance](https://www.binance.com/en/binancewallet) Alpha - [Bitget](https://www.bitget.com/) - [BingX](https://bingx.com/) - [Bitmart](https://www.bitmart.com/en-US) - [Bitunix](https://www.bitunix.com/) - [Bybit](https://www.bybit.com/trade/usdt/NODEUSDT) - [DigiFinix](https://www.digifinex.com/) - [Gate](https://www.gate.com/trade/NODE_USDT) - [HTX](https://www.htx.com/) - [Kraken](https://www.kraken.com/) - [Kucoin](https://www.kucoin.com/) - [LBank](https://www.lbank.com/) - [MEXC](https://www.mexc.com/acquisition/custom-sign-up) - [Pancakeswap](https://pancakeswap.finance/) ## Can anyone buy \$NODE? No. $NODE is not available to individuals or entities located in, under the control of, residents, or nationals of the following restricted jurisdictions: Afghanistan, Canada, China, Iran, Iraq, North Korea, Pakistan, Syria, Ukraine, the United States, the United States Minor Outlying Islands, and the US Virgin Islands. Additionally, \$NODE is unavailable to any individual or entity subject to sanctions or listed on any sanctions list maintained by the United Nations, the United States (including OFAC’s SDN and Entity Lists), the European Union or its Member States, the United Kingdom, or any other applicable governmental authority β€” regardless of location. For additional information, ensure to thoroughly review our [Terms and Conditions of the \$NODE airdrop](https://nodeops-public.hel1.your-objectstorage.com/airdrop-TnC.pdf). ## How do I see the $NODE in my wallet? [NodeOps Portal](/Guides/Portal) lets you view your \$NODE balance. **Show me a quick tutorial** **Show me video** 1. Log in to the [portal.nodeops.network/transfer](https://portal.nodeops.network/transfer) with your [relevant wallet](/Learn/Products/DeFi-Services/staking#supported-wallets). 2. Select the chain your \$NODE is on. > The airdropped \$NODE is on Arbitrum One. **Show me** 3. You balance now shows at the top right of the dashboard. **Show me** Alternatively, you can add a custom token to most wallets: **Show me a quick tutorial** Wallets differ slightly in their flows, this demonstration uses MetaMask. 1. Log in to your wallet. 2. From the **Tokens** tab, select the hamburger menu and click **Import tokens**. 3. Click **Custom token**, and select the chain your \$NODE is on. 4. Copy the \$NODE token address and enter it into the **Token contract address** field: > This demo shows Arbitrum One's \$NODE. 5. If the token symbol comes up as NODE, you're good to go, click **Next**. Congratulations, your \$NODE holdings are now visible in your wallet. ## Will there be a public sale or IDO? Yes, the IDO went live in June 2025 and was exclusive to Binance Wallet via PancakeSwap. ## Which wallet should I use to receive the airdrop? Any EVM-compatible wallet connected to your NodeOps account is valid. Make sure your wallet is funded for gas when claiming. ## How do I earn \$NODE? [gNODE](/Guides/Community-Incentives/points) is earned through Protocol participation allowing users to later convert this to \$NODE: - Become a [Template developer](/Guides/Marketplace/Configure-Compute/upload-template) and earn rewards when users run workloads via your code - [Provide Compute](/Get-Started/Cloud-Compute/Provide-Compute/README.md) - Earn higher rewards when you assign your machine/s workloads - [Verify the Protocol](/Get-Started/Cloud-Compute/node-orchestrator.md) - [Top up with credits](/Get-Started/Pay-for-Services/Readme.mdx): Burn \$10 or more \$NODE to earn Credits and unlock multipliers that boost your future rewards - [Deploy Nodes](/Get-Started/Console/README.md): Use the [NodeOps Console](https://console.nodeops.network/) to deploy Nodes or workloads - [Farm Compute](/Guides/Marketplace/farm) / [rent a machine](/Get-Started/Cloud-Compute/rent-compute.md): Lease Compute from the Marketplace - [Mint a UNO NFT](/Guides/Community-Incentives/uno#mint-uno): Mint a UNO NFT to gain ecosystem perks, future governance access, and airdrop eligibility - [Stake](/Get-Started/DeFi-Services/stake.md) \$NODE or supported tokens with [NodeOps Portal](https://portal.nodeops.network/) - [Launch UNO-enabled CU](/Guides/Community-Incentives/uno#uno-available-cu) ## What does holding \$NODE mean? \$NODE holders can: - [Trade \$NODE](/Learn/FAQ/token#what-cex-support-node) - Convert [\$NODE into credits](/Get-Started/Pay-for-Services#step-1-optional-top-up-your-credits) for use in-app - [Engage in governance](/Tokenomics/governance#vote-on-governance-proposals) ## Does holding \$NODE give me governance rights? Yes \$NODE and UNO holders are eligible to [vote](/Tokenomics/governance#vote-on-governance-proposals). - Standard participation: staked and bonded $NODE tokens carry equal voting weight (1 token = 1 vote). - Universal Node Orchestrator (UNO) Operator participation: each UNO operator receives a voting weight of 2,000 $NODE tokens for every UNO NFT they hold. ## What are NPs? [gNODE](/Guides/Community-Incentives/points) replaces NPs. NPs (Node Points) were earned by users for participating in the NodeOps ecosystem. For every $1 spent, you earned 0.5 NPs. They also offer allowlisted access to future Node sales and potential ecosystem airdrops. ## What happens to my Wave-1 airdropped \$NODE? Wave-1 \$NODE allocations have already been included in the amounts visible on the eligibility checker page. As of now, Wave 1 tokens will remain non-transferable until further updates are announced. ## What is Wave-1 & Wave-2? Wave-3: [gNODE](/Guides/Community-Incentives/points) replaces the previous reward points. Wave-1 \$NODE airdrop was a non-transferable reward token for early users. Wave-2 was the next phase of \$NODE distribution to reward the community that has committed to the project since Wave-1. ## Is \$NODE transferable? βœ… Once \$NODE is listed on exchanges, all IDO and airdropped tokens will be transferable. Other tokens, however are still under [locks or vesting](/Tokenomics/node#distribution). ## Which exchanges can I trade \$NODE on? From June 30th 2025, \$NODE became available on selected exchanges, over time more exchanges listed the token for sale. \$NODE may be traded on several popular exchanges, including: - [Binance](https://www.binance.com/en/binancewallet) Alpha - [Bitget](https://www.bitget.com/) - [BingX](https://bingx.com/) - [Bitmart](https://www.bitmart.com/en-US) - [Bitunix](https://www.bitunix.com/) - [Bybit](https://www.bybit.com/trade/usdt/NODEUSDT) - [DigiFinix](https://www.digifinex.com/) - [Gate](https://www.gate.com/trade/NODE_USDT) - [HTX](https://www.htx.com/) - [Kraken](https://www.kraken.com/) - [Kucoin](https://www.kucoin.com/) - [LBank](https://www.lbank.com/) - [MEXC](https://www.mexc.com/acquisition/custom-sign-up) - [Pancakeswap](https://pancakeswap.finance/) ## Is \$NODE inflationary or deflationary? \$NODE is initially inflationary with a dynamic emission model with capped daily supply. The early inflationary emissions exist to reward early contributors. However, a reducing emission algorithm with the associated burn mechanism will offset this, pushing the system toward a deflationary process. Learn more from the [$NODE tokenomics](Tokenomics/node.md). ## \$NODE burns ### Why doesn't the burn wallet use 0xdead? The burn wallet's custom address is provably irrecoverable and hardcoded in the $NODE contract for added security. It functions identically to 0xdead but with enforced immutability. We created a dedicated burn address because NodeOps’ tokenomics require ongoing, verifiable burn events. By anchoring all burns to a single, hard-coded address, the community can easily track every transaction in one place, ensuring maximum transparency and auditability over time. ### How can I verify \$NODE burns myself? Visit the burn transaction link [0x2080FeE444118AFCe30fCb749802C18c0a980dB7](https://etherscan.io/address/0x2080FeE444118AFCe30fCb749802C18c0a980dB7), inspect the balance, and check the [$NODE contract](https://etherscan.io/token/0x2F714d7b9A035d4ce24af8d9b6091c07E37f43Fb) for transfer restrictions. ### Will all \$NODE burns use the same address? Yes, all future burns will go to the address [0x2080FeE444118AFCe30fCb749802C18c0a980dB7](https://etherscan.io/address/0x2080FeE444118AFCe30fCb749802C18c0a980dB7). ### What is a burn address? A burn address is a special address where tokens sent and can never be recovered. It is not a wallet, not a deployable contract, and has no private key β€” making it mathematically impossible to retrieve tokens once burned. ### How much \$NODE was burned in the first event? 20,365,011.90 \$NODE was permanently burned, equal to 3% of total supply and 18.02% of circulating supply. ### How does the burn tie into $NODE tokenomics? Under the [dynamic mint-and-burn model](/Tokenomics/node#dynamic-mint--burn), all new emissions are tied to verifiable network revenue. Tokens are minted only when backed by usage, and burned as part of ongoing cycles. Every burn flows through the [official address](https://etherscan.io/address/0x2080FeE444118AFCe30fCb749802C18c0a980dB7), making supply adjustments transparent, enforceable, and onchain-verifiable. ### How does the \$NODE burn approach improve on conventional burn models? Many protocols burn tokens as a symbolic gesture or by convention. NodeOps enforces burns at the contract level and locks them to a dedicated address. This removes trust assumptions, eliminates manipulation risks, and provides onchain proof that every reduction is permanent. ### Are \$NODE burn rates fixed? No. Burn rates dynamically tuned to network usage, with parameters to be set and refined through governance. What we’re implementing isn’t a separate or single instance β€œProof of Burn” model, but rather the next phase of implementing our dynamic mint-and-burn tokenomics. As adoption and revenue scale, the NodeOps economy ensures supply adjusts transparently and sustainably in line with the growth of NodeOps Network. --- ### UNO > Frequently asked questions about UNO NFTs on NodeOps, including minting, rewards, Node orchestrator delegation, and eligibility. URL: https://docs.nodeops.network/Learn/FAQ/UNO ## What is UNO? > **Tip: TL;DR** - Holding UNO offers some of the same properties as holding [$NODE](/Tokenomics/node.md) - UNO holders are eligible to run [Orchestrator Nodes](/Learn/Ecosystem/nodeorchestrator) - UNO holders are [eligible to vote](/Tokenomics/governance#eligible-participants) as part of the DAO - Purchase UNO from [portal.nodeops.network](http://portal.nodeops.network) and mint on Ethereum, Arbitrum, or Base ### Overview UNO is a Flagship NFT collection, released for public sale in March 2025. UNO confers the following utility to holders: - Revenue share: Quarterly share from NodeOps Network profits - Allowlists: Ecosystem allowlists and early access to [Console](/Guides/Console/README.md) projects - Platform access and discounts: Save on Node Deployments and migrations and get beta access to new features. > **Note: UNO rewards have dropped** Each UNO NFT grants access to one 2CU machine to allow you to [farm its workload rewards](/Guides/Marketplace/farm.md) in [gNODE](/Guides/Community-Incentives/points.md). - Favourable unlocks: Earn the rights to early \$NODE unlocks and more favourable vesting schedules by being an UNO holder and active on the ecosystem - Governance: Influence network decisions along with \$NODE holders - Auto-bonding: UNO holders that become Compute providers will have \$NODE bonded on their behalf > **Important: UNO properties** - Non-transferrable for 1 year from mint ## Current UNO Node Operator Campaign ### What is the daily reward for UNO Season 2? 24 gNODE per UNO per day, settled weekly. ### What is the duration of the UNO Season 2 Campaign? The UNO Season 2 Campaign runs from 1st - 30th September inclusive. ### How do the UNO Node Operator rewards work? UNO NFTs represent your license to participate in the NodeOps ecosystem. When you delegate your UNO NFT an Orchestrator Node, your rewards depend on how responsive that operator is throughout the day. ### What does it mean that UNO rewards are an epoch-based activity? The system runs on 24 epochs per day (1 epoch = 1 hour). Each epoch, Orchestrator Nodes are asked to perform specific tasks to verify the Compute Marketplace services. Operators that respond correctly and on time have their activity recorded. You earn if your Node responds. In each epoch, your account is credited with rewards for that hour. At the end of the day, you can earn up to 30 $gNODE per day per UNO license β€” as long as your Orchestrator Node was consistently responsive. If the node misses epochs, your reward will be proportionally reduced. ## UNO general information ### How do I use UNO to unlock my airdrop bonus? [Deploy an Orchestrator Node](/Get-Started/Cloud-Compute/node-orchestrator.md) to unlock your bonus. ### I can't see the UNO NFT in my wallet, what should I do? If your wallet doesn't support NFTs, try connecting your wallet with a third-party such as [NFTscan](https://www.nftscan.com/), [OpenSea](https://opensea.io/), or check the explorer for the network you selected while purchasing the ticket. ### Will UNO be available on secondary marketplaces after minting? No, until the unlock period completes, UNO won't be available anywhere else apart from the NodeOps platform. The supply is limited to 10k NFTs. ### Where can I buy UNO? Mint your own UNO via [NodeOps Portal](/Guides/Community-Incentives/uno#mint-uno). ### What currency can I purchase UNO in, and how will gas be deducted? You can pay with multiple chains and token options available with our payment partner. You must cover the cost of gas, which will vary between networks. ### Are there any restricted geographies unable to buy UNO? You must not be (i) a citizen or resident of, or located in: Algeria, Bolivia, Morocco, Nepal, Pakistan, Vietnam, Afghanistan, Canada, China, Bangladesh, Cuba, Iraq, Iran, Egypt, North Korea, Republic of China, Syria, Sudan, Zimbabwe, Tunisia, United States (and its territories), Ukraine, Belarus, Albania, Burma, Central African Republic, Democratic Republic of Congo, Lybia, Somalia, Yemen, and Nepal ("Restricted Jurisdictions") or any other country, jurisdiction, a geographic area that is subject to U.S. or other sovereign country sanctions, or (ii) subject to sanctions or otherwise designated on any list of prohibited or restricted parties, including but not limited to the lists maintained by the United Nations Security Council, the U.S. Government (i.e., the US Department of the Treasury's Office of Foreign Assets Control ("OFAC"), the Specially Designated Nationals List and Foreign Sanctions Evaders List of the U.S. Department of Treasury and the Entity List of the U.S. Department of Commerce), the European Union or its Member States, the United Kingdom, or other applicable government authority. ### What chain does the UNO mint happen on? You can select from Ethereum, Arbitrum, and Base. ### What Cloud Compute access does UNO provide? Each UNO allows the holder access to a 2CU machine in the Cloud Network. ### What happens to my alloted 2CU machine after renewal lapses? Cloud Compute must be set up and then the machines must be renewed monthly. If you run multiple machines, each one must be renewed individually. ### Can I earn by holding an UNO? Yes, as an UNO holder you can earn [gNODE](/Guides/Community-Incentives/points) by [verifying the Compute](/Get-Started/Cloud-Compute/node-orchestrator.md) added to the Cloud Marketplace by [providers](/Get-Started/Cloud-Compute/Provide-Compute/README.md). ### Am I eligible for more Compute if I hold multiple UNO? Yes, the allowance is per UNO. Minted 3 UNO NFTs? You’re eligible for three 2CU machines. ### If I purchase multiple UNO do I multiply my rewards? This is a yes and no answer! If you hold multiple UNO, then your profit share multiplies. > For example, 2 UNO means twice the profit share. However, this is not the case for rewards or discounts. > For example, in terms of any future airdrops, they will be issued per wallet not per UNO. Similarly, a discount does not multiply. > For example, as 20% discount does not accumulate to a 40% discount. ## Past UNO Campaigns **Status: Completed UNO season campaigns** #### What was the UNO Season 1 Campaign? The UNO Season 1 campaign ran from 22nd July – 31st August 2025 (inclusive). #### What are the UNO Node Operator Season 1 rewards? Users who delegate their UNO NFT to an active node operator will receive 30 gNODE per day, per Operator Node/license. **Status: Completed UNO sale** #### Phase 1 Phase 1 opened on March 10th 2025 and is completed. Price set at 500 $NODE > For Phase 1, \$NODE holders minted UNO in exchange for 500 \$NODE [here](https://uno.nodeops.network) for 48 hours. #### Phase 2 In Phase 2, minting cost was /$200 - For Phase 2: - Buy as many $25 tickets as you wish - A raffle will determine which tickets win a chance to mint - Each full mint costs $200, so any tickets you purchased go toward that total - If you are on an allowlist, you will have 5x the chances to win > For example, if you buy 8 tickets (totalling \$200) and two of those tickets get selected in the raffle, you've effectively paid for one UNO mint already. You can claim that immediately. If you want to claim the second winning spot as well, you'd pay an additional $200 to complete that second mint. Any unclaimed spots will carry over to Phase 3. Phase 2 opened on March 12th and is completed. ##### What happens if I buy an UNO raffle and don't win an allowlisted place? The mechanism setup ensured that anyone who didn't get an allowlisted place in the raffle would get their money back once Phase 3 was completed. However, everyone that engaged in the raffle has been awarded the opportunity to mint UNO. No refunds are anticipated for Phase 2. #### Phase 3 In Phase 3, UNO cost: - /$250 or - 1500 Wave 1 airdropped $NODE Phase 3 opened on March 19th and is completed. #### What action should I take if I hold Wave 1 airdrop $NODE tokens already? You were automatically allowlisted as a Wave 1 airdrop $NODE holder and could exchange: - [500 $NODE to claim 1 UNO NFT](https://uno.nodeops.network/) in [Phase 1](#phase-1) - [1500 $NODE to claim 1 UNO NFT](https://uno.nodeops.network/) in [Phase 3](#phase-3) However, these phases are now complete. --- ### Supported Wallets > Learn how to set up your EVM wallet for NodeOps Network on Arbitrum, including network configuration and ETH gas requirements. URL: https://docs.nodeops.network/Learn/FAQ/wallets ## Networks ### How do I switch to Arbitrum Mainnet? To use NodeOps Network on Mainnet, your wallet needs to connect with Arbitrum One, Arbitrum’s Mainnet network. If your wallet doesn't switch automatically, you can add the network manually with the following details: Network Name: Arbitrum One RPC URL: https://arb1.arbitrum.io/rpc Chain ID: 42161 Currency Symbol: ETH Block Explorer URL: https://arbiscan.io ### How much Arbitrum ETH do I need? That answer depends on the network congestion/fees. Typically less than 0.1 Arbitrum ETH is more than enough. ### I have registered the wrong wallet address with my account, how can I change it? Please open a ticket on [Discord](https://nodeops.network/discord) and we'll take care of it. --- ### What is Airdrop? β€” NodeOps Glossary > An airdrop is a pre-allocated percentage of a project's official token distributed to early supporters and community contributors. Airdrops incentivize par... URL: https://docs.nodeops.network/Learn/Glossary/airdrop **Airdrop** β€” An airdrop is a pre-allocated percentage of a project's official token distributed to early supporters and community contributors. Airdrops incentivize participation and reward early adopters who contribute to a project's growth. **Category:** Tokens & Economics ## Related terms - [Sybils](/Learn/Glossary/sybils) - [Staking](/Learn/Glossary/staking) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is API Key? β€” NodeOps Glossary > An API key is a secret token that identifies and authorizes your app when communicating with a service. It acts as a password for programs, not people. The... URL: https://docs.nodeops.network/Learn/Glossary/api-key **API Key** β€” An API key is a secret token that identifies and authorizes your app when communicating with a service. It acts as a password for programs, not people. The key verifies your account and enables access to authorized data and services. If someone else obtains your key, they could use your account, potentially incurring costs or triggering rate limits. Always protect your API keys using environment variables and secret management systems. **Category:** Development & DevOps ## Related terms - [Secrets](/Learn/Glossary/secrets) - [Environment Variables](/Learn/Glossary/environment-variables) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is AVS? β€” NodeOps Glossary > Autonomous Verifiable Services (AVS) refers to the protocol responsible for validation of tasks related to Node deployment and operations. AVS is a concept... URL: https://docs.nodeops.network/Learn/Glossary/avs **AVS** β€” Autonomous Verifiable Services (AVS) refers to the protocol responsible for validation of tasks related to Node deployment and operations. AVS is a concept originating from EigenLayer's restaking architecture, enabling new forms of decentralized verification and trust. **Category:** DePIN & Infrastructure ## Related terms - [Staking](/Learn/Glossary/staking) - [Operator](/Learn/Glossary/operator) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Bond? β€” NodeOps Glossary > Bonding is the process of locking $NODE tokens to register a machine with the NodeOps Protocol. Unlike staking in a Proof of Stake (PoS) mechanism, bonding... URL: https://docs.nodeops.network/Learn/Glossary/bond **Bond** β€” Bonding is the process of locking $NODE tokens to register a machine with the NodeOps Protocol. Unlike staking in a Proof of Stake (PoS) mechanism, bonding provides economic alignment between Compute providers and the protocol's decentralized physical infrastructure (DePIN). The bonded tokens serve as collateral that will be slashed if the provider fails to maintain their agreed Service Level Agreement (SLA). **Category:** Tokens & Economics ## Related terms - [Staking](/Learn/Glossary/staking) - [Provider](/Learn/Glossary/provider) - [DePIN](/Learn/Glossary/depin) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Bot? β€” NodeOps Glossary > A bot is a software agent. In Web3, bots are often employed by people attempting to create multiple wallet instances for airdrop hunting. This behavior is ... URL: https://docs.nodeops.network/Learn/Glossary/bot **Bot** β€” A bot is a software agent. In Web3, bots are often employed by people attempting to create multiple wallet instances for airdrop hunting. This behavior is closely linked to Sybil attacks, where bad actors create fake identities to gain unfair advantages in token distributions. **Category:** Security & Privacy ## Related terms - [Sybils](/Learn/Glossary/sybils) - [Airdrop](/Learn/Glossary/airdrop) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Compute Unit? β€” NodeOps Glossary > A Compute Unit (CU) is the standard unit of measurement for a Compute provider machine's capacity and the unit of consumption by a Compute consumer on Node... URL: https://docs.nodeops.network/Learn/Glossary/compute-unit **Compute Unit** β€” A Compute Unit (CU) is the standard unit of measurement for a Compute provider machine's capacity and the unit of consumption by a Compute consumer on NodeOps Cloud. It standardizes how computing resources are measured, allocated, and billed across the decentralized marketplace. **Category:** DePIN & Infrastructure ## Related terms - [Provider](/Learn/Glossary/provider) - [Machine](/Learn/Glossary/machine) - [Template](/Learn/Glossary/template) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Console? β€” NodeOps Glossary > NodeOps Console is the user interface that Node Runners use to deploy and manage their blockchain and protocol Nodes. It provides a no-code dashboard for l... URL: https://docs.nodeops.network/Learn/Glossary/console **Console** β€” NodeOps Console is the user interface that Node Runners use to deploy and manage their blockchain and protocol Nodes. It provides a no-code dashboard for launching Node-as-a-Service (NaaS) subscriptions with just a few clicks, handling all technical infrastructure behind the scenes. **Category:** NodeOps Products ## Related terms - [NaaS](/Learn/Glossary/naas) - [Node Operators](/Learn/Glossary/node-operators) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is CPU Architecture? β€” NodeOps Glossary > CPU architecture refers to the instruction set design of a processor. The two main architectures in Cloud computing are ARM64 (RISC-based, power-efficient,... URL: https://docs.nodeops.network/Learn/Glossary/cpu-architecture **CPU Architecture** β€” CPU architecture refers to the instruction set design of a processor. The two main architectures in Cloud computing are ARM64 (RISC-based, power-efficient, used in smartphones and increasingly in servers like Apple M-series and AWS Graviton) and AMD64/x86-64 (CISC-based, wide software compatibility, dominant in desktops and data centers). Choosing the correct architecture is essential when deploying Docker containers and templates on NodeOps Cloud. **Category:** DePIN & Infrastructure ## Related terms - [Docker Image](/Learn/Glossary/docker-image) - [Template](/Learn/Glossary/template) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is DAO? β€” NodeOps Glossary > A Decentralized Autonomous Organization (DAO) is a governance mechanism that operates without a central authority. DAOs govern collectively through members... URL: https://docs.nodeops.network/Learn/Glossary/dao **DAO** β€” A Decentralized Autonomous Organization (DAO) is a governance mechanism that operates without a central authority. DAOs govern collectively through members who make decisions by voting. Members typically hold tokens that represent ownership or voting power, enabling transparent and democratic protocol governance. **Category:** Governance ## Related terms - [Staking](/Learn/Glossary/staking) - [Bond](/Learn/Glossary/bond) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is DePIN? β€” NodeOps Glossary > Decentralized Physical Infrastructure Networks (DePIN) leverage blockchain and decentralized technologies to power and govern real-world physical infrastru... URL: https://docs.nodeops.network/Learn/Glossary/depin **DePIN** β€” Decentralized Physical Infrastructure Networks (DePIN) leverage 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. NodeOps Network is a DePIN orchestration layer. **Category:** DePIN & Infrastructure ## Related terms - [Provider](/Learn/Glossary/provider) - [Machine](/Learn/Glossary/machine) - [Bond](/Learn/Glossary/bond) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Docker Image? β€” NodeOps Glossary > A Docker image is a pre-packaged environment containing everything needed to run an application, including code, dependencies, and system libraries. When d... URL: https://docs.nodeops.network/Learn/Glossary/docker-image **Docker Image** β€” A Docker image is a pre-packaged environment containing everything needed to run an application, including code, dependencies, and system libraries. When deploying templates on NodeOps Cloud Marketplace, Docker images must be public (accessible for pulling during deployment) and tagged with the correct CPU architecture and version using a digest (SHA256) or tag. **Category:** Development & DevOps ## Related terms - [Template](/Learn/Glossary/template) - [CPU Architecture](/Learn/Glossary/cpu-architecture) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Encryption? β€” NodeOps Glossary > Encryption is the process of converting information or data into a code to prevent unauthorized access. It is fundamental to securing data in transit and a... URL: https://docs.nodeops.network/Learn/Glossary/encryption **Encryption** β€” Encryption is the process of converting information or data into a code to prevent unauthorized access. It is fundamental to securing data in transit and at rest across networks and systems. Best practices for encryption in Web3 include using environment variables for sensitive data, implementing secret management systems, and encrypting data at rest. **Category:** Security & Privacy ## Related terms - [Secrets](/Learn/Glossary/secrets) - [Environment Variables](/Learn/Glossary/environment-variables) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Environment Variables? β€” NodeOps Glossary > Environment variables are secure placeholders used to store sensitive information β€” like API keys β€” outside of your code. Applications access them at runti... URL: https://docs.nodeops.network/Learn/Glossary/environment-variables **Environment Variables** β€” Environment variables are secure placeholders used to store sensitive information β€” like API keys β€” outside of your code. Applications access them at runtime through the system environment, so secret values never need to be written directly into the source code. This keeps credentials hidden and makes applications safer to share or deploy. **Category:** Development & DevOps ## Related terms - [API Key](/Learn/Glossary/api-key) - [Secrets](/Learn/Glossary/secrets) - [Docker Image](/Learn/Glossary/docker-image) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Failover? β€” NodeOps Glossary > Failover is the capability to automatically switch to a redundant or standby system in the event of a failure, ensuring high availability and business cont... URL: https://docs.nodeops.network/Learn/Glossary/failover **Failover** β€” Failover is the capability to automatically switch to a redundant or standby system in the event of a failure, ensuring high availability and business continuity. NodeOps infrastructure is designed with failover mechanisms to maintain 100% uptime for managed Nodes. **Category:** DePIN & Infrastructure ## Related terms - [Machine](/Learn/Glossary/machine) - [NaaS](/Learn/Glossary/naas) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Federated Learning? β€” NodeOps Glossary > Federated learning is a Machine Learning (ML) technique where models are trained across multiple decentralized devices or servers holding local data sample... URL: https://docs.nodeops.network/Learn/Glossary/federated-learning **Federated Learning** β€” Federated learning is a Machine Learning (ML) technique where models are trained across multiple decentralized devices or servers holding local data samples, without exchanging the raw data. This enhances both privacy and security while enabling distributed AI model training β€” a key use case for DePIN Compute marketplaces. **Category:** AI & Machine Learning ## Related terms - [DePIN](/Learn/Glossary/depin) - [Compute Unit](/Learn/Glossary/compute-unit) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Federation? β€” NodeOps Glossary > Federation is the process of linking identity information across multiple systems or organizations, enabling secure collaboration and single sign-on across... URL: https://docs.nodeops.network/Learn/Glossary/federation **Federation** β€” Federation is the process of linking identity information across multiple systems or organizations, enabling secure collaboration and single sign-on across domains. Federated Identity Management (FIM) allows users to access multiple applications with a single set of credentials. **Category:** Security & Privacy ## Related terms - [Encryption](/Learn/Glossary/encryption) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Full Disk Encryption? β€” NodeOps Glossary > Full Disk Encryption (FDE) is a security measure that encrypts all data on a disk drive, protecting information even if the physical device is lost or stol... URL: https://docs.nodeops.network/Learn/Glossary/full-disk-encryption **Full Disk Encryption** β€” Full Disk Encryption (FDE) is a security measure that encrypts all data on a disk drive, protecting information even if the physical device is lost or stolen. FDE is a best practice for infrastructure security in Cloud and decentralized Compute environments. **Category:** Security & Privacy ## Related terms - [Encryption](/Learn/Glossary/encryption) - [Secrets](/Learn/Glossary/secrets) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Gas Sponsorship? β€” NodeOps Glossary > Gas sponsorships allow services to be accessed and claims to be made without the connected wallet paying the gas fee for writing data onchain. This is enab... URL: https://docs.nodeops.network/Learn/Glossary/gas-sponsorship **Gas Sponsorship** β€” Gas sponsorships allow services to be accessed and claims to be made without the connected wallet paying the gas fee for writing data onchain. This is enabled through EIP-7702, reducing friction for users interacting with blockchain-based services. **Category:** Blockchain Concepts ## Related terms - [Staking](/Learn/Glossary/staking) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Localhost? β€” NodeOps Glossary > Localhost refers to the current device used to access a network service. It is often associated with the IP address 127.0.0.1 and is commonly used for test... URL: https://docs.nodeops.network/Learn/Glossary/localhost **Localhost** β€” Localhost refers to the current device used to access a network service. It is often associated with the IP address 127.0.0.1 and is commonly used for testing web applications locally, accessing services running on the same machine, and loopback communication during development. **Category:** Development & DevOps ## Related terms - [API Key](/Learn/Glossary/api-key) - [Docker Image](/Learn/Glossary/docker-image) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Machine? β€” NodeOps Glossary > Machines are individual Compute infrastructure units that a provider registers with NodeOps Cloud. Each machine is added to the NodeOps Network under a pro... URL: https://docs.nodeops.network/Learn/Glossary/machine **Machine** β€” Machines are individual Compute infrastructure units that a provider registers with NodeOps Cloud. Each machine is added to the NodeOps Network under a provider account using the 'Add Machine' process during provider onboarding. Machines host workloads deployed through the marketplace. **Category:** DePIN & Infrastructure ## Related terms - [Provider](/Learn/Glossary/provider) - [Workload](/Learn/Glossary/workload) - [Compute Unit](/Learn/Glossary/compute-unit) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is NaaS? β€” NodeOps Glossary > Node-as-a-Service (NaaS) is a simplified way for anyone to run Web3 protocol or blockchain Nodes. With NaaS providers like NodeOps, you outsource hardware,... URL: https://docs.nodeops.network/Learn/Glossary/naas **NaaS** β€” Node-as-a-Service (NaaS) is a simplified way for anyone to run Web3 protocol or blockchain Nodes. With NaaS providers like NodeOps, you outsource hardware, installation, updates, and uptime management β€” deploying Nodes with just a few clicks without needing technical expertise. **Category:** NodeOps Products ## Related terms - [Console](/Learn/Glossary/console) - [Node Operators](/Learn/Glossary/node-operators) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Node Operators? β€” NodeOps Glossary > Node Operators are end users β€” the Node Runners who deploy and own the Nodes they run using partner service provider interfaces. NodeOps Console is the pri... URL: https://docs.nodeops.network/Learn/Glossary/node-operators **Node Operators** β€” Node Operators are end users β€” the Node Runners who deploy and own the Nodes they run using partner service provider interfaces. NodeOps Console is the primary interface for Node operators to deploy and manage their blockchain and protocol Nodes. **Category:** Network Roles ## Related terms - [Console](/Learn/Glossary/console) - [NaaS](/Learn/Glossary/naas) - [Operator](/Learn/Glossary/operator) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Operator? β€” NodeOps Glossary > Operators are individuals or groups participating in the validation of tasks related to Node deployment through the NodeOps Network Autonomous Verifiable S... URL: https://docs.nodeops.network/Learn/Glossary/operator **Operator** β€” Operators are individuals or groups participating in the validation of tasks related to Node deployment through the NodeOps Network Autonomous Verifiable Services (AVS). Operator onboarding involves a series of steps to opt into supporting the NodeOps Network AVS. **Category:** Network Roles ## Related terms - [AVS](/Learn/Glossary/avs) - [Node Operators](/Learn/Glossary/node-operators) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Private Template? β€” NodeOps Glossary > A private template is a deployment configuration on NodeOps Cloud that can only be viewed, modified, or deployed by its owner. Private templates offer cont... URL: https://docs.nodeops.network/Learn/Glossary/private-template **Private Template** β€” A private template is a deployment configuration on NodeOps Cloud that can only be viewed, modified, or deployed by its owner. Private templates offer control over who can access your infrastructure configurations, and owners can change template visibility at any time. **Category:** NodeOps Products ## Related terms - [Template](/Learn/Glossary/template) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Provider? β€” NodeOps Glossary > A provider is an individual or group lending their underutilized or unused hardware infrastructure (machines) for workloads deployed through NodeOps Networ... URL: https://docs.nodeops.network/Learn/Glossary/provider **Provider** β€” A provider is an individual or group lending their underutilized or unused hardware infrastructure (machines) for workloads deployed through NodeOps Network. Providers go through an onboarding process to join the provider pool and must bond $NODE tokens to register their machines. **Category:** Network Roles ## Related terms - [Machine](/Learn/Glossary/machine) - [Bond](/Learn/Glossary/bond) - [Workload](/Learn/Glossary/workload) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### NodeOps Glossary > Complete glossary of NodeOps Network terms including DePIN, NaaS, Compute Units, staking, bonding, templates, API keys, Docker images, and more. URL: https://docs.nodeops.network/Learn/Glossary A comprehensive reference of key terms used across NodeOps Network, DePIN infrastructure, and Web3 Node operations. ## Browse by category ### DePIN & infrastructure - [AVS](/Learn/Glossary/avs) β€” Autonomous Verifiable Services (AVS) refers to the protocol responsible for validation of tasks related to Node deployment and operations. - [Compute Unit](/Learn/Glossary/compute-unit) β€” A Compute Unit (CU) is the standard unit of measurement for a Compute provider machine's capacity and the unit of consumption by a Compute consumer on NodeOps Cloud. - [CPU Architecture](/Learn/Glossary/cpu-architecture) β€” CPU architecture refers to the instruction set design of a processor. - [DePIN](/Learn/Glossary/depin) β€” Decentralized Physical Infrastructure Networks (DePIN) leverage blockchain and decentralized technologies to power and govern real-world physical infrastructure. - [Failover](/Learn/Glossary/failover) β€” Failover is the capability to automatically switch to a redundant or standby system in the event of a failure, ensuring high availability and business continuity. - [Machine](/Learn/Glossary/machine) β€” Machines are individual Compute infrastructure units that a provider registers with NodeOps Cloud. - [Scheduling](/Learn/Glossary/scheduling) β€” Scheduling is the process of finding the right machine for a Node deployment request within the NodeOps Network. - [Workload](/Learn/Glossary/workload) β€” A workload is a Node deployed on a provider machine within the NodeOps Network. ### Tokens & economics - [Airdrop](/Learn/Glossary/airdrop) β€” An airdrop is a pre-allocated percentage of a project's official token distributed to early supporters and community contributors. - [Bond](/Learn/Glossary/bond) β€” Bonding is the process of locking $NODE tokens to register a machine with the NodeOps Protocol. - [Staking](/Learn/Glossary/staking) β€” Under Proof-of-Stake (PoS) blockchains, staking is the locking of tokens to support blockchain operations. - [Supply](/Learn/Glossary/supply) β€” Token supply is measured in three ways: Circulating Supply (tokens circulating in the market), Total Supply (tokens in existence minus verifiably burned tokens), and Max Supply (the theoretical maximum tokens that could exist given the tokenomics). ### Security & privacy - [Bot](/Learn/Glossary/bot) β€” A bot is a software agent. - [Encryption](/Learn/Glossary/encryption) β€” Encryption is the process of converting information or data into a code to prevent unauthorized access. - [Federation](/Learn/Glossary/federation) β€” Federation is the process of linking identity information across multiple systems or organizations, enabling secure collaboration and single sign-on across domains. - [Full Disk Encryption](/Learn/Glossary/full-disk-encryption) β€” Full Disk Encryption (FDE) is a security measure that encrypts all data on a disk drive, protecting information even if the physical device is lost or stolen. - [SBOM](/Learn/Glossary/sbom) β€” A Software Bill of Materials (SBOM) is a security and compliance audit that analyzes the full list of components used in a software application. - [Secrets](/Learn/Glossary/secrets) β€” Secrets are sensitive data such as API keys that require careful handling. - [Sybils](/Learn/Glossary/sybils) β€” A Sybil is essentially a copy identity. ### Development & DevOps - [API Key](/Learn/Glossary/api-key) β€” An API key is a secret token that identifies and authorizes your app when communicating with a service. - [Docker Image](/Learn/Glossary/docker-image) β€” A Docker image is a pre-packaged environment containing everything needed to run an application, including code, dependencies, and system libraries. - [Environment Variables](/Learn/Glossary/environment-variables) β€” Environment variables are secure placeholders used to store sensitive information β€” like API keys β€” outside of your code. - [Localhost](/Learn/Glossary/localhost) β€” Localhost refers to the current device used to access a network service. ### NodeOps products - [Console](/Learn/Glossary/console) β€” NodeOps Console is the user interface that Node Runners use to deploy and manage their blockchain and protocol Nodes. - [NaaS](/Learn/Glossary/naas) β€” Node-as-a-Service (NaaS) is a simplified way for anyone to run Web3 protocol or blockchain Nodes. - [Private Template](/Learn/Glossary/private-template) β€” A private template is a deployment configuration on NodeOps Cloud that can only be viewed, modified, or deployed by its owner. - [Template](/Learn/Glossary/template) β€” A template is an infrastructure-as-configuration playbook: a YAML file that defines how an application should run within the NodeOps Cloud Marketplace. ### Network roles - [Node Operators](/Learn/Glossary/node-operators) β€” Node Operators are end users β€” the Node Runners who deploy and own the Nodes they run using partner service provider interfaces. - [Operator](/Learn/Glossary/operator) β€” Operators are individuals or groups participating in the validation of tasks related to Node deployment through the NodeOps Network Autonomous Verifiable Services (AVS). - [Provider](/Learn/Glossary/provider) β€” A provider is an individual or group lending their underutilized or unused hardware infrastructure (machines) for workloads deployed through NodeOps Network. ### Governance - [DAO](/Learn/Glossary/dao) β€” A Decentralized Autonomous Organization (DAO) is a governance mechanism that operates without a central authority. ### Blockchain concepts - [Gas Sponsorship](/Learn/Glossary/gas-sponsorship) β€” Gas sponsorships allow services to be accessed and claims to be made without the connected wallet paying the gas fee for writing data onchain. ### AI & machine learning - [Federated Learning](/Learn/Glossary/federated-learning) β€” Federated learning is a Machine Learning (ML) technique where models are trained across multiple decentralized devices or servers holding local data samples, without exchanging the raw data. ## All terms (A–Z) - [Airdrop](/Learn/Glossary/airdrop) - [API Key](/Learn/Glossary/api-key) - [AVS](/Learn/Glossary/avs) - [Bond](/Learn/Glossary/bond) - [Bot](/Learn/Glossary/bot) - [Compute Unit](/Learn/Glossary/compute-unit) - [Console](/Learn/Glossary/console) - [CPU Architecture](/Learn/Glossary/cpu-architecture) - [DAO](/Learn/Glossary/dao) - [DePIN](/Learn/Glossary/depin) - [Docker Image](/Learn/Glossary/docker-image) - [Encryption](/Learn/Glossary/encryption) - [Environment Variables](/Learn/Glossary/environment-variables) - [Failover](/Learn/Glossary/failover) - [Federated Learning](/Learn/Glossary/federated-learning) - [Federation](/Learn/Glossary/federation) - [Full Disk Encryption](/Learn/Glossary/full-disk-encryption) - [Gas Sponsorship](/Learn/Glossary/gas-sponsorship) - [Localhost](/Learn/Glossary/localhost) - [Machine](/Learn/Glossary/machine) - [NaaS](/Learn/Glossary/naas) - [Node Operators](/Learn/Glossary/node-operators) - [Operator](/Learn/Glossary/operator) - [Private Template](/Learn/Glossary/private-template) - [Provider](/Learn/Glossary/provider) - [SBOM](/Learn/Glossary/sbom) - [Scheduling](/Learn/Glossary/scheduling) - [Secrets](/Learn/Glossary/secrets) - [Staking](/Learn/Glossary/staking) - [Supply](/Learn/Glossary/supply) - [Sybils](/Learn/Glossary/sybils) - [Template](/Learn/Glossary/template) - [Workload](/Learn/Glossary/workload) ## What next? - [Get Started with NodeOps](/Get-Started/Console/README.md) and put these concepts into practice - Learn about [NodeOps core products and services](/Core-Services) - Browse [protocol Node guides](/Guides/Console) for step-by-step deployment tutorials --- ### What is SBOM? β€” NodeOps Glossary > A Software Bill of Materials (SBOM) is a security and compliance audit that analyzes the full list of components used in a software application. This inclu... URL: https://docs.nodeops.network/Learn/Glossary/sbom **SBOM** β€” A Software Bill of Materials (SBOM) is a security and compliance audit that analyzes the full list of components used in a software application. This includes code auditing, configuration scanning, and vulnerability testing. SBOM is a component of compliance standards such as Executive Order 14028 (U.S. government) and ISO/IEC 5230. Users can compile SBOM reports from the NodeOps Marketplace security scanner. **Category:** Security & Privacy ## Related terms - [Encryption](/Learn/Glossary/encryption) - [Secrets](/Learn/Glossary/secrets) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Scheduling? β€” NodeOps Glossary > Scheduling is the process of finding the right machine for a Node deployment request within the NodeOps Network. The scheduling algorithm matches workload ... URL: https://docs.nodeops.network/Learn/Glossary/scheduling **Scheduling** β€” Scheduling is the process of finding the right machine for a Node deployment request within the NodeOps Network. The scheduling algorithm matches workload requirements with available provider machines based on Compute resources, location, and other criteria. **Category:** DePIN & Infrastructure ## Related terms - [Machine](/Learn/Glossary/machine) - [Workload](/Learn/Glossary/workload) - [Provider](/Learn/Glossary/provider) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Secrets? β€” NodeOps Glossary > Secrets are sensitive data such as API keys that require careful handling. Best practices include using environment variables, implementing secret manageme... URL: https://docs.nodeops.network/Learn/Glossary/secrets **Secrets** β€” Secrets are sensitive data such as API keys that require careful handling. Best practices include using environment variables, implementing secret management systems (e.g., Kubernetes Secrets, HashiCorp Vault), encrypting data at rest, and using temporary in-memory storage for short-lived sensitive data. **Category:** Security & Privacy ## Related terms - [API Key](/Learn/Glossary/api-key) - [Environment Variables](/Learn/Glossary/environment-variables) - [Encryption](/Learn/Glossary/encryption) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Staking? β€” NodeOps Glossary > Under Proof-of-Stake (PoS) blockchains, staking is the locking of tokens to support blockchain operations. Validators must stake set amounts of the native ... URL: https://docs.nodeops.network/Learn/Glossary/staking **Staking** β€” Under Proof-of-Stake (PoS) blockchains, staking is the locking of tokens to support blockchain operations. Validators must stake set amounts of the native token to validate new transactions and add new blocks. The stake is slashed if the validator fails to build legitimate blocks, ensuring only valid data is added. Validators are rewarded with the native token for successfully adding new blocks. **Category:** Tokens & Economics ## Related terms - [Bond](/Learn/Glossary/bond) - [DAO](/Learn/Glossary/dao) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Supply? β€” NodeOps Glossary > Token supply is measured in three ways: Circulating Supply (tokens circulating in the market), Total Supply (tokens in existence minus verifiably burned to... URL: https://docs.nodeops.network/Learn/Glossary/supply **Supply** β€” Token supply is measured in three ways: Circulating Supply (tokens circulating in the market), Total Supply (tokens in existence minus verifiably burned tokens), and Max Supply (the theoretical maximum tokens that could exist given the tokenomics). **Category:** Tokens & Economics ## Related terms - [Staking](/Learn/Glossary/staking) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Sybils? β€” NodeOps Glossary > A Sybil is essentially a copy identity. While each human individual is unique, Sybil attacks attempt to create multiple identities to gain unfair advantage... URL: https://docs.nodeops.network/Learn/Glossary/sybils **Sybils** β€” A Sybil is essentially a copy identity. While each human individual is unique, Sybil attacks attempt to create multiple identities to gain unfair advantages. This strategy is often employed by airdrop hunters trying to capture an unfair share of available rewards by operating many fake wallet addresses. **Category:** Security & Privacy ## Related terms - [Bot](/Learn/Glossary/bot) - [Airdrop](/Learn/Glossary/airdrop) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Template? β€” NodeOps Glossary > A template is an infrastructure-as-configuration playbook: a YAML file that defines how an application should run within the NodeOps Cloud Marketplace. Tem... URL: https://docs.nodeops.network/Learn/Glossary/template **Template** β€” A template is an infrastructure-as-configuration playbook: a YAML file that defines how an application should run within the NodeOps Cloud Marketplace. Templates specify the public Docker image, resource allocation (CPU, memory), environment variables with placeholders for user input, and whether the application should be exposed to the internet. Templates can be private or public. **Category:** NodeOps Products ## Related terms - [Docker Image](/Learn/Glossary/docker-image) - [Compute Unit](/Learn/Glossary/compute-unit) - [Private Template](/Learn/Glossary/private-template) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### What is Workload? β€” NodeOps Glossary > A workload is a Node deployed on a provider machine within the NodeOps Network. Each workload represents an active deployment consuming Compute resources f... URL: https://docs.nodeops.network/Learn/Glossary/workload **Workload** β€” A workload is a Node deployed on a provider machine within the NodeOps Network. Each workload represents an active deployment consuming Compute resources from the provider's infrastructure. **Category:** DePIN & Infrastructure ## Related terms - [Machine](/Learn/Glossary/machine) - [Provider](/Learn/Glossary/provider) - [Scheduling](/Learn/Glossary/scheduling) ## Learn more - [Full Glossary](/Learn/Glossary) β€” Browse all NodeOps Network terms - [Get Started with NodeOps](/Get-Started/Console/README.md) β€” Deploy your first Node - [Core Services](/Core-Services) β€” Explore the NodeOps ecosystem --- ### NodeOps Network Overview > Technical overview of NodeOps Network architecture, including provider onboarding, Node scheduling, deployment lifecycle, and AVS verification. URL: https://docs.nodeops.network/Learn/overview To build a strong and fully functioning network for Node deployments requires focus on several important aspects: - How do providers onboard NodeOps Network? - How do Restaking Operators onboard NodeOps Network? - How does Node deployment get matched to available providers? - How are the Protocol participants incentivized and rewarded? - How is the Network kept reliable? NodeOps Network brings four different types of Protocol participants under one roof and orchestrates various tasks between them to keep the Network active, secure, reliable, and honest. These are: 1. **Compute Providers:** Individuals or groups that provide the Compute infrastructure 2. **Restaking Operators:** Existing operators on various restaking platforms 3. **Node Operators:** Individuals using NodeOps Network to deploy their Nodes 4. **NodeWatch Network:** Individuals or groups running the NodeWatch light client ![The NodeOps Network](/img/atlas.png "The NodeOps Network") ## Orchestration within NodeOps Network All the individual tasks required to be performed require coordination between the different participants, and this is where the orchestration element comes into play. In NodeOps Network, all these tasks have been grouped together into several core functions: ![Orchestration within NodeOps Network](/img/Learn/trinity-responsibilities.jpg "Orchestration within NodeOps Network") **Onboarding:** Onboarding contains the set of tasks required for onboarding: - New Compute users, for instance, Protocols interested in bootstrapping a Node network - Compute Providers looking to use or resell their Compute infrastructure - Restaking Operators willing to provide additional economic security to these Node networks **Scheduling and Deployment:** These are the set of tasks related to finding the optimal Compute for a Node and performing the deployment. NodeOps Network provides custom logic to select a Compute from the pool for every Node deployment based on certain parameters, such as CPU, RAM, and disk space. **Monitoring:** Every Compute cluster will be constantly monitored for its uptime, CPU, memory, and disk utilization. Additionally, the state of each Compute with respect to its hardware configuration will also be monitored to ensure any changes are captured. **Incentivization and Slashing:** To reward honest behavior of the participants, and deter any misadventure, incentivization and slashing ensures the economic alignment and fosters the sustainable \$NODE economy. ## NodeOps Network AVS The NodeOps Network AVS (Autonomous Verifiable Services) play a crucial role within the NodeOps Network Network in performing on-chain verification of certain crucial tasks. A group of [third party Operators](./Ecosystem/restakers.md) registered with the NodeOps Network AVS are responsible for performing these tasks. ## Deployment Lifecycle The deployment lifecycle in NodeOps Network is a structured process encompassing several vital stages. Let's follow the first use case coming to NodeOps Network Mainnet: Node deployment. ![Deployment Lifecycle](/img/DeploymentLifecycle.png "Deployment Lifecycle") It begins with a Node operator's request for Node deployment via the [Marketplace](https://cloud.nodeops.network/marketplace) and progresses through various states. The network's smart contracts facilitate each step, ensuring a transparent, secure, and efficient pathway from request to resource allocation. **Payment Processing:** The first step in the Node deployment process is payment processing, which starts the moment a Node operator selects a Node and proceeds to buy a subscription. Every new subscription is a new order processed through an Order Management System. Upon payment processing, a record is created within the NodeOps Network backend, and the payment verification AVS task kicks in. The NodeOps Network AVS operators perform verification on the subscription payment and once approved, the Node deployment is ready to be scheduled. **Scheduling:** Scheduling refers to selecting the most appropriate machine for a deployment. The NodeOps Network scheduler uses a scheduling logic to choose the best available machine based on different parameters for every deployment task. For details, please refer to [Node Scheduling and Deployment](/docs/Learn/Ecosystem/providers.mdx#node-scheduling-and-deployment). **Deployment:** Once the machine is confirmed, the scheduler performs the deployment on that machine. For details, please refer to [Node Scheduling and Deployment](/docs/Learn/Ecosystem/providers.mdx#node-scheduling-and-deployment). **Rewards:** The reward calculation process runs automatically every 24 hours. Each provider is rewarded for being active in the pool as well as for any Nodes running on their machines. Node Operators are also rewarded for every Node they purchase and deploy using NodeOps Network Console, and the restaking operators are rewarded for every successful execution of AVS tasks. Rewards are covered in depth within the individual sections for each stakeholder. The NodeOps Network Console and Provider dashboard provides several functions that Node Operators and providers can use to monitor their Nodes and machines. These functions form part of the operational management of these Nodes and machines and provide critical information in the form of data points, charts, and graphs. --- ### Agent Terminal > Explore NodeOps Agent Terminal, a Cloud-based collaborative sandbox for building, testing, and deploying AI agents on DePIN Compute. URL: https://docs.nodeops.network/Learn/Products/Cloud/agent-terminal 🌟 Status: Beta testing on Mainnet ## What is Agent Terminal? Agent Terminal is a cutting-edge, Cloud-based playground for collaborative AI development. > **Tip: Imagine an online collaborative tool like CodePen designed for the complexities of coding, testing, and training AI.** The sandboxed code deploys into [NodeOps Cloud](./README.md): NodeOps' permissionless, secure, verifiable, DePIN Compute marketplace. Collaborate, test, and debug your app wherever your team mates are. > **Warning: This is not a production environment: use this for testing code and training models. Do NOT run critical workloads from Agent Terminal.** ## Who is Agent Terminal for? Agent Terminal provides an intuitive coding interface for developers at all levels. The two key segments of our community that are most likely to be the first-comers are: ### AI agent developers Agent Terminal is for developers who need to experiment, build, and deploy AI solutions in real time. Whether you're working on small-scale agents or testing advanced AI workloads, our developer-friendly terminal offers: - Affordable Cloud-linked Compute power: Seamlessly connect to CPU and GPU resources from the NodeOps Cloud Marketplace for foundational coding and intensive AI tasks - Collaborative development: Collaborate with your team in real time, sharing code and results instantly - Scalable workflows: Handle everything from lightweight non-GPU AI workflows to full-scale AI deployment pipelines as we integrate GPU capabilities - An exit from the sandbox: Does your AI agent need to consume real-world data? Don't worry, the AI agent can break out of its box via a plug-in, privacy-friendly, AI Cloud Browser. We will launch with a free service for as long as we can, and then move to a subscription model going forward. ## Why Agent Terminal? There is an urgent need for a versatile developer platform that integrates with affordable Cloud Compute as needed. The Agent Terminal connects developers seamlessly with NodeOps' CPU AI workflows, to let you: - Develop and test AI agents with minimal setup - Deploy AI workloads in a flexible, fast, and user-friendly environment - And soon, with GPU options onboarded, scale up to support GPU-intensive AI solutions seamlessly Interact with your application as if it were running locally to test, debug, and demonstrate applications. And, do this from anywhere, with collaborative features like code sharing, live editing, and commenting. The tools you need are integrated, providing instant access to popular AI frameworks and libraries directly from your development sandbox. ### Tools you are familiar with - HTTP enabled: Collect data from trusted oracles - asdf: manage different versions of Rust, Node.js, Python, Java, Elixir, etc.) and other tools (like Terraform, Kubernetes, etc.) without conflicts - Integrate your favorite extensions from the VS Code ecosystem to enhance your development environment - Easily plug in linters, debuggers, and more, to simplify how you work with different tools and languages ### Simplified collaboration Interact with your application as if it were running locally to test, debug, and demonstrate applications. Share the port-forwarded URL and show the application's output to others or conduct live coding sessions, for simple, effective, remote code collaboration. ### Simplified resourcing Thanks to NodeOps Network's Compute marketplace: NodeOps Cloud, you can add the Compute you need to your cluster to resource your LLM or AI agent. ### Control over your finances Launching as a free service, with an affordable monthly subscription pricing model planned, the Agent Terminal is an affordable, lock-in-free option for developers. And, when you want to bring in the big guns, the Agent Terminal will estimate the by-the-hour cost of the Compute your cluster will consume, meaning you are always in control of your budget. Whether you're a solo developer experimenting with ideas or part of a team ready to push the boundaries of AI, this platform is for you. ## On the Roadmap Next up on the Roadmap: - GPU - Access 600+ open source LLMs with our API key ## What next? - [Get started](/Get-Started/Cloud-Tools/agent-terminal.md) > Agent Terminal is now open to beta testers. --- ### Linux capabilities dropped > Understand why NodeOps Cloud drops Linux capabilities to reduce attack surface and improve container security on provider machines. URL: https://docs.nodeops.network/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/dropped-linux ## Linux capabilities are dropped [Linux](https://man7.org/linux/man-pages/man7/capabilities.7.html) capabilities provide a way to grant specific privileges to processes without giving them full root access. When all Linux capabilities are dropped, it significantly impacts any running process's ability to perform privileged operations. ### Impact 1. **Reduced attack surface**: Dropping all capabilities [limits potential exploitation vectors](https://www.kernel.org/doc/html/latest/security/credentials.html). 2. **Limited system access**: The process cannot perform operations that typically require root privileges. - Binding to [ports below 1024](https://www.kernel.org/doc/html/latest/networking/ip-sysctl.html) - Modifying system files - Changing network configurations 3. **Increased security**: Prevents accidental or malicious abuse of privileged operations. 4. **Potential functionality issues**: Some applications may require specific capabilities to function correctly. ### Best Practices - Only grant [necessary capabilities](https://www.kernel.org/doc/html/latest/security/credentials.html) to processes that require them - Use fine-grained capability management instead of running processes as root ### What next? Consider reading up on: - [Services run with UserID 65535](./user-65535.md) - [Ports](./ports-exposed.md) --- ### Persistent storage > Learn about persistent storage in NodeOps Cloud containers, including best practices for persistent volumes and data backups. URL: https://docs.nodeops.network/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/persistent-storage 🚧 Status: Coming soon ## Persistent storage Persistent storage in computing refers to data storage that retains data after a machine is shut down. In containerized environments, persistent storage is crucial for maintaining data across container lifecycles. ### Best practices 1. Use [persistent volumes (PVs) and persistent volume claims (PVCs)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) for data that needs to persist. 2. Implement [dynamic provisioning](https://kubernetes.io/docs/concepts/storage/storage-classes/) with storage classes to automate volume management. 3. Regularly [back up data stored in persistent volumes](https://kubernetes.io/docs/concepts/storage/storage-classes/). ### What next? Consider reading up on: - [Avoiding sensitive data storage](/Learn/Glossary/secrets) --- ### Ports exposed > Learn how NodeOps Cloud handles TCP/UDP port exposure for containers, improving security through network isolation by default. URL: https://docs.nodeops.network/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/ports-exposed ## No TCP/UDP Ports Exposed Not exposing any TCP/UDP ports during the initial stage of a service or container deployment is a security measure that limits network access. ### Impact 1. **Reduced attack surface**: [Minimizes potential entry points](https://www.man7.org/linux/man-pages/man7/network_namespaces.7.html)) for network-based attacks. 2. **Improved security posture**: Prevents unauthorized access to services that may not be fully configured or secured. 3. **Network isolation**: The service cannot receive incoming connections, [limiting its ability to interact](https://docs.docker.com/network) with other network entities. 4. **Outbound connections**: While incoming connections are blocked, the service can still initiate [outbound connections](https://kubernetes.io/docs/concepts/services-networking/service/) if needed. ### Considerations 1. **Service accessibility**: Services requiring incoming connections will require port exposure at a later stage. 2. **Inter-service communication**: In containerized environments, internal communication may still be possible through container networks without exposing ports externally. ### What next? Consider reading up on: - [All Linux capabilities dropped](./dropped-linux.md) - [Services run with UserID 65535](./user-65535.md) --- ### Understand machine properties > Explore NodeOps Cloud machine properties including Linux capabilities, persistent storage, exposed ports, namespaces, and user IDs. URL: https://docs.nodeops.network/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties You are in the right place to learn more about how NodeOps Network machines are configured. Learn more about: - [Linux capabilities being dropped](./dropped-linux.md) - [Persistent storage](./persistent-storage.md) - [Ports exposed](./ports-exposed.md) - [Single namespace](./single-namespace.md) - [UserID 65535](./user-65535.md) --- ### Single Namespace Architecture > Understand how NodeOps Cloud uses network namespaces to isolate container environments with dedicated routes and firewall rules. URL: https://docs.nodeops.network/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/single-namespace ## Network Namespace A network namespace is a logical copy of the [network stack, with its own routes, firewall rules, and network devices](https://www.man7.org/linux/man-pages/man7/network_namespaces.7.html). It's commonly used in containerization technologies like [Docker](/Learn/Glossary/docker-image) to isolate network environments. ### Key Points - Creates isolated network environments. - Useful for testing and containerization. - Managed using the `ip netns` command. ### What next? Consider reading up on: - [Persistent storage](./persistent-storage.md) --- ### UserID 65535 > Learn why NodeOps Cloud runs services with non-root UserID 65535 to enhance container security and limit process privileges. URL: https://docs.nodeops.network/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/user-65535 > **Tip: TL;DR** - UserID 65535 is an [unprivileged user](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) in containerized environments. ## Services Running with UserID 65535 Running services with UserID 65535 (non-root) is a security measure to reduce the potential impact of a compromised service. ### Impact 1. **Reduced privileges**: The service runs with [limited permissions](https://www.redhat.com/sysadmin/rootless-containers-podman), similar to a regular user account. 2. **Improved security**: Prevents the service from [accessing or modifying](https://docs.docker.com/engine/security/userns-remap/) system-critical files and settings. 3. **Isolation**: Helps contain potential security breaches by [limiting the service's access](https://kubernetes.io/docs/concepts/security/pod-security-standards/) to other parts of the system. 4. **Compatibility considerations**: Some applications may assume root privileges and need to be adapted to work with a non-root user ID. ### Best Practices - Ensure the service has the necessary permissions to perform its required tasks without excess privileges. - Use additional security measures like SELinux or AppArmor for further access control. ### What next? Consider reading up on: - [Ports exposed](./ports-exposed.md) --- ### Optimize templates > Practical examples for optimizing NodeOps Cloud YAML templates, covering resource allocation, cost management, and performance monitoring. URL: https://docs.nodeops.network/Learn/Products/Cloud/Cloud-Infrastructure/Optimize-Infrastructure/optimize The following scenarios are paired with a template to demonstrate how developers can consider optimizations as they define their infrastructure. ## Consider resource optimization Scenario: A data scientist is working with large datasets and wants to optimize resource usage to prevent memory overload or slow performance. Template: ```yaml services: image: jupyter/scipy-notebook imagePullPolicy: Always resourceUsage: limits: cpu: 500m memory: 1024Mi requests: cpu: 500m memory: 1024Mi env: DATA_CHUNK_SIZE: "1000" ``` > This template ensures efficient resource allocation and encourages chunk-based processing for large datasets. ## Consider user behavior patterns Scenario: A shared Jupyter notebook server hosts users with varying needsβ€”some performing light tasks, others running intensive computations. Template: ```yaml services: image: jupyter/datascience-notebook resourceUsage: idle: cpu: 200m memory: 512Mi peak: cpu: 1000m memory: 2048Mi env: MODE: "{{ USER_MODE }}" ``` > This template provides flexibility by defining both idle and peak resource allocations, accommodating diverse user behaviors. ## Consider performance monitoring Scenario: Administrators need to monitor resource usage (CPU, memory) of running Jupyter notebooks to identify bottlenecks. Template: ```yaml services: image: jupyter/base-notebook resourceUsage: idle: cpu: 300m memory: 1024Mi env: MONITORING_ENABLED: "true" command: > start-notebook.sh --NotebookApp.ResourceUsage.enabled=True ``` This template integrates monitoring tools (such as jupyter-resource-usage) for real-time tracking of notebook performance. ## Consider cost management Scenario: A Cloud-based environment charges based on Compute usage, so precise resource allocation is critical to control costs. Template: ```yaml services: image: jupyter/minimal-notebook resourceUsage: idle: cpu: 100m memory: 256Mi peak: cpu: 800m memory: 2048Mi ``` > This template minimizes idle costs while allowing sufficient resources during peak usage, balancing performance and cost efficiency. ## What next? - Learn more about [template schemas](/Reference/template-schema.md) - Are you ready to submit a [template](/Guides/Marketplace/Configure-Compute/upload-template.md) to the Marketplace? - Consider performing a [vulnerability scan](/Get-Started/Cloud-Tools/scan.md) to verify the veracity of your templates --- ### Cloud infrastructure > Learn about NodeOps Cloud infrastructure-as-configuration using YAML templates to automate and manage decentralized Compute deployments. URL: https://docs.nodeops.network/Learn/Products/Cloud/Cloud-Infrastructure 🌟 Status: Live on Mainnet [NodeOps Cloud](./README.md) makes it easy to manage Cloud infrastructure by letting developers use simple YAML templates to automate deployments. This template-based approach allows you to define and consume Compute infrastructure in a declarative manner: enabling automation of your infrastructure deployments. This allows you to consume and create infrastructure templates that enable: - Version control - Automated testing - Continuous integration and deployment - Modularity and reusability ## Templates for developers NodeOps Cloud Compute is consumed via "playbooks" of standardized templates. You may either: - [Submit a template](/Guides/Marketplace/Configure-Compute/upload-template#submit-a-public-template-to-the-marketplace) for approval and earn a share of the workload fee - [Create a private template](/Guides/Marketplace/Configure-Compute/upload-template#create-a-private-template-for-personal-use) > **Info: Monetize your templates** In the boostrapping phase of the Network, templates earn 20% of the workload fee. > This allows early template contributors to enjoy a significant incentive should their template prove popular. ## Templates for users Logged into the [Cloud Marketplace](https://cloud.nodeops.network/), navigate to **Deploy Templates**. See the [Get Started](/Get-Started/Cloud-Infrastructure/deploy) for detailed template setup steps. ## The rationale for YAML templates NodeOps Cloud's "Infrastructure as Configuration" approach uses a [YAML](https://yaml.org/) file, a data serialization standard commonly used for configuration files. Using YAML templates for infrastructure provisioning offers several advantages: - Readability: YAML's simple syntax is easy for people and machines to understand - Declarative approach: Define the desired state of your infrastructure without specifying the step-by-step process to achieve it - Reusability: Templates can be parameterized and shared across multiple pipelines, reducing code duplication - Consistency: Standardized templates ensure that infrastructure is deployed consistently across different environments These YAML templates are an effective solution for managing complex Cloud infrastructures: combining the power of automation with the simplicity and readability of declarative configurations. ## Unit of consumption Each template playbook will provision your Compute infrastructure according to your use case and is charged according to the workload, measured as the Compute consumed. The Compute consumed is defined by Compute Units or CUs: One CU is defined as: 1CU = 1 vCPU, 2GB RAM, 30GB NVMe Disk ## What next? - [Deploy a template](/Get-Started/Cloud-Infrastructure/deploy) - [Submit a template](/Guides/Marketplace/Configure-Compute/upload-template) to NodeOps Cloud Marketplace - [Set up private templates](/Guides/Marketplace/Configure-Compute/upload-template.md) and deploy your custom workloads - Learn how to define a [template](/Reference/template-schema.md) - Browse the [template FAQ](/Learn/FAQ/templates.md) --- ### DePIN Cloud > Discover NodeOps DePIN Cloud, a decentralized Compute marketplace for deploying, providing, and managing verifiable Cloud infrastructure. URL: https://docs.nodeops.network/Learn/Products/Cloud ## What is the NodeOps Cloud? [NodeOps Cloud](https://cloud.nodeops.network/) is a verifiable, high-availability, economically secure, decentralized Cloud infrastructure: allowing anyone to provide, purchase, deploy, and manage verifiable Compute. > **Tip: Run Cloud infrastructure** NodeOps Cloud Compute is consumed via "playbooks" of standardized templates. - [Browse the template Marketplace](/Get-Started/Cloud-Infrastructure/deploy/) for an app, environment, or infrastructure requirements - [Upload your own customized template](/Guides/Marketplace/Configure-Compute/upload-template.md) ## Who is the NodeOps Cloud Marketplace for? NodeOps Cloud is for anyone who needs user friendly, managed, redundency-enabled, multi-region, Cloud Compute and the tooling to let them focus on what matters. NodeOps Network Protocol, the coordination layer, exists to enforce the economic alignment of the NodeOps Cloud Marketplace participants. It does this by enabling participants to earn by verifying the [Compute provided](/Learn/Ecosystem/providers.mdx). These verifiers are the [Node Orchestrators](/Learn/Ecosystem/nodeorchestrator.md): entities running the NodeWatch light client. ## How can I earn with NodeOps Cloud? The NodeOps Protocol that coordinates the Cloud Marketplace rewards participants. This means that there are several ways to earn: - Become a [Template developer](/Guides/Marketplace/Configure-Compute/upload-template) and earn rewards when users run workloads via your code - [Provide Compute](/Get-Started/Cloud-Compute/Provide-Compute/README.md) - Earn higher rewards when you assign your machine/s workloads - [Verify the Protocol](/Get-Started/Cloud-Compute/node-orchestrator.md) - [Top up with credits](/Get-Started/Pay-for-Services/Readme.mdx): Burn \$10 or more \$NODE to earn Credits and unlock multipliers that boost your future rewards - [Deploy Nodes](/Get-Started/Console/README.md): Use the [NodeOps Console](https://console.nodeops.network/) to deploy Nodes or workloads - [Farm Compute](/Guides/Marketplace/farm) / [rent a machine](/Get-Started/Cloud-Compute/rent-compute.md): Lease Compute from the Marketplace - [Mint a UNO NFT](/Guides/Community-Incentives/uno#mint-uno): Mint a UNO NFT to gain ecosystem perks, future governance access, and airdrop eligibility - [Stake](/Get-Started/DeFi-Services/stake.md) \$NODE or supported tokens with [NodeOps Portal](https://portal.nodeops.network/) - [Launch UNO-enabled CU](/Guides/Community-Incentives/uno#uno-available-cu) ## Why is NodeOps Cloud important? When you run critical infrastructure in the Cloud, you need to know that your Compute provider can keep those services live. And, to be a successful Compute provider, you need to show consumers that your services are reliable. NodeOps Network's DePIN orchestration layer allows Compute providers to verifiably demonstrate the resilience of the service they provide to Compute consumers. NodeOps Network offers to transform the traditional Compute consumption model by implementing the best that blockchain technology has to offer: decentralized, tamper-proof Protocols. NodeOps Network enforces Compute provider's integrity with its Autonomous Verifiable Services (AVS). This ensures that Compute providers are incentivized to meet their SLAs through automated rewards and penalties: all verifiably monitored and enforced via the NodeWatch Network. > **Tip: Why we use two names** Orchestra analogy: NodeOps Network is the conductor, and NodeOps Cloud is the drummer providing the rhythm. ## How is Cloud Compute charged for? With NodeOps, your Compute is charged by Compute Units (CUs) consumed: 1CU = 1 vCPU, 2GB RAM, 30GB NVMe Disk ## How are Compute providers compensated? Compute providers earn a share of the charge paid for consuming the CUs. That is, they earn a share of the fee the consumer pays. A proportion of the fee is burned as part of the [\$NODE economics](/Tokenomics/node.md). ## What next? - Learn more about the "Infrastructure as Configuration" [templates](/Learn/Products/Cloud/Cloud-Infrastructure/README.md) - Understand how to [monitor your Cloud Infrastructure](/Guides/Marketplace/Monitor-Infrastructure) --- ### Security Hub > Learn about NodeOps Security Hub, an AI-powered code vulnerability scanner for Docker images, repositories, and Cloud templates. URL: https://docs.nodeops.network/Learn/Products/Cloud/security 🌟 Status: Live on Mainnet ## Overview NodeOps Marketplace’s [Security Hub](https://cloud.nodeops.network/scan) is an AI-powered, code vulnerability scanning solution. Integrated directly into the NodeOps Network Marketplace dashboard, Security Hub enables you to proactively detect, assess, and remediate security risks in public codebases, Docker images, and templates β€” all from the Marketplace dashboard's user-friendly interface. The NopeOps Marketplace Dashboard provides an integrated vulnerability scanner to allow you to verify the integrity of: - Codebases / repositories - Public Docker Images - 🚧 Templates ## Why NodeOps Security Hub? Containerized workloads are growing fast, and so are the threats. NodeOps Security Hub delivers automated scanning to help you stay ahead. Traditional scanning tools are often complex, siloed, and challenging to integrate. They weren't developed with containerized, or decentralized environments in mind. This results in developers and DevOps teams leaving systems exposed to known critical risks and exposes the end user to hacks that can drain their funds and leak their data. Secure your stack without slowing it down. ## What is Security Hub? Security Hub is an at-a-click code vulnerability scanner that provides instant, AI-powered, actionable reports. Leveraging open source security scanners, it allows you to search for know vulnerabilities in your stack. Security Hub offers: - Comprehensive scanning: Uses leading open-source tools to identify vulnerabilities and misconfigurations in containers, code, and infrastructure - User-friendly interface: Initiate scans and review reports with just a few clicks β€” no security expertise required - Detailed reporting: Get in-depth, AI-categorized vulnerability summaries and downloadable reports - Continuous protection: Automatic rescans and real-time alerts as images or dependencies update - CI/CD Integration: Embed Security Hub into DevOps pipelines for automated, ongoing protection ## What next? - [Scan your code](/Get-Started/Cloud-Tools/scan.md) - [Learn more about security best practices](/Learn/Glossary/secrets) --- ### Liquidity release > Unlock immediate liquidity from NFT Node licenses using the NodeOps LNT Vault, converting future rewards into tradable VT and YT tokens. URL: https://docs.nodeops.network/Learn/Products/DeFi-Services/liquidity > **Tip: TL;DR** [NodeOps Console](https://console.Nodeops.network/)lets you lock your NFT licenses in an LNT vault for immediate liquidity. LNT vault lets you unlock immediate liquidity from your Node licenses. This innovative system turns your future Node-based rewards into flexible, tradable assets. ## What licenses are supported? - Aethir > The NFT may be available on a reseller marketplace such as [Opensea](https://opensea.io/collection/aethir-checker-license). ## What is LNT Vault liquidity extraction? The LNT Vault gives you control over when and how you access your Node license rewards β€” breaking free from the slow drip of emissions and turning them into assets you can trade. In many Initial Node Offering (INO) projects, when you buy a Node license (typically issued as an NFT), you gain the right to operate a Node (or delegate that right) and earn validator rewards gradually over time as the Node produces emissions. This creates a β€œlocked” rewards system because you can’t access the full value you’ve purchased immediately, you earn it bit by bit as the network pays out over time. The LNT (Liquid Node Token) Vault changes this by letting you deposit your Node license and receive two separate, tradable tokens: - VT (Vesting Token): Your right to the baseline guaranteed emissions from qualified Node operations - YT (Yield Token): Your right to any excess yield above the guaranteed portion Both VT and YT can be traded, held, or integrated into DeFi markets so you can realize value from your license straight away. ## Why use LNT Vault for liquidity extraction? - Access value now: Convert future validator rewards into tradable rights today - Custom exposure: Keep VT for predictable returns, sell YT for upfront liquidity, or mix strategies to match your needs - No operational or financial burden: No need to run a Node yourself, or to subscribe to NodeOp's Node-as-a-Service model - Market-driven flexibility: Participate in secondary markets for VT and YT and respond to price trends. ## Who is this LNT Vault for? - INO buyers who want quicker liquidity than the standard gradual payout model - Institutions managing significant inventories of illiquid Node licenses. ## What next? - [Get started](/Get-Started/DeFi-Services/liquidity) and extract immediate liquidity from your license - Just want to earn the license rewards over time? - [Delegate your license](/Get-Started/Console/commission-based) for a reward share, or - [Run a dedicated managed Node subscription](/Get-Started/Console/subscription) for your license - [Learn more](https://www.certik.com/resources/blog/certik-ventures-announces-investment-in-zoo-finance) about the team behind the LNT Vault --- ### Staking > Stake tokens on NodeOps Portal to earn dual rewards: APR on your staked assets plus $NODE via gNODE. Supports 450+ EVM wallets. URL: https://docs.nodeops.network/Learn/Products/DeFi-Services/staking 🌟 Status: Live on Mainnet > **Tip: TL;DR** [NodeOps Portal's](/Guides/Portal) unified dashboard lets you stake tokens and manage your \$NODE. With NodeOps Portal you can: - [Manage \$NODE](/Guides/Portal) - [Convert gNODE to \$NODE](/Guides/Portal#redeem-gnode-with-nodeops-portal) - [Mint UNO](/Guides/Community-Incentives/uno#mint-uno) - [Stake and unstake](/Guides/Portal) With several features coming soon: - 🚧 Engage with governance - 🚧 Manage rewards - 🚧 Convert \$NODE to credits all from one unified dashboard. ## Dual incentives with Portal's stakedrop Staking offers dual incentives rewards: earn an APR in the token you stake **and** a [\$NODE reward](/Tokenomics/node.md). ## What tokens are supported? - **$ATH** Mainnet > 100 K gNode pool | ends 4th October, 2025 - **$POL** on Ethereum Mainnet > 2 mil gNODE pool | ends 28th July, 2026 NodeOps is working hard to make our vision a reality: - $HYPE Mainnet - $ETH EigenLayer Mainnet - $BEAM Mainnet - **$HYPE** Testnet ## Supported wallets Portal supports over 450 EVM-compatible wallets, including any wallet that supports the WalletConnect standard: - Argent - Binance Chain Wallet - Keplr - Ledger Live - Math Wallet - MetaMask - OKX - Phantom - Rainbow Wallet - SafePal - Trezor Wallet - Trust Wallet ... and many more. ## Why should I stake? Staking with the [NodeOps Portal](https://portal.nodeops.network/) provides an opportunity to earn passive income, that is, yield on your staked tokens. ## How do I earn the \$NODE reward? The value of the yield correlates with how long you commit your stake for. The \$NODE rewards are issued as [gNODE](/Guides/Community-Incentives/points.md) which may be redeemed to \$NODE via the same Portal app. ## NodeOps Validator sets - [Beam validators](https://nodes.onbeam.com/delegations) - [HyperLiquid validators](https://app.hyperliquid-testnet.xyz/explorer) - [Polygon validators](https://staking.polygon.technology/validators/182) ## What next? - [Get started and drop your stake](/Get-Started/DeFi-Services/stake.md) - Learn more about [NodeOps' Portal](/Guides/Portal/) - Learn more about [staking $BEAM from the blog](https://nodeops.network/blog/staking-beam-with-nodeops-staking-hub) - Learn more about [staking $HYPE from the blog](https://nodeops.network/blog/staking-hype-with-nodeops-staking-hub) - Learn more about [staking $POL from the blog](https://nodeops.network/blog/staking-pol-with-nodeops-staking-hub) --- ### Node-as-a-Service > Deploy and manage blockchain Nodes with NodeOps Console NaaS. Delegate NFT licenses or subscribe for managed Nodes with 100% uptime. URL: https://docs.nodeops.network/Learn/Products/Node-services 🌟 Status: Live > **Tip: TL;DR** [NodeOps Console](https://console.nodeops.network/) lets you delegate NFT licenses and earn a share of their rewards or subscribe to run a managed Node and earn all of the rewards. ## What is Node-as-Service? NodeOps Console provides a Node-as-a-service (NaaS) subscription to a no-code Node runner dashboard serving a diverse blockchain ecosystem. NaaS removes the complexity of running Blockchain and Protocol Node infrastructure so anyone can spin up a Node and earn the rewards. With NodeOps Console, you can launch and maintain Blockchain or Protocol Nodes in seconds. No manual setup needed, no steep learning curve. Choose from: - [Paying a subscription to run a Node](/Get-Started/Console/subscription), or - [Delegating an NFT license to NodeOps](/Get-Started/Console/commission-based) who will take a commission to run the Node If you choose to pay a subscription to run a Node, you take 100% of the rewards. Should you delegate, then NodeOps takes a commission, a share of the rewards. ## Supported Blockchain and Protocol Nodes | Protocol | Keys or license required | NFT delegation supported | |--------------------------|--------------------|--------------------| | [Aethir](/Guides/Console/Managed-Nodes/aethir.mdx) |Y| | | [Avail](/Guides/Console/Managed-Nodes/avail.mdx) |N | | | [Beam](/Guides/Console/Managed-Nodes/beam.mdx) |Y|| | [CARV](/Guides/Console/Managed-Nodes/carv.mdx) |Y | [Y](/Guides/Console/Managed-Nodes/carv#carv-commission-model)| | [Celestia](/Guides/Console/Managed-Nodes/celestia.mdx) |N | | | [Captain & Company](/Guides/Console/Managed-Nodes/capnco.mdx)|Y | | | [DIN](/Guides/Console/Managed-Nodes/din.mdx) |Y | | | [Fuse](/Guides/Console/Managed-Nodes/fuse.mdx) |Y | | | [Huddle01](/Guides/Console/Managed-Nodes/huddle01.md) |Y | | | [Hybrid](/Guides/Console/Managed-Nodes/hybrid.md) |Y | | | [Hychain](/Guides/Console/Managed-Nodes/hychain.md) |Y | | | [iAgent](/Guides/Console/Managed-Nodes/iagent/bootstrapping.md)|Y| | | [KIP](/Guides/Console/Managed-Nodes/kip.md) |Y | | | [Lumoz](/Guides/Console/Managed-Nodes/lumoz.md) |Y | | | [Nexus](/Guides/Console/Managed-Nodes/nexus.md) |N | | | [0G](/Guides/Console/Managed-Nodes/og-alignment.md) |Y | [Y](/Guides/Console/Managed-Nodes/og-alignment#delegate-your-0g-alignment-nft-to-earn-commission)| | [OpenPad](/Guides/Console/Managed-Nodes/openpad.md) |Y | | | [PlayAI](/Guides/Console/Managed-Nodes/playai.md) |Y | | | [Rivalz](/Guides/Console/Managed-Nodes/rivalz.md) |Y | | | [Sophon](/Guides/Console/Managed-Nodes/sophon/README.md) |Y| [Y](/Guides/Console/Managed-Nodes/sophon/commission)| | [Vemp Horizon](/Guides/Console/Managed-Nodes/vemp-horizon.md)|Y | | | [XAI](/Guides/Console/Managed-Nodes/xai.md) |Y |[Y](/Get-Started/Console/commission-based)| | [XProtocol](/Guides/Console/Managed-Nodes/xprotocol.md) |Y | | ## What is the commission service? NodeOps empowers you to unlock the full potential of your NFT licenses by leveraging the power of delegation. Delegate your NFT licenses to NodeOps as your trusted operator and passively earn a share of the rewards. No need to subscribe to run a Node or manage any infrastructure yourself. Just delegate and watch your NFTs generate yield, turning dormant digital assets into active income streams. This delegation-driven approach lets you participate fully in DeFi, earning rewards from an otherwise-unused asset. Never let go of your NFTs; get access to their upside. This service is available for: - [0G](/Guides/Console/Managed-Nodes/og-alignment) - Arbitrum - [Carv Checker license](/Guides/Console/Managed-Nodes/carv) - [Xai Sentry license](/Guides/Console/Managed-Nodes/xai) - [Sophon Guardian license](/Guides/Console/Managed-Nodes/sophon/commission) ## Why Node-as-a-service? Traditionally, operating a blockchain Node requires specialized hardware, reliable internet connection, and technical expertise in operating systems like Linux or Windows. With NodeOps, these challenges are a thing of the past. We handle everything for you: * Hardware Requirements: No need to invest in or manage physical equipment * Node Installation: Our streamlined process ensures your Node is properly set up * Software Updates: Enjoy hassle-free automatic updates to keep your Node up-to-date * Reliable Uptime: We ensure consistent performance and reliability ## Who is Node-as-a-service for? Anyone interested in running a Node; many people do this to earn incentives from the Protocol whose Nodes they run. With NodeOps, running a Node is as simple as clicking a few buttons β€” no technical skills required. Enjoy simplified Node deployment for Protocols across verticals such as Gaming, AI, DePIN, and more, all under one roof. ## FAQ ### What is license delegation? NodeOps offers a Node Delegation feature, enabling you to put your NFT licenses to work without the financial overhead of subscribing to run a Node from our [Node-as-a-Service](/Learn/Products/Node-services) offering. With just a few clicks, you can delegate your NFT to trusted NodeOps-operated infrastructure and automatically allocate a portion of the rewards toward NodeOps as commission for managing the operation. The rest is yours β€” all the benefits with no financial outlay and none of the hassle. ### Why use Node delegation? - Hassle-free: No need to set up servers, monitor uptime, or update Node software (or pay for a managed Node subscription) - Passive earning: Your NFT continues to generate yield while you focus on other things - Trusted infrastructure: Operated by NodeOps, with network-grade uptime and security - Flexible: You choose the NFT to delegate; commissions are transparent and automatic ### What happens if Protocols don't have a dedicated delegation page? If the Project doesn't natively support delegation, the entire flow is handled in the NodeOps Console app. ### How do I release my delegated NFT license? The NodeOps Console app provides [Delegate](/Get-Started/Console/commission-based) and [Undelegate](/Guides/Console/console-account.md#undelegate-your-nft) flows. Be aware that Protocols may have cool down periods for the unlock/undelegate flow to protect the integrity of their Node networks? ## What next? - [Get started](/Get-Started/Console/commission-based) and delegate an NFT - Don't want to share the license rewards? Run a dedicated [managed Node subscription](/Guides/Console) for your license - Want immediate access to the license liquidity? Drop supported licenses into the [LNT Vault](/Learn/Products/DeFi-Services/liquidity) - Learn about the full set of [products and services](/Core-Services#product-and-services) offered across the NodeOps ecosystem --- ### Products and services > Overview of NodeOps ecosystem products: DePIN Cloud, Agent Terminal, Security Hub, staking, liquidity release, and Node-as-a-Service. URL: https://docs.nodeops.network/Learn/Products Deep dive the NodeOps ecosystem products and services. - [DePIN Cloud](/Learn/Products/Cloud) and its toolsets, [Agent Terminal](/Learn/Products/Cloud/agent-terminal) and [Security Hub](/Learn/Products/Cloud/security) > Accessed via the [Cloud Marketplace](https://cloud.nodeops.network/) app. - DeFi services - [Staking](/Learn/Products/DeFi-Services/staking) - [Liquidity release](/Learn/Products/DeFi-Services/liquidity) > Accessed via the [Console app](https://console.nodeops.network/) or the [Portal app](https://portal.nodeops.network/), depending on the service. - Node-as-a-Service - [Subscription-based managed Nodes](/Learn/Products/Node-services#what-is-node-as-service) - [Commission-based managed Nodes](/Learn/Products/Node-services#what-is-the-commission-service) > Accessed via the [Console app](https://console.nodeops.network/). --- ### Learn About NodeOps Network > Introduction to NodeOps Network, the DePIN coordination protocol for decentralized Cloud Compute, Node deployment, and infrastructure management. URL: https://docs.nodeops.network/Learn ## What is NodeOps? **NodeOps is the leading economically-secured, permissionless, DePIN coordination Protocol**: redefining Cloud infrastructure management. NodeOps' one-stop solution bridges the gap for Compute providers, Node operators, developers, and Protocols, enabling seamless integration and access to premium decentralized services. > **Tip: Mission** NodeOps is committed to easing how you code and deploy Apps, AI, and blockchain technologies. Our mission is to enhance the builder experience so that users and developers remain focused on what matters. NodeOps is organized around 4 pillars: 1. The **NodeOps Network**, a chain-agnostic, permissionless DePIN orchestrator for general-purpose Compute, secured by Autonomous Verifiable Services (AVS). The Network's participants include: - [Restaking operators](./Ecosystem/restakers.md) - [Node Orchestrators](./Ecosystem/nodeorchestrator.md) - [Compute providers](./Ecosystem/providers.mdx) 2. A suite of [core services](../Core-Services/Readme.md). 3. **NodeOps Foundation**'s governance layer β€” underpinning the network and the services and centered around the [\$NODE](../Tokenomics/node) token, which serves as the economic backbone, fueling the Network's decentralization. 4. **NodeOps' ecosystem of partners and providers** that are the lifeblood of the network. These four pillars enable NodeOps to offer a versatile, secure, and user-friendly platform abstracting away the infrastructure challenges of decentralized computing and blockchain operations. ## Explain it like I'm five NodeOps Network is like a large, safe playground where parents (Protocols, dApps & Apps, or Web3 projects) drop off their kids (Nodes, applications, storage, agents) to play. Each parent hires allocated toys (Compute Nodes) from the playground's store (NodeOps marketplace) using pocket money (tokens). Groups of kids often converge together to build fantastic structures (decentralized Node networks) with these. Helpful guardians (monitoring systems) watch to ensure everyone plays fairly, that the structures are safe, and that the toys don't break. If something goes wrong, they quickly fix it, so everyone can keep playing. The playground has several key features: - New kids and toys are welcomed in (onboarding). - The guardians ensure the environment is safe and the toys are ready to use (deployment and monitoring). - Reliable toys earn the store additional rewards, and faulty toys incur store penalties (incentivization and slashing). ## High-level overview of the ecosystem ```mermaid graph TD %% Subgraph groups all nodes for clarity subgraph ATLAS_FLOW[ ] A[Infrastructure Service Providers] B[NodeOps Network] D[Providers] E[Node Management] F[Incentivization and Slashing] G[NodeWatch Network] end A -->|Supply| B B -->|Onboarding| D B -->|Deployment
and Monitoring| E B -->|Crypto-Economic Security| F F -->|Compliance| G %% Optional: Highlight F node for emphasis (edit as needed) class F redNode; classDef redNode fill:#FF3333,stroke:#DE2222,color:#111,stroke-width:2px; ``` ![NodeOps Network ELI5](/img/AtlasELI5.jpeg "NodeOps Network ELI5") --- ### Use cases > Introduction to use cases URL: https://docs.nodeops.network/Learn/Use-cases NodeOps Network's service-agnostic Marketplace supports multiple verticals from low-demand Node operations to high-demand AI, ML, and data modeling. ## Node operations While the marketplace is agnostic as to what consumers do with their Compute load, the first large workload demand coming to the NodeOps Network is Node operations. > This is because NodeOps Network is brought to you by the [NodeOps team](https://nodeops.network/). Every Protocol requires a decentralized, secure, and reliable Node infrastructure for its Node network to run on. This is not easy to achieve from day 1, especially for new Protocols. NodeOps Network addresses this key challenge that Protocols face when it comes to creating a Node network by improving: 1. The level of decentralization in the Node network. 2. The security and reliability of the Node network. 3. Ease of Node deployment and Node management. By providing a unified platform for Protocols to seamlessly deploy their Nodes onto a diverse pool of decentralized, secure, and reliable infrastructure providers, NodeOps Network effectively addresses these challenges. This not only saves significant time, resources, and cost, but also ensures a high level of decentralization, security, and reliability for Node networks. ## AI Agents Ever used a paid version of a LLM only to find that it slows down to a stupor every so often? Frustrating isn't it! Even the large LLM providers suffer from Compute demand issues and so the tool you rely on can become, well, unreliable. It doesn't have to be this way, you can provision your own LLM from NodeOps Cloud's Compute and be sure that the resources you need are there when you need them. --- --- ## Reference ### Compute requirements > View Compute Unit (CU) requirements for Machines on the NodeOps Cloud Marketplace. Learn CPU, RAM, and storage specs needed to provide DePIN Compute. URL: https://docs.nodeops.network/Reference/compute-requirements Compute is sold per CU on the NodeOps Cloud Marketplace. These CUs are provided according to the requirements listed on this reference page. > **Tip: 1CU = 1 vCPU, 2GB RAM, 30GB NVMe Disk** ## Compute requirements for Machines on NodeOps Cloud Marketplace > **Info: Machines **must**** Comply with the minimum hardware and port requirements: - CPUs or vCPUs: β‰₯2 - GB RAM: β‰₯4 - SSD storage: β‰₯80GB NVMe Storage - Network bandwidth: β‰₯1Gbps unlimited - Uptime: β‰₯ 99% - OS: Debian (12+) or Ubuntu (22.04+) installation with: - Linux kernel 6.7+ - Latest security patches - Allow traffic on ports: - UDP 8472,51820 - TCP 10250 - Public static IPv4 address - Run the Protocol at root > **Warning: Machines **must not**:** - Run additional workloads - Have third-party applications or monitoring agents installed - Enable [SWAP](https://wiki.archlinux.org/title/Swap) - Be exposed to intervention with the workload or machines > **Info: Run at root** NodeOps Network's integration must be run directly on a machine at root: - You can't run it in Docker - Don't run it on a homelab ## What next? - Register as a [Compute provider](/Get-Started/Cloud-Compute/Provide-Compute/register-to-provide.md) - Understand more about [managing a Machine](/Guides/Marketplace/Manage-Machines/README.md) - If you just want to run a proof of concept, but don't have a Machine with enough capacity, don't worry, you can re-sell [Cloud Compute](/Guides/Marketplace/Provide-Compute/provide-gcp-compute.md). --- ### GPU available > Explore the list of supported GPUs available on the NodeOps Cloud Marketplace. Find compatible GPU hardware for AI inference and Compute workloads. URL: https://docs.nodeops.network/Reference/gpu-supported - RTX 3090 - Released 2020 - Architecture: Ampere - Perfomance: High VRAM (24 GB GDDR6X), strong 4K performance, well-suited for creative workloads - Features: Offers exceptional rendering and AI capability - RTX 4090 - October 2022 - Architecture: Ada Lovelace, using TSMC 4N process - Performance: Offers 50% to 100% better performance than the RTX 3090 across benchmarks, creative workloads, and 4K gaming - Features: Superior ray-tracing, DLSS 3, more CUDA/Tensor/RT cores, significantly improved efficiency - RTX 5090 - Q1 2025 - Architecture: Blackwell (RTX 50-series) - Performance: Upgraded core counts: ~21,760 CUDA cores vs. 16,384 on the 4090. VRAM: 32 GB GDDR7 on a 512-bit bus, offering significant bandwidth boost > RTX 5090 comparison: > - Compared to RTX 4090: ~27–35% average performance improvement in gaming and AI workloads [source](https://www.corsair.com/us/en/explorer/gamer/gaming-pcs/rtx-5090-vs-4090-whats-the-difference/) > - Compared to RTX 3090: Massive leap in performanceβ€”benchmarks show 69–97% higher FPS across resolutions [source](https://www.club386.com/nvidia-geforce-rtx-5090-vs-rtx-3090/) ## What next? - Access the supported GPU from [Cloud Marketplace templates](/Guides/Marketplace/Marketplace-Templates#highlighted-templates) --- ### LLMs available > Browse supported large language models (LLMs) available on NodeOps Network. Deploy AI models via Cloud Marketplace templates like Gaia mainnet. URL: https://docs.nodeops.network/Reference/llms-supported Each of these LLM models is provided in quantized format (Q5_K_M), which trades some precision for smaller memory footprint and faster inference, making them GPU-friendly. - EXAONE-3.5-24B-Instruct-Q5_K_M: - Large-scale 24B parameter instruct model - Optimized quantization (Q5_K_M) for efficiency - General-purpose reasoning and task completion - Qwen2.5-7B-Instruct-Q5_K_M: - 7B parameter instruct model from Alibaba’s Qwen series - Balanced for chat, summarization, and Q&A - Quantized for faster inference with moderate memory usage - Llama-3.2-3B-Instruct-Q5_K_M - Meta’s Llama 3.2 model (3B parameters) - Lightweight, efficient for instruction following - Good choice for smaller tasks and resource-limited runs - Qwen2.5-Coder-3B-Instruct-Q5_K_M - Specialized 3B model for code understanding & generation - Optimized for programming tasks (Python, JS, etc.) - Small footprint for cost-effective code inference - DeepSeek-R1-Distill-Llama-8B-Q5_K_M - Distilled 8B parameter model, derived from Llama - Balanced between speed and quality - Great for chatbots and general AI applications - Qwen2-0.5B-Instruct-Q5_K_M - Tiny 0.5B instruct model - Ultra-lightweight, very fast and cheap to run - Suitable for simple Q&A or rule-based inference Available from: - [Gaia template](Guides/Marketplace/Marketplace-Templates/gaia-mainnet.md) --- ### DAO proposal schema > Follow the NodeOps DAO proposal schema to draft a Protocol Improvement Proposal (PIP). Includes structure guide, template, and submission tips. URL: https://docs.nodeops.network/Reference/proposal-schema 🌟 Status: Live > **Warning: The source of truth is the GitHub, [github.com/NodeOps-app/pips](https://github.com/NodeOps-app/pips).** ## NodeOps DAO proposal style & structure guide A [NodeOps DAO](/Tokenomics/governance) proposal is made up of 7 sections as detailed below. ## 1. Proposal title - Format: PIP-XX: Provide a short, clear description. - Style: Sentence case with only key words capitalized; avoid overly technical jargon. - Example: PIP-01: Establish quorum is functional ## 2. Summary A concise statement outlining the proposal’s purpose and what it aims to achieve. ## 3. Longer description A detailed explanation of the proposal, including context, background, rationale, and any relevant data or references. Clearly state the problem, the proposed solution, and why it matters for the NodeOps ecosystem. ## 4. Next steps List the concrete actions or outcomes if the proposal is approved or rejected. Format: - If passed, (describe the action or change). - If rejected, (describe alternative or next steps). ## 5. Voting options Clearly state the required voting choices: - Yes - No - Abstain ## 6. Discussion link Provide a link to the relevant Discourse discussion thread for community input. ## 7. Voting window Set the window over which voting is possible, typically between 3 and 21 days. ## Template schema ```markdown text Title: PIP-XX: (Short, clear description) Summary (One or two sentences summarizing the proposal’s intent.) Longer Description (Detailed rationale, context, and supporting information. Explain the problem, solution, and expected impact.) Next Steps - If this resolution passes, (describe the resulting action). - If this resolution fails, (describe what will happen next). Voting Options - Yes - No - Abstain Discussion Link (Insert forum post link). Voting window (Start time:date stamp to end time:date stamp inclusive). ``` ## Tips - Use clear, accessible language - Keep sections brief but informative - Link to any supporting documents or references as needed ## What next? - Learn more about [NodeOps DAO](/Tokenomics/governance) - Visit the [GitHub repository that holds and manages the PIPs](https://github.com/NodeOps-app/pips) --- ### Template schemas > Define and deploy services using NodeOps YAML template schemas. Learn resource allocation, Docker image configurations, constraints, and example templates. URL: https://docs.nodeops.network/Reference/template-schema ## Define services in a template NodeOps Network's Marketplace Infrastructure is defined and provisioned via a viable YAML file known as a template. This YAML file defines how an application should run within NodeOps Network's Cloud Infrastructure. It can be used to specify: - The **public [Docker image](/Learn/Glossary/docker-image)** to be used - **Resource allocation** (CPU, memory) - **Environment variables** - Whether the application should be **exposed to the internet** A template acts as an [infrastructure blueprint or playbook](/Learn/Products/Cloud/Cloud-Infrastructure/README.md): ensuring consistent deployment configurations for users. ## Template specification overview | Specification| Description| Example| Allowable Values | |-------------|------------|--------|------------------| | Docker Image| Specifies the public Docker image used for deployment.| [`nginx:latest`](/Reference/template-schema#example-nginx-template)| Valid [Docker image tags](/Reference/template-schema#architecture-tags) (`name:tag`) for [arch amd64](/Learn/Glossary/cpu-architecture)| | Resource Allocation| Defines `cpu` and `memory` resources allocated to the application.| [`cpu: "500m" memory: "128Mi"`](/Reference/template-schema#example-nginx-template)| CPU (`m` for milli-cores), Memory (`Mi`) | | Environment Variables| Configures environment variables, including placeholders and defaults.| [`env: - name: APP_ENV value: "{{.ENV}}" default: development`](/Reference/template-schema#example-protocol-node-template)| Dynamic (`{{.ENV}}`), Static values | | Internet Exposure| Indicates whether the application should be accessible publicly.| [`expose: true`](/Reference/template-schema#example-protocol-node-template)| `true`, `false` | The template structure is versatile to accommodate all your use cases, use the drop down to learn more: ****Show me the YAML definition**** [See examples and further details](/Reference/template-schema) ## Operational constraints 1. All services in the template run under a single pod with same [network namespace](/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/single-namespace.md). > This allows all the services to connect to each other over [localhost](/Learn/Glossary/localhost). 2. [Persistent storage](/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/persistent-storage) is not guaranteed on NodeOps Network; high availability storage options will be available in future updates. > **Warning: - Avoid storing [sensitive data](/Learn/Glossary/secrets), such as private keys, on disk** 3. [Privileged access](/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/user-65535) is not allowed. 4. All [Linux capabilities](/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/dropped-linux) are dropped. 5. Templates run with [userid: 65535](/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/user-65535) (non-root). 6. No [TCP/UDP ports ](/Learn/Products/Cloud/Cloud-Infrastructure/Machine-Properties/ports-exposed) are exposed during this stage. 7. All [container images](/Learn/Glossary/docker-image) must be publicly accessible. 8. HTTP/S services are exposed behind a Cloudflare proxy under [AtlasNetwork.app](http://atlasnetwork.app/). ### Template constraints To ensure fair resource usage, the following constraints apply: > **Warning: Template constraints** 1. Maximum of 5 **services**. 2. Only one service per template can be exposed to the public. 3. Only 1 persistent volume is allowed. 4. The total resource usage is limited to **4 Compute Units (CUs)** > calculated as: CU = max(total CPU, total Memory) 5. Upon template interruption, **all** services will be restarted as part of a single pod with multiple containers. ### Template update constraints You can update descriptions, documentation, and **new versions** of your Docker Image. > [Learn how](/Guides/Marketplace/Configure-Compute#update-your-docker-image). However: - You **can't** modify a template's existing service resource allocations - You **can't** add new services in an upgrade to a template ## Example templates ### Example Jupiter notebook ```yaml version: 0.1 services: jupiter: image: jupyter/base-notebook resourceUsage: idle: cpu: 200 memory: 400 ``` ```yaml name: template.yaml type: object required: - version - services properties: version: type: float value: 0.1 description: Defines the version of the template specification. services: type: object properties: jupiter: type: object required: - image - resourceUsage properties: image: type: string description: Publicly-accessible Docker/container image for the service. value: jupyter/base-notebook resourceUsage: type: object properties: idle: type: object required: - cpu - memory properties: cpu: type: integer description: CPU unit in millicores. value: 200 memory: type: integer description: Memory unit in megabytes. value: 400 ``` ### Example nginx template For example, to configure services such as nginx, the YAML would abide by the following properties: ```yaml version: 0.1 services: nginx: image: nginx:latest args: - '-g' - 'daemon off;' imagePullPolicy: "Always" ports: - containerPort: 80 protocol: TCP expose: true - containerPort: 443 protocol: TCP expose: false env: - name: APP_ENV value: production - name: DEBUG_MODE value: 'false' resourceUsage: idle: cpu: 100 memory: 256 ``` ```yaml name: template.yaml type: object required: - version - services properties: version: type: float value: 0.1 description: Defines the version of the template specification. services: type: object properties: nginx: type: object required: - image - resourceUsage properties: image: type: string description: Publicly-accessible Docker/container image for the service. value: nginx:latest imagePullPolicy: type: string required: false enum: ["Always", "IfNotPresent", "Never"] description: Defines when to pull the Docker image for the service. value: "Always" args: type: array required: false description: Arguments to pass to the command for the service. items: type: string value: - "-g" - "daemon off;" ports: type: array required: true description: Port definitions for the service. items: type: object required: - containerPort - protocol properties: containerPort: type: integer required: true description: Application port. protocol: type: string required: true enum: ["TCP", "UDP"] description: The protocol used by the service. expose: type: boolean required: false description: Whether the port should be exposed for the service. value: - containerPort: 80 protocol: TCP expose: true - containerPort: 443 protocol: TCP env: type: array required: false description: Predefined environment variables for runtime. items: type: object required: - name - value properties: name: type: string description: Name of the environment variable. value: type: string description: The value of the environment variable. value: - name: APP_ENV value: production - name: DEBUG_MODE value: "false" resourceUsage: type: object required: true description: Specifies the resources required by the service. properties: idle: type: object required: - cpu - memory properties: cpu: type: integer description: CPU unit in millicores. value: 100 memory: type: integer description: Memory unit in megabytes. value: 256 ``` #### nginx required fields explained ##### Version Defines the version of the template specification. Use 0.1 as the baseline. ##### Services Each service definition requires the following fields: - **image**: Publicly accessible [Docker](/Learn/Glossary/docker-image)/container image for the service - **port**: Port/s inside the container where the application listens/serves traffic - **env**: Predefined environment variables for the service runtime - **resourceUsage**: Specifies the resources required by the service ### Example Protocol Node template ``` version: 0.1 services: validator: image: elixirprotocol/validator:latest imagePullPolicy: Always args: [] ports: - containerPort: 80 protocol: TCP expose: true env: - name: USER_DEFINED value: "{{ .USER_INPUT_1 }}" default: development resourceUsage: idle: cpu: 100 memory: 4000 ``` ```yaml name: template.yaml type: object required: - version - services properties: version: type: float value: 0.1 description: Defines the version of the template specification. services: type: object properties: validator: type: object required: - image - resourceUsage properties: image: type: string description: Publicly-accessible Docker/container image for the service. value: elixirprotocol/validator:latest imagePullPolicy: type: string enum: ["Always", "IfNotPresent", "Never"] description: Defines when to pull the Docker image for the service. value: "Always" args: type: array description: Arguments to pass to the command for the service. items: type: string value: [] ports: type: array required: true description: Port definitions for the service. items: type: object required: - containerPort - protocol properties: containerPort: type: integer description: Application port. value: 80 protocol: type: string enum: ["TCP", "UDP"] description: The protocol used by the service. value: TCP expose: type: boolean required: false description: Whether the port should be exposed for the service. value: true env: type: array required: false description: Predefined environment variables for the service. items: type: object required: - name - value properties: name: type: string description: Name of the environment variable. value: type: string description: Value of the environment variable (static or dynamic). default: type: string description: Default value if not provided. value: - name: USER_DEFINED value: "{{ .USER_INPUT_1 }}" default: development resourceUsage: type: object required: true description: Specifies the resources required by the service. properties: idle: type: object required: - cpu - memory properties: cpu: type: integer description: CPU unit in millicores. value: 100 memory: type: integer description: Memory unit in megabytes. value: 4000 ``` ## Gotchas ### Architecture tags Docker images inherit the [host’s architecture](/Learn/Glossary/cpu-architecture) unless explicitly set. For example, building on an Apple M-series Mac defaults to `linux/arm64` even if the image is intended for `amd64`. - Check the manifest: Always run `docker manifest inspect ` to confirm the declared platform before pushing. - Be explicit: Use `--platform linux/amd64` with `docker buildx` to avoid incorrect tagging. ## What next? - [Submit a template](/Guides/Marketplace/Configure-Compute/upload-template) to NodeOps Cloud Marketplace - [Deploy a Marketplace template](/Get-Started/Cloud-Infrastructure/deploy) at-a-click - Browse the [template FAQ](/Learn/FAQ/templates.md) - Learn more about the benefits of ["Infrastructure as Configuration"](/Learn/Products/Cloud/Cloud-Infrastructure/README.md) - Scan your template [for vulnerabilities](/Get-Started/Cloud-Tools/scan.md) with NodeOps Security Hub --- --- ## Tokenomics ### Bridge $NODE > Bridge $NODE tokens between Arbitrum, Ethereum, and Binance Smart Chain using NodeOps Portal. Trustless cross-chain transfers for the $NODE token. URL: https://docs.nodeops.network/Tokenomics/bridge 🌟 Status: Live on Mainnet/s > **Tip: TL;DR** [NodeOps Portal](https://portal.nodeops.network) provides a trustless asset transfer to bridge \$NODE between Arbitrum ↔ Ethereum ↔ Binance Smart Chain ## Bridge with NodeOps Portal This guide walks you through bridging \$NODE accross different chains. Use the video or walkthrough to understand how to bridge your \$NODE. **Show me video** > **Info: Finality and fees differ** - **Ethereum ↔ Arbitrum:** Native bridge (up to 15-minute finality) - **Ethereum ↔ BSC:** Official BSC bridge (7-day withdrawal) - **Arbitrum ↔ BSC:** Third-party bridge via LayerZero (up to 15-minute finality) The gas fee to bridge is always dynamic: based on network congestion. #### Prerequisites - EVM-compatible wallet containing \$NODE - Gas funds - You are logged into the [NodeOps Portal](https://portal.nodeops.network). 1. From the **Bridge** tab, choose your source and destination chains. **Show me** > **Important: Ensure your wallet is connected to the source chain and has enough funds for gas on that chain.** 2. Enter amount: specify how much \$NODE you want to bridge or use **Max**, review the transaction details, and confirm in your wallet. > Note that the dashboard displays your \$NODE balance based on the origin chain. **Show me** 3. Click **Bridge Tokens**. Wait for completion: the bridge process may take a few minutes. #### (Optional) verify the transfer Either: - Switch your wallet to the destination chain and check your balance to confirm the bridged \$NODE - Click **View on explorer** to examine the onchain record of the transaction ## Stay safe out there Scammers hijack funds; keep away from them: - Only use the official NodeOps bridge: [https://portal.nodeops.network](https://portal.nodeops.network) - Never share your private keys ## What next? - See all the [Portal functions and features](/Guides/Portal) - Learn about the [\$NODE tokenomics](./node.md) - Learn more about the [\$NODE ecosystem](../Learn/README.md) --- ### NodeOps DAO > Learn how NodeOps DAO governance works. Vote on Protocol Improvement Proposals (PIPs), shape staking and emissions policy, and participate onchain. URL: https://docs.nodeops.network/Tokenomics/governance 🌟 Status: Live ## TL;DR > **Tip: TL;DR** - $NODE stakers, bonders, and UNO holders are [eligible to vote](/Tokenomics/governance#eligible-participants) - Protocol Improvement Proposals (PIPs) are discussed on [Discourse](https://forum.nodeops.network) and managed in [GitHub](https://github.com/NodeOps-app/pips) - PIPs are [voted on](/Tokenomics/governance#vote-on-governance-proposals) in [NodeOps Portal](https://portal.nodeops.network/) with outcomes recorded onchain ## Overview NodeOps Protocol governance is managed by a DAO that gives [eligible participants](/Tokenomics/governance#eligible-participants) control over the Protocol’s direction. The DAO can set key economic parameters, such as: - Staking logic - Emissions schedules - Platform credit allocations - Ecosystem grant disbursement DAO governance shapes the Protocol's development. ## Eligible participants NodeOps applies a Proof of Coordination governance model that rewards those who contribute meaningfully. This means that only those individuals who are actively involved in the staking, bonding, and who hold UNO have a vote, ensuring that decisions reflect real engagement and expertise. - Standard participation: staked and bonded $NODE tokens carry equal voting weight (1 token = 1 vote). - Universal Node Orchestrator (UNO) Operator participation: each UNO operator receives a voting weight of 2,000 $NODE tokens for every UNO NFT they hold. ## Vote on governance proposals Votes are cast by [eligible participants](/Tokenomics/governance#eligible-participants) in the [NodeOps Portal app](https://portal.nodeops.network). Use the drop down for a voting guide. **Show me how to vote in NodeOps Portal** #### Prerequisites - You are [eligible to vote](/Tokenomics/governance#eligible-participants) - You are logged into [NodeOps Portal app](https://portal.nodeops.network) with the same Web3 wallet as you perform all your \$NODE- and UNO-related activities #### Voting guide 🚧 Status: Coming soon Use the video or walkthrough to understand how to cast your vote on a Protocol Improvement Proposal. 1. Logged into the [Portal app](https://portal.nodeops.network), navigate to the Governance tab. 2. Select a PIP that’s open for voting. 3. Cast your vote, and click **Submit Vote**. 4. Confirm in your wallet to register your vote onchain. Congratulations, your vote is registered. ## NodeOps DAO governance flow **Show me detailed governance flow** | Step | Description | | --- | --- | | 1. Idea & eligibility | DAO member identifies issue and checks if eligible to propose | | 2. Drafting | Proposal is written (following [the PIP guidelines](/Reference/proposal-schema)) | | 3. Discussion | Protocol improvement proposal posted on [Discourse](https://forum.nodeops.network) for feedback and refinement | | 4. PIP finalization | Proposal updated based on feedback and prepared for voting | | 5. PIP setup | Proposal submitted to Portal for onchain registration | | 6. Voting | DAO members vote during the set window | | 7. Tally & announcement | Results tallied, quorum checked, outcome announced | | 8. Execution | Passed proposal is implemented | | 9. Post-execution review | Community reviews and monitors implementation | 1. Idea formation and eligibility. > A community member identifies an issue or improvement. 2. Draft the proposal. > A proposal is drafted to be posted on [Discourse](https://forum.nodeops.network). Either as a concept or as a PIP, following the required [format and structure](https://github.com/NodeOps-app/pips?tab=readme-ov-file#pip-proposal-schema). 3. Discussion on [Discourse](https://forum.nodeops.network). > The proposal is posted on the NodeOps DAO’s [Discourse](https://forum.nodeops.network) forum for open discussion and feedback. Typically, a 7-10 day discussion is encouraged. Community members debate and refine the proposal. If the proposal is already drawn up to format, the community may propose edits. 4. Finalize the Proposal. > Incorporating the community feedback, the proposer [drafts the PIP](https://github.com/NodeOps-app/pips), following the required format and structure. 5. PIP setup. > The proposal is submitted to Portal for onchain registration. 6. Voting period runs. > The PIP defines its own voting window, typically between 3-21 days. 7. Vote tallying and result announcement. After the voting window closes, votes are tallied. Quorum requirements must be met for the vote to be valid. If quorum is not met, the proposal fails automatically. 8. Execution. > If the proposal passes, the approved changes are implemented: Onchain actions are executed by smart contracts or DAO multisig, as applicable. Offchain actions are coordinated by the relevant working group or core team. 9. Post-execution review. > The DAO monitors implementation and may discuss outcomes or suggest further improvements. ## DAO FAQ ### How do I get started? To engage in governance, head over to [Discourse](https://forum.nodeops.network) to open up or join a discussion. ### How do I create a PIP? Fork the GitHub repo, [github.com/NodeOps-app/pips](https://github.com/NodeOps-app/pips) and make your PR. ### How does the DAO govern? Protocol Improvement Proposals (PIPs) start life on [Discourse](https://forum.nodeops.network) as discussions or the [GitHub repo](https://github.com/NodeOps-app/pips) and the link dropped in Discourse. If a PIP looks viable, a proposal is created and uploaded to NodeOps Portal. Finally, the DAO casts their votes and if the quorum is reached, the PIP will be enacted upon, or not, according to the outcome. ## What next? - Find the [PIP template](/Reference/proposal-schema) - Learn more about [NodeOps Protocol governance](https://nodeops.network/governance) - Learn more about the [levers controlling the token economy](https://www.notion.so/Tokenomics/node#revenue-share--optimal-control-of-emissions) --- ### $NODE Tokenomics > Explore $NODE tokenomics including supply allocation, vesting schedules, dynamic mint and burn mechanics, revenue sharing, and governance parameters. URL: https://docs.nodeops.network/Tokenomics/node > **Info: - Ticker: \$NODE** - Standard: ERC-20 - Community allocation: 47.5% - Total supply at genesis: 678,833,730 \$NODE - \$NODE may be [bridged between the different chains](./bridge.md) - \$NODE's [contracts](/Tokenomics#node-contracts) are available > **Note: TL;DR** The NodeOps Network tokenomics framework isn’t just a set of rules. It’s a real-time, dynamic, optimally controlled, onchain economy designed to reward contribution, enforce discipline, and scale value. **\$NODE is not minted speculatively β€” it’s minted when the Network earns.** From launch, every \$NODE token is backed by real Protocol revenue. Supply growth is dynamically adjusted through governance, emission caps, and an evolving mint/burn ratio. ## \$NODE tokenomics Behind every blockchain, rollup, and decentralized Protocol lies one constant: **Compute**. It’s what powers consensus, secures networks, and runs dApps. But orchestrating that Compute β€” across chains, teams, and infrastructure providers β€” remains fragmented, inefficient, and largely manual. **NodeOps Network** exists to solve that. It’s an AI-powered general-purpose Compute coordination layer, where infrastructure is decentralized, dynamic, and composable. Whether it’s validator networks, GPU-powered AI inference, or decentralized storage Nodes, NodeOps Network automates the coordination, deployment, and scaling of Compute at internet scale. ### The role of \$NODE **\$NODE is the economic engine of NodeOps Network.** It’s not just a utility token β€” it’s how coordination gets priced, how participants get rewarded, and how the network self-governs. - It secures infrastructure through economic security guarantees - It rewards Compute providers and orchestrators based on real work, not speculation - It governs emissions with a dynamic, revenue-backed mint/burn model - And, it unlocks premium services, Network participation, and Protocol alignment ### Why \$NODE matters Decentralization isn’t just about removing intermediaries. It’s about distributing trust, and Compute is where that trust lives. NodeOps Network puts AI at the center of decentralized Compute coordination. **\$NODE ensures that value flows where it’s earned β€” to those who run the machines that keep Web3 alive.** This is a Network designed to work, scale, and sustain itself β€” with a clear focus on what truly matters: users, product excellence, real demand, and, crucially, sustainable revenue. ## \$NODE usage \$NODE is the economic foundation of the **NodeOps Network**, governing access, coordination, and participation across its decentralized Compute layer. It is used to access services, stake infrastructure, secure workloads, and participate in network-level decisions. ### Access via burn and mint credits All services on the NodeOps Network β€” including Compute, orchestration, and automation β€” are priced in USD. Users pay by burning an equivalent amount of \$NODE and receive **credits**, which serve as non-transferable, non-fungible prepaid access to dApps and services built on top of the Protocol. This ensures that usage is always preceded by token commitment. ### Compute bonding and capacity onboarding Compute providers are required to bond \$NODE to register and contribute resources. A base bond of **2,000 \$NODE** provides access to the provider set. An additional **200 \$NODE per machine** is required for each new unit added. Machine capacity is measured in **Compute Units (1 CU = 1 CPU, 2GB RAM, 30GB storage)**. This creates a clear economic threshold for participation and scales capacity based on committed stake. ### Verifiable Compute via restaking NodeOps Network integrates with AVS ecosystems like EigenLayer, Solayer, and Symbiotic to enable slashing-based accountability. \$NODE can be restaked to provide economic guarantees for Compute execution. If providers or operators fail to meet availability or integrity requirements, their stake is subject to slashing. ### Governance participation \$NODE holders can participate in governance, including voting on reward policies, bonding requirements, emission configurations, and operational parameters such as burn/mint ratio, Compute provider bonding fees, ecosystem growth decisions, and emission caps. Governance decisions are made onchain and tied to stake-based voting power. \$NODE governance framework empowers token holders, rewards real contributions, and ensures the long-term health of the Protocol. ## Allocation ### Supply - **Total supply at genesis:** 678,833,730 \$NODE - **Total circulating supply at launch:** 133,390,828, which is 19.65% of the total supply - **Dynamic burn/mint ratio:** starts at 0.2 ### Distribution NodeOps Network has allocated 47.5% of the genesis supply to the community. The following graph details the breakdown. Let’s break down how \$NODE is distributed across stakeholders, what each allocation supports, and how vesting schedules ensure accountability over time. #### **Community & ecosystem growth** *203,650,119 \$NODE (30% of Total supply)* The largest portion of \$NODE is reserved for growing and supporting the NodeOps ecosystem. This includes: - **Contributor incentives**: rewarding active users and builders - **Partnerships and integrations**: supporting dApp teams and infrastructure partners - **Marketing and education**: funding campaigns, events, hackathons, and developer support **Vesting schedule**: 10% unlocked at genesis, 6-month cliff, 60-month total linear vesting #### **Airdrop** *105,221,229 \$NODE (15.5%)* Airdrops reward the early supporters who helped bootstrap the NodeOps Network, including active users, Testnet contributors, community members, and all Node Operators. Learn more about the airdrop allocation. **Vesting**: 80% unlocked at genesis, 10% at 6 months after TGE, 10% at 9 months after TGE. #### **IDO** *13,576,675 \$NODE (2%)* A fixed portion of 2% is allocated towards IDO to allow early users to participate in the \$NODE economy from the beginning. **Vesting:** 100% unlocked at IDO completion. #### **NodeOps Protocol incentives** *101,825,059 \$NODE (15%)* This allocation supports the Protocol’s core reward systems. It powers emissions tied to Compute workloads, validator performance, orchestrator Nodes (UNO), staking rewards, and other forms of measurable network participation across the Protocol. **Vesting:** 15% unlocked at TGE, 6 months cliff, 48 months total linear vesting. #### **Initial contributors** *101,825,059 \$NODE (15%)* Allocated to the team and contributors who brought NodeOps from idea to launch, including builders, researchers, and core supporters. Designed to: - Reward past work - Align long-term incentives - Support future hiring of top talent **Vesting: 0% unlocked at genesis, 12 months cliff, 60 months total linear vesting.** #### **Early backers** *152,137,590 \$NODE (22.5%)* These tokens go to investors and backers who believed in NodeOps early, supported development, provided capital, and have provided strategic guidance during the earliest stages of growth. **Vesting : 0% unlocked at genesis, 12-month cliff, 36-month total linear vesting.** ### \$NODE release schedule Discover how the \$NODE release schedule unfolds month by month with our [tokenomics simulator](https://nodeops.network/tokenomics?tab=release-schedule). You get to predict future distributions and unlock scenarios. ## Revenue share & optimal control of emissions ### **Dynamic mint & burn** NodeOps Network implements a dynamic mint and burn algorithm that ties token emissions to onchain revenue. Unlike fixed emission curves or speculative incentives, this model ensures \$NODE supply expands only when backed by economic activity, drawing heavily from the Burn-and-Mint Equilibrium (BME) framework popularized in DePIN protocols. The system operates through epoch-governed burn/mint ratios, daily emission caps, and transparent allocation, with all mints traceable to real network usage. For hands-on insight into how the dynamic mint and burn algorithm controls \$NODE supply, [try our simulator](https://nodeops.network/tokenomics?tab=dynamic-burn-mint) and examine upcoming release patterns. ### Core mint formula $Minted_t = Revenue_t / (2 * r(t) * P_t)$ Where: - $Revenue_t$ is daily protocol revenue (USD) - $P_t$ is \$NODE Token Price - $r(t)$ is the Burn/Mint ratio (adjusted each epoch) Note: The ratio r(t) is set via governance and **can be adjusted dynamically** based on token velocity, revenue velocity, and staking participation β€” a system rooted in **optimal dynamic control**. ### Governance-driven adaptive ratio control NodeOps starts with an **initial burn/mint ratio of 0.20** to stimulate early growth, and tightens emissions over time. This ensures early adopters, node operators, and stakers are fairly rewarded without long-term oversupply risk. **Example ratio cycle** | Epoch (Quarter) | Mint/Burn Ratio | Phase | | --- | --- | --- | | Q3 2025 | 0.20 | Bootstrapping incentives | | Q4 2025 | 0.32 | Moderate tapering | | Q1 2026 | 0.48 | Transition to baseline | | Q2+ 2026 | 0.72 | Long-term equilibrium | ## Revenue split Every \$1 earned as revenue onchain is split and distributed. Only the **non-burn portion** of revenue is used to mint \$NODE, ensuring all inflation is backed by economic value. See how revenue splits shape the \$NODE token supply; try the [tokenomics simulator](https://nodeops.network/tokenomics?tab=revenue-split) to test different scenarios and instantly visualize the impact. ## What next? - Learn more about the [\$NODE ecosystem](../Learn/README.md) - [Stake your \$NODE](./stake.md) - View the \$NODE in your wallet with [NodeOps Portal](/Guides/Portal) ## Disclaimer This content is provided for informational purposes only and should not be relied upon as legal, financial, investment, or tax advice. The \$NODE token is a utility asset intended solely for use within the NodeOps Network. Participation in the Genesis Airdrop and use of the NodeOps Network involve risk and should be undertaken only after careful consideration. Nothing in this site constitutes an offer to buy or sell securities or any financial instruments. Eligibility criteria and token allocations may be subject to change at NodeOps' discretion. You are solely responsible for ensuring compliance with all applicable laws and regulations in your jurisdiction. Always conduct independent research and consult with qualified advisors before making any decisions involving digital assets. $NODE is not available to individuals or entities located in, under the control of, residents, or nationals of the following restricted jurisdictions: Afghanistan, Canada, China, Iran, Iraq, North Korea, Pakistan, Syria, Ukraine, the United States, the United States Minor Outlying Islands, and the US Virgin Islands. Additionally, \$NODE is unavailable to any individual or entity subject to sanctions or listed on any sanctions list maintained by the United Nations, the United States (including OFAC’s SDN and Entity Lists), the European Union or its Member States, the United Kingdom, or any other applicable governmental authority β€” regardless of location. For additional information, ensure to thoroughly review our [Terms and Conditions of the \$NODE airdrop](https://nodeops-public.hel1.your-objectstorage.com/airdrop-TnC.pdf). --- ### $NODE Overview > Discover $NODE, the ERC-20 utility token powering NodeOps Network. Learn about contracts, staking, bridging, transfers, and the DePIN token economy. URL: https://docs.nodeops.network/Tokenomics \$NODE creates economic alignment between the participants of the NodeOps Network Protocol. Use this page as an entrypoint to discover more. ## $NODE's tokenomics \$NODE is an ERC-20 token with a community allocation of 47.5% of the genesis supply. [\$NODE's tokenomics](./node.md) are designed to control against inflation long term. ## \$NODE contracts | **Protocol contract details** | **Address** | Description | Chain | | --- | --- | --- | --- | | Airdrop pool contract | `0x2080FeE444118AFCe30fCb749802C18c0a980dB7` | Rewards issued in 2025 | [Arb](https://arbiscan.io/address/0x2080FeE444118AFCe30fCb749802C18c0a980dB7) | | Airdrop vesting contract | `0xcbA485746Fe9A96E56f264c750c4025b135129Df` | Vested airdrop allocations | [Eth](https://etherscan.io/address/0xcbA485746Fe9A96E56f264c750c4025b135129Df) | | Early backers vesting contract | `0x708aa8eAe215f9369C1caaB30f259c4E193CD426` | Vested allocations for early backers | [Bsc](https://bscscan.com/address/0x708aa8eAe215f9369C1caaB30f259c4E193CD426) | | Ecosystem vesting contract | `0xcDfC2Cc484E5Cf5669d34BA44260C83c4279f7B2` | Vested allocations for ecosystem activities | [Eth](https://etherscan.io/address/0xcDfC2Cc484E5Cf5669d34BA44260C83c4279f7B2) | | IDO contract | `0x746038a17EBbB4298F0946cade01D80c09858240` | Token issuance | [Eth](https://etherscan.io/address/0x746038a17EBbB4298F0946cade01D80c09858240)| | Incentives vesting contract | `0x1BCe1330E93D08f2996fDaEd23a9168B9e3ed090` | Vested allocations for Protocol incentives | [Eth](https://etherscan.io/address/0x1BCe1330E93D08f2996fDaEd23a9168B9e3ed090) | | Initial contributor vesting contract | `0x808A4650e2e27E0051db16c3089888cc92662e52` | Vested allocations for initial project contributors | [Bsc](https://bscscan.com/address/0x808A4650e2e27E0051db16c3089888cc92662e52) | | NODE to credits | `0x1BCe1330E93D08f2996fDaEd23a9168B9e3ed090` | Node to Credits onchain conversion | [Arb](https://arbiscan.io/address/0x1BCe1330E93D08f2996fDaEd23a9168B9e3ed090) | | Order registry contract | `0xC02ADd3D60aF95Bd7652D68c7D510F0d52f994Ef` | Revenue visibility | [Arb](https://arbiscan.io/address/0xC02ADd3D60aF95Bd7652D68c7D510F0d52f994Ef) | | Provider bonding contract | `0xcDfC2Cc484E5Cf5669d34BA44260C83c4279f7B2` | Provider collateral locking for registration and machine onboarding | [Arb](https://arbiscan.io/address/0xcDfC2Cc484E5Cf5669d34BA44260C83c4279f7B2) | | Staking contract (ARB)| `0x808A4650e2e27E0051db16c3089888cc92662e52` | Rewards | [Arb](https://arbiscan.io/address/0x808A4650e2e27E0051db16c3089888cc92662e52) | | Staking contract (BSC)| `0xcbA485746Fe9A96E56f264c750c4025b135129Df` | Rewards | [Bsc](https://bscscan.com/address/0xcbA485746Fe9A96E56f264c750c4025b135129Df) | ### Burn address To control against inflation, as revenue is earned, the token is burned. The burn wallet is found at the Ethereum address [0x2080FeE444118AFCe30fCb749802C18c0a980dB7](https://etherscan.io/address/0x2080FeE444118AFCe30fCb749802C18c0a980dB7). ## NodeOps Portal NodeOps Network provides a unified app to assist you to manage any \$NODE you own: - [Bridge](./bridge.md) - [Transfer](./transfer.md) - [Stake](./stake.md) - and [more](Learn/Products/DeFi-Services/staking.md) ## What is $NODE for? \$NODE is more than a token that you can stake or trade. $NODE is a utility token that can be converted to credits for access to the products and services in [Cloud Marketplace](/Learn/Products/Cloud/README.md) and the [Node-as-a-Service Console](/Guides/Console/README.md). ## View your \$NODE You may view your \$NODE from the [Portal app](/Guides/Portal) or directly in your EVM-compatible wallet. **Show me how to add the \$NODE token to my wallet** Wallets differ slightly in their flows, this demonstration uses MetaMask. 1. Log in to your wallet. 2. From the **Tokens** tab, select the hamburger menu and click **Import tokens**. 3. Click **Custom token**, and select the chain your \$NODE is on. 4. Copy the \$NODE token address and enter it into the **Token contract address** field: > This demo shows Arbitrum One's \$NODE. 5. If the token symbol comes up as NODE, you're good to go, click **Next**. Congratulations, your \$NODE holdings are now visible in your wallet. --- ### Stake $NODE > Stake $NODE tokens and earn yield using NodeOps Portal. Lock your tokens in the staking interface to participate in the NodeOps DePIN network. URL: https://docs.nodeops.network/Tokenomics/stake 🌟 Status: Live on Mainnet/s > **Tip: TL;DR** [NodeOps Portal](https://portal.nodeops.network) let's you stake \$NODE and other supported tokens. ## Stake \$NODE with NodeOps Portal [NodeOps Portal](https://portal.nodeops.network) provides a staking interface to lock your \$NODE and earn yield. Use the video or walkthrough to understand how to stake \$NODE to earn \$NODE yield. **Show me video** For a real-time, guided walkthrough, checkout the [YouTube of **How to stake \$NODE**](https://www.youtube.com/watch?v=8ozK86yBWVw). ### Prerequisites - EVM-compatible wallet containing \$NODE - Gas funds ### Step 1: Lock your \$NODE 1. Logged into [NodeOps Portal](https://portal.nodeops.network), click **Stake** on the left hand menu. 2. Enter the amount of \$NODE to stake. 3. Select your lockup period. > The longer you stake, the better the rewards. 4. Click **Approve NODE**, review the transaction details, and confirm in your wallet. 5. Click **Stake**, review the transaction details, and confirm in your wallet. ### Step 2: (Optional) verify the transfer Click **View on explorer** to examine the onchain record of the transaction. ## Stay safe out there Scammers hijack funds; keep away from them: - Only use the official NodeOps Portal: [https://portal.nodeops.network](https://portal.nodeops.network) - Never share your private keys ## What next? - See all the [Portal functions and features](/Guides/Portal) - Learn about the [\$NODE tokenomics](./node.md) - Learn more about the [\$NODE ecosystem](../Learn/README.md) --- ### Transfer $NODE > Transfer $NODE tokens between wallets securely using NodeOps Portal. Move your tokens trustlessly on the same chain with the official NodeOps app. URL: https://docs.nodeops.network/Tokenomics/transfer 🌟 Status: Live on Mainnet/s > **Tip: TL;DR** [NodeOps Portal](https://portal.nodeops.network) allows you to transfer \$NODE between wallets. ## Transfer \$NODE with NodeOps Portal [NodeOps Portal](https://portal.nodeops.network) provides a trustless asset transfer mechanism to move \$NODE between wallets. This guide walks you through transferring \$NODE. Use the video or walkthrough to understand how to transfer \$NODE across chains. **Show me video** #### Prerequisites - Wallets: - Sending wallet: EVM-compatible wallet containing \$NODE - Receiving wallet: EVM-compatible wallet - Funds for gas on the chain your $NODE sits on - You are logged into the [NodeOps Portal](https://portal.nodeops.network) with the sending wallet containing your \$NODE 1. Click **Transfer** on the left hand menu. **Show me** 2. Enter the amount of \$NODE to move. 3. Enter the destination wallet. 4. Click **Transfer**, review the transaction details, and confirm in your wallet. **Show me** #### (Optional) verify the transfer Click **View on explorer** to examine the onchain record of the transaction. Congratulations, the \$NODE has been transferred via the same chain as the original sending wallet's \$NODE. ## Stay safe out there Scammers hijack funds; keep away from them: - Only use the official NodeOps Portal: [https://portal.nodeops.network](https://portal.nodeops.network) - Never share your private keys ## What next? - See all the [Portal functions and features](/Guides/Portal) - Learn about the [\$NODE tokenomics](./node.md) - Learn more about the [\$NODE ecosystem](../Learn/README.md) --- --- ## Compare ### AI & Machine Learning Nodes β€” Compare & Deploy > Compare ai & machine learning Nodes available on NodeOps Console. Protocols building decentralized AI infrastructure including Compute, data verification, and model training URL: https://docs.nodeops.network/Compare/ai-infrastructure-nodes Protocols building decentralized AI infrastructure including Compute, data verification, and model training NodeOps Console lets you deploy and manage ai & machine learning Nodes with no manual setup β€” choose a protocol, subscribe, and your Node is running in seconds. ## Available protocols | Protocol | Node Type | License Required | Delegation | From ($/mo) | |----------|-----------|-----------------|------------|-------------| | [Aethir](/Guides/Console/Managed-Nodes/aethir) | Checker | Yes | No | $6.00 | | [CARV](/Guides/Console/Managed-Nodes/carv) | Verifier | Yes | Yes | $20.00 | | [iAgent](/Guides/Console/Managed-Nodes/iagent/bootstrapping) | Node | Yes | Yes | Contact | | [Nexus](/Guides/Console/Managed-Nodes/nexus) | Prover | No | No | $15.00 | | [0G](/Guides/Console/Managed-Nodes/og-alignment) | Alignment | Yes | Yes | Contact | | [PlayAI](/Guides/Console/Managed-Nodes/playai) | Oasis | Yes | No | $9.00 | | [Rivalz](/Guides/Console/Managed-Nodes/rivalz) | zNode | Yes | No | $3.75 | ## Pricing comparison Compare monthly subscription costs across ai & machine learning protocols: | Protocol | 1 Month | 3 Months | 6 Months | 12 Months | |----------|---------|----------|----------|-----------| | Aethir | $6.00 | $5.70 | $5.40 | $4.80 | | CARV | $20.00 | $18.00 | $16.00 | $14.00 | | Nexus | $15.00 | $14.25 | $13.50 | $12.00 | | PlayAI | $9.00 | $8.55 | $8.10 | $7.20 | | Rivalz | $3.75 | $3.56 | $3.38 | $3.00 | > Longer subscriptions include discounts up to 30%. Prices shown are per license per month. ## Protocol details ### Aethir Cloud computing infrastructure platform revolutionizing the ownership, distribution, and utilization of enterprise-grade GPUs through a decentralized framework. - **Node Type:** Checker - **License Required:** Yes β€” Checker Node Key License - **Delegation:** Not supported - **Starting Price:** $6.00/month [Deploy Aethir Node](/Guides/Console/Managed-Nodes/aethir) | [Get Started with Console](/Get-Started/Console/README.md) ### CARV Modular data layer facilitating data exchange and value distribution across gaming, AI, and beyond. Verifier Nodes maintain protocol integrity. - **Node Type:** Verifier - **License Required:** Yes β€” CARV Node NFT - **Delegation:** Supported - **Starting Price:** $20.00/month [Deploy CARV Node](/Guides/Console/Managed-Nodes/carv) | [Get Started with Console](/Get-Started/Console/README.md) ### iAgent AI agent infrastructure protocol with bootstrapping and delegation capabilities for decentralized AI services. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Supported [Deploy iAgent Node](/Guides/Console/Managed-Nodes/iagent/bootstrapping) | [Get Started with Console](/Get-Started/Console/README.md) ### Nexus Hyperscale decentralized supercomputer for verifiable computation, purpose-built for AI workloads, blockchain, and privacy-enhancing technologies. - **Node Type:** Prover - **License Required:** No - **Delegation:** Not supported - **Starting Price:** $15.00/month [Deploy Nexus Node](/Guides/Console/Managed-Nodes/nexus) | [Get Started with Console](/Get-Started/Console/README.md) ### 0G Decentralized AI operating system providing scalable infrastructure for AI applications and data availability. - **Node Type:** Alignment - **License Required:** Yes β€” 0G Alignment NFT - **Delegation:** Supported [Deploy 0G Node](/Guides/Console/Managed-Nodes/og-alignment) | [Get Started with Console](/Get-Started/Console/README.md) ### PlayAI AI orchestration layer for consumer intelligence, enabling data access, rewards, and enhanced user experiences across consumer-focused products. - **Node Type:** Oasis - **License Required:** Yes β€” PlayAI Oasis NFT - **Delegation:** Not supported - **Starting Price:** $9.00/month [Deploy PlayAI Node](/Guides/Console/Managed-Nodes/playai) | [Get Started with Console](/Get-Started/Console/README.md) ### Rivalz AI Intelligence Layer powered by DePIN, utilizing Dymension with Celestia and Eigen to operate validator zNodes that track data flows. - **Node Type:** zNode - **License Required:** Yes β€” zNode License NFT - **Delegation:** Not supported - **Starting Price:** $3.75/month [Deploy Rivalz Node](/Guides/Console/Managed-Nodes/rivalz) | [Get Started with Console](/Get-Started/Console/README.md) ## FAQ ### What are ai & machine learning Nodes? Protocols building decentralized AI infrastructure including Compute, data verification, and model training ### How much does it cost to run ai & machine learning Nodes on NodeOps? Pricing starts from $3.75/month. Longer subscriptions receive discounts up to 30%. ### Do I need technical expertise to run these Nodes? No. NodeOps Console handles all hardware, installation, updates, and uptime management. You can deploy Nodes with just a few clicks using the NaaS (Node-as-a-Service) model. ## What next? - [Get Started with NodeOps Console](/Get-Started/Console/README.md) to deploy your first Node - View all [supported protocols](/Guides/Console) on NodeOps Console - Learn about [Node-as-a-Service](/Learn/Glossary/naas) and how NodeOps handles the technical complexity --- ### Data Availability Nodes β€” Compare & Deploy > Compare data availability Nodes available on NodeOps Console. Modular blockchain protocols focused on data availability layers for scalable infrastructure URL: https://docs.nodeops.network/Compare/data-availability-nodes Modular blockchain protocols focused on data availability layers for scalable infrastructure NodeOps Console lets you deploy and manage data availability Nodes with no manual setup β€” choose a protocol, subscribe, and your Node is running in seconds. ## Available protocols | Protocol | Node Type | License Required | Delegation | From ($/mo) | |----------|-----------|-----------------|------------|-------------| | [Avail](/Guides/Console/Managed-Nodes/avail) | Validator | No | No | $7.50 | | [Celestia](/Guides/Console/Managed-Nodes/celestia) | Light | No | No | $15.00 | | [0G](/Guides/Console/Managed-Nodes/og-alignment) | Alignment | Yes | Yes | Contact | ## Pricing comparison Compare monthly subscription costs across data availability protocols: | Protocol | 1 Month | 3 Months | 6 Months | 12 Months | |----------|---------|----------|----------|-----------| | Avail | $7.50 | $7.13 | $6.75 | $6.00 | | Celestia | $15.00 | $14.25 | $13.50 | $12.00 | > Longer subscriptions include discounts up to 30%. Prices shown are per license per month. ## Protocol details ### Avail Web3 infrastructure layer allowing modular execution layers to scale and interoperate in a trust-minimized way through data availability. - **Node Type:** Validator - **License Required:** No - **Delegation:** Not supported - **Starting Price:** $7.50/month [Deploy Avail Node](/Guides/Console/Managed-Nodes/avail) | [Get Started with Console](/Get-Started/Console/README.md) ### Celestia Modular blockchain powering applications with full-stack customizability through a dedicated data availability layer. - **Node Type:** Light - **License Required:** No - **Delegation:** Not supported - **Starting Price:** $15.00/month [Deploy Celestia Node](/Guides/Console/Managed-Nodes/celestia) | [Get Started with Console](/Get-Started/Console/README.md) ### 0G Decentralized AI operating system providing scalable infrastructure for AI applications and data availability. - **Node Type:** Alignment - **License Required:** Yes β€” 0G Alignment NFT - **Delegation:** Supported [Deploy 0G Node](/Guides/Console/Managed-Nodes/og-alignment) | [Get Started with Console](/Get-Started/Console/README.md) ## FAQ ### What are data availability Nodes? Modular blockchain protocols focused on data availability layers for scalable infrastructure ### How much does it cost to run data availability Nodes on NodeOps? Pricing starts from $7.50/month. Longer subscriptions receive discounts up to 30%. ### Do I need technical expertise to run these Nodes? No. NodeOps Console handles all hardware, installation, updates, and uptime management. You can deploy Nodes with just a few clicks using the NaaS (Node-as-a-Service) model. ## What next? - [Get Started with NodeOps Console](/Get-Started/Console/README.md) to deploy your first Node - View all [supported protocols](/Guides/Console) on NodeOps Console - Learn about [Node-as-a-Service](/Learn/Glossary/naas) and how NodeOps handles the technical complexity --- ### Decentralized Compute Nodes β€” Compare & Deploy > Compare decentralized Compute Nodes available on NodeOps Console. Protocols providing decentralized computing resources including GPU and ZK proof generation URL: https://docs.nodeops.network/Compare/decentralized-compute-nodes Protocols providing decentralized computing resources including GPU and ZK proof generation NodeOps Console lets you deploy and manage decentralized Compute Nodes with no manual setup β€” choose a protocol, subscribe, and your Node is running in seconds. ## Available protocols | Protocol | Node Type | License Required | Delegation | From ($/mo) | |----------|-----------|-----------------|------------|-------------| | [Lumoz](/Guides/Console/Managed-Nodes/lumoz) | Node | Yes | No | Contact | | [Nexus](/Guides/Console/Managed-Nodes/nexus) | Prover | No | No | $15.00 | ## Pricing comparison Compare monthly subscription costs across decentralized Compute protocols: | Protocol | 1 Month | 3 Months | 6 Months | 12 Months | |----------|---------|----------|----------|-----------| | Nexus | $15.00 | $14.25 | $13.50 | $12.00 | > Longer subscriptions include discounts up to 30%. Prices shown are per license per month. ## Protocol details ### Lumoz ZK Compute layer providing zero-knowledge proof infrastructure for scalable blockchain applications. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Lumoz Node](/Guides/Console/Managed-Nodes/lumoz) | [Get Started with Console](/Get-Started/Console/README.md) ### Nexus Hyperscale decentralized supercomputer for verifiable computation, purpose-built for AI workloads, blockchain, and privacy-enhancing technologies. - **Node Type:** Prover - **License Required:** No - **Delegation:** Not supported - **Starting Price:** $15.00/month [Deploy Nexus Node](/Guides/Console/Managed-Nodes/nexus) | [Get Started with Console](/Get-Started/Console/README.md) ## FAQ ### What are decentralized Compute Nodes? Protocols providing decentralized computing resources including GPU and ZK proof generation ### How much does it cost to run decentralized Compute Nodes on NodeOps? Pricing starts from $15.00/month. Longer subscriptions receive discounts up to 30%. ### Do I need technical expertise to run these Nodes? No. NodeOps Console handles all hardware, installation, updates, and uptime management. You can deploy Nodes with just a few clicks using the NaaS (Node-as-a-Service) model. ## What next? - [Get Started with NodeOps Console](/Get-Started/Console/README.md) to deploy your first Node - View all [supported protocols](/Guides/Console) on NodeOps Console - Learn about [Node-as-a-Service](/Learn/Glossary/naas) and how NodeOps handles the technical complexity --- ### NFT Delegation Nodes β€” Earn Rewards Passively > Delegate your NFT Node license to NodeOps and earn protocol rewards without running infrastructure. Compare protocols supporting NFT delegation. URL: https://docs.nodeops.network/Compare/delegation-supported-nodes NFT delegation lets you earn protocol rewards by delegating your Node license to NodeOps β€” no subscription fees, no infrastructure management. NodeOps runs the Node and takes a small commission from rewards. ## Delegation-supported protocols | Protocol | Node Type | License Type | Guide | |----------|-----------|-------------|-------| | CARV | Verifier | CARV Node NFT | [Deploy](/Guides/Console/Managed-Nodes/carv) | | iAgent | Node | NFT License | [Deploy](/Guides/Console/Managed-Nodes/iagent/bootstrapping) | | 0G | Alignment | 0G Alignment NFT | [Deploy](/Guides/Console/Managed-Nodes/og-alignment) | | Sophon | Node | NFT License | [Deploy](/Guides/Console/Managed-Nodes/sophon) | | XAI | Sentry | Sentry Key | [Deploy](/Guides/Console/Managed-Nodes/xai) | ## How delegation works 1. **Connect your wallet** containing the NFT license to [NodeOps Console](https://console.nodeops.network/) 2. **Select the commission-based model** β€” no subscription fees required 3. **Delegate your license** β€” NodeOps creates a burner wallet and handles all operations 4. **Earn rewards** β€” protocol rewards are distributed to your wallet minus a small commission > Learn more about [commission-based delegation](/Get-Started/Console/commission-based). ### CARV Modular data layer facilitating data exchange and value distribution across gaming, AI, and beyond. Verifier Nodes maintain protocol integrity. - **License:** CARV Node NFT - **Node Type:** Verifier [Delegate CARV License](/Guides/Console/Managed-Nodes/carv) ### iAgent AI agent infrastructure protocol with bootstrapping and delegation capabilities for decentralized AI services. - **License:** NFT License - **Node Type:** Node [Delegate iAgent License](/Guides/Console/Managed-Nodes/iagent/bootstrapping) ### 0G Decentralized AI operating system providing scalable infrastructure for AI applications and data availability. - **License:** 0G Alignment NFT - **Node Type:** Alignment [Delegate 0G License](/Guides/Console/Managed-Nodes/og-alignment) ### Sophon Web3 protocol offering managed Node services with commission-based delegation support through NodeOps Console. - **License:** NFT License - **Node Type:** Node [Delegate Sophon License](/Guides/Console/Managed-Nodes/sophon) ### XAI Gaming blockchain with Sentry Nodes that validate network operations. Offers basic shared and premium dedicated operator plans. - **License:** Sentry Key - **Node Type:** Sentry [Delegate XAI License](/Guides/Console/Managed-Nodes/xai) ## What next? - [Get Started with delegation](/Get-Started/Console/commission-based) - Compare [no-license-required Nodes](/Compare/no-license-required-nodes) for subscription-based options - Learn about [NodeOps Console](/Guides/Console) and all supported protocols --- ### Gaming & Metaverse Nodes β€” Compare & Deploy > Compare gaming & metaverse Nodes available on NodeOps Console. Gaming-focused blockchain protocols with validator and infrastructure Nodes URL: https://docs.nodeops.network/Compare/gaming-blockchain-nodes Gaming-focused blockchain protocols with validator and infrastructure Nodes NodeOps Console lets you deploy and manage gaming & metaverse Nodes with no manual setup β€” choose a protocol, subscribe, and your Node is running in seconds. ## Available protocols | Protocol | Node Type | License Required | Delegation | From ($/mo) | |----------|-----------|-----------------|------------|-------------| | [Beam](/Guides/Console/Managed-Nodes/beam) | Validator | Yes | No | $40.00 | | [CARV](/Guides/Console/Managed-Nodes/carv) | Verifier | Yes | Yes | $20.00 | | [Hychain](/Guides/Console/Managed-Nodes/hychain) | Node | Yes | No | Contact | | [Vemp Horizon](/Guides/Console/Managed-Nodes/vemp-horizon) | Node | Yes | No | Contact | | [XAI](/Guides/Console/Managed-Nodes/xai) | Sentry | Yes | Yes | $15.00 | ## Pricing comparison Compare monthly subscription costs across gaming & metaverse protocols: | Protocol | 1 Month | 3 Months | 6 Months | 12 Months | |----------|---------|----------|----------|-----------| | Beam | $40.00 | $38.00 | $36.00 | $32.00 | | CARV | $20.00 | $18.00 | $16.00 | $14.00 | | XAI | $15.00 | $14.25 | $13.50 | $12.75 | > Longer subscriptions include discounts up to 30%. Prices shown are per license per month. ## Protocol details ### Beam Permissionless proof-of-stake Layer 1 blockchain for gaming. Beam Nodes validate transactions and add new blocks to the network. - **Node Type:** Validator - **License Required:** Yes β€” Beam:Node Token (ERC-721) + 20,000 BEAM minimum stake - **Delegation:** Not supported - **Starting Price:** $40.00/month [Deploy Beam Node](/Guides/Console/Managed-Nodes/beam) | [Get Started with Console](/Get-Started/Console/README.md) ### CARV Modular data layer facilitating data exchange and value distribution across gaming, AI, and beyond. Verifier Nodes maintain protocol integrity. - **Node Type:** Verifier - **License Required:** Yes β€” CARV Node NFT - **Delegation:** Supported - **Starting Price:** $20.00/month [Deploy CARV Node](/Guides/Console/Managed-Nodes/carv) | [Get Started with Console](/Get-Started/Console/README.md) ### Hychain Gaming-focused blockchain designed for high-performance game economies and infrastructure. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Hychain Node](/Guides/Console/Managed-Nodes/hychain) | [Get Started with Console](/Get-Started/Console/README.md) ### Vemp Horizon Web3 gaming and metaverse infrastructure protocol with managed Node services. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Vemp Horizon Node](/Guides/Console/Managed-Nodes/vemp-horizon) | [Get Started with Console](/Get-Started/Console/README.md) ### XAI Gaming blockchain with Sentry Nodes that validate network operations. Offers basic shared and premium dedicated operator plans. - **Node Type:** Sentry - **License Required:** Yes β€” Sentry Key - **Delegation:** Supported - **Starting Price:** $15.00/month [Deploy XAI Node](/Guides/Console/Managed-Nodes/xai) | [Get Started with Console](/Get-Started/Console/README.md) ## FAQ ### What are gaming & metaverse Nodes? Gaming-focused blockchain protocols with validator and infrastructure Nodes ### How much does it cost to run gaming & metaverse Nodes on NodeOps? Pricing starts from $15.00/month. Longer subscriptions receive discounts up to 30%. ### Do I need technical expertise to run these Nodes? No. NodeOps Console handles all hardware, installation, updates, and uptime management. You can deploy Nodes with just a few clicks using the NaaS (Node-as-a-Service) model. ## What next? - [Get Started with NodeOps Console](/Get-Started/Console/README.md) to deploy your first Node - View all [supported protocols](/Guides/Console) on NodeOps Console - Learn about [Node-as-a-Service](/Learn/Glossary/naas) and how NodeOps handles the technical complexity --- ### No License Required Nodes β€” Deploy Without NFTs > Run blockchain Nodes on NodeOps Console without purchasing an NFT license. Compare no-license-required protocols with pricing and deployment guides. URL: https://docs.nodeops.network/Compare/no-license-required-nodes These protocols let you start running Nodes immediately without purchasing an NFT license or key. Connect your wallet, subscribe, and deploy. ## No-license protocols | Protocol | Node Type | From ($/mo) | Guide | |----------|-----------|-------------|-------| | Avail | Validator | $7.50 | [Deploy](/Guides/Console/Managed-Nodes/avail) | | Celestia | Light | $15.00 | [Deploy](/Guides/Console/Managed-Nodes/celestia) | | Nexus | Prover | $15.00 | [Deploy](/Guides/Console/Managed-Nodes/nexus) | ### Avail Web3 infrastructure layer allowing modular execution layers to scale and interoperate in a trust-minimized way through data availability. **Prerequisites:** EVM-compatible wallet [Deploy Avail Node](/Guides/Console/Managed-Nodes/avail) ### Celestia Modular blockchain powering applications with full-stack customizability through a dedicated data availability layer. **Prerequisites:** EVM-compatible wallet [Deploy Celestia Node](/Guides/Console/Managed-Nodes/celestia) ### Nexus Hyperscale decentralized supercomputer for verifiable computation, purpose-built for AI workloads, blockchain, and privacy-enhancing technologies. **Prerequisites:** EVM-compatible wallet [Deploy Nexus Node](/Guides/Console/Managed-Nodes/nexus) ## What next? - Looking for protocols that support delegation? See [Delegation-Supported Nodes](/Compare/delegation-supported-nodes) - [Get Started with NodeOps Console](/Get-Started/Console/README.md) --- ### Compare Blockchain Nodes > Compare blockchain and protocol Nodes available on NodeOps Console. Find the right Node by category, pricing, license requirements, and delegation support. URL: https://docs.nodeops.network/Compare ## Find the right Node for you NodeOps Console supports **23 protocols** across multiple categories. Use the guides below to compare Nodes by use case, requirements, and pricing. ### Browse by category - [AI & Machine Learning](/Compare/ai-infrastructure-nodes) β€” Protocols building decentralized AI infrastructure including Compute, data verification, and model training - [Gaming & Metaverse](/Compare/gaming-blockchain-nodes) β€” Gaming-focused blockchain protocols with validator and infrastructure Nodes - [Data Availability](/Compare/data-availability-nodes) β€” Modular blockchain protocols focused on data availability layers for scalable infrastructure - [Web3 Infrastructure](/Compare/web3-infrastructure-nodes) β€” Core Web3 infrastructure protocols including Compute, storage, and communication layers - [Validator & Staking](/Compare/validator-staking-nodes) β€” Proof-of-stake validator Nodes that secure blockchain networks and earn staking rewards - [Decentralized Compute](/Compare/decentralized-compute-nodes) β€” Protocols providing decentralized computing resources including GPU and ZK proof generation ### Quick comparison | Protocol | Node Type | License Required | Delegation | From ($/mo) | |----------|-----------|-----------------|------------|-------------| | [Aethir](/Guides/Console/Managed-Nodes/aethir) | Checker | Yes | No | $6.00 | | [Avail](/Guides/Console/Managed-Nodes/avail) | Validator | No | No | $7.50 | | [Beam](/Guides/Console/Managed-Nodes/beam) | Validator | Yes | No | $40.00 | | [CARV](/Guides/Console/Managed-Nodes/carv) | Verifier | Yes | Yes | $20.00 | | [Celestia](/Guides/Console/Managed-Nodes/celestia) | Light | No | No | $15.00 | | [Captain & Company](/Guides/Console/Managed-Nodes/capnco) | Node | Yes | No | Contact | | [DIN](/Guides/Console/Managed-Nodes/din) | Node | Yes | No | Contact | | [Fuse](/Guides/Console/Managed-Nodes/fuse) | Node | Yes | No | Contact | | [Huddle01](/Guides/Console/Managed-Nodes/huddle01) | Node | Yes | No | Contact | | [Hybrid](/Guides/Console/Managed-Nodes/hybrid) | Node | Yes | No | Contact | | [Hychain](/Guides/Console/Managed-Nodes/hychain) | Node | Yes | No | Contact | | [iAgent](/Guides/Console/Managed-Nodes/iagent/bootstrapping) | Node | Yes | Yes | Contact | | [KIP](/Guides/Console/Managed-Nodes/kip) | Node | Yes | No | Contact | | [Lumoz](/Guides/Console/Managed-Nodes/lumoz) | Node | Yes | No | Contact | | [Nexus](/Guides/Console/Managed-Nodes/nexus) | Prover | No | No | $15.00 | | [0G](/Guides/Console/Managed-Nodes/og-alignment) | Alignment | Yes | Yes | Contact | | [OpenPad](/Guides/Console/Managed-Nodes/openpad) | Node | Yes | No | Contact | | [PlayAI](/Guides/Console/Managed-Nodes/playai) | Oasis | Yes | No | $9.00 | | [Rivalz](/Guides/Console/Managed-Nodes/rivalz) | zNode | Yes | No | $3.75 | | [Sophon](/Guides/Console/Managed-Nodes/sophon) | Node | Yes | Yes | Contact | | [Vemp Horizon](/Guides/Console/Managed-Nodes/vemp-horizon) | Node | Yes | No | Contact | | [XAI](/Guides/Console/Managed-Nodes/xai) | Sentry | Yes | Yes | $15.00 | | [XProtocol](/Guides/Console/Managed-Nodes/xprotocol) | Node | Yes | No | Contact | ### No license required These protocols let you start running Nodes without purchasing an NFT license: - [Avail](/Guides/Console/Managed-Nodes/avail) β€” Validator Node from $7.50/mo - [Celestia](/Guides/Console/Managed-Nodes/celestia) β€” Light Node from $15.00/mo - [Nexus](/Guides/Console/Managed-Nodes/nexus) β€” Prover Node from $15.00/mo ### Delegation supported These protocols support NFT license delegation, letting you earn rewards without managing infrastructure: - [CARV](/Guides/Console/Managed-Nodes/carv) β€” Modular data layer facilitating data exchange and value distribution across gaming, AI, and beyond. Verifier Nodes maintain protocol integrity. - [iAgent](/Guides/Console/Managed-Nodes/iagent/bootstrapping) β€” AI agent infrastructure protocol with bootstrapping and delegation capabilities for decentralized AI services. - [0G](/Guides/Console/Managed-Nodes/og-alignment) β€” Decentralized AI operating system providing scalable infrastructure for AI applications and data availability. - [Sophon](/Guides/Console/Managed-Nodes/sophon) β€” Web3 protocol offering managed Node services with commission-based delegation support through NodeOps Console. - [XAI](/Guides/Console/Managed-Nodes/xai) β€” Gaming blockchain with Sentry Nodes that validate network operations. Offers basic shared and premium dedicated operator plans. ## What next? - [Get Started with NodeOps Console](/Get-Started/Console/README.md) to deploy your first Node - Learn about [Node-as-a-Service (NaaS)](/Learn/Glossary/naas) and how NodeOps simplifies Node running - Explore the [NodeOps Cloud Marketplace](/Guides/Marketplace) for Compute templates --- ### Validator & Staking Nodes β€” Compare & Deploy > Compare validator & staking Nodes available on NodeOps Console. Proof-of-stake validator Nodes that secure blockchain networks and earn staking rewards URL: https://docs.nodeops.network/Compare/validator-staking-nodes Proof-of-stake validator Nodes that secure blockchain networks and earn staking rewards NodeOps Console lets you deploy and manage validator & staking Nodes with no manual setup β€” choose a protocol, subscribe, and your Node is running in seconds. ## Available protocols | Protocol | Node Type | License Required | Delegation | From ($/mo) | |----------|-----------|-----------------|------------|-------------| | [Avail](/Guides/Console/Managed-Nodes/avail) | Validator | No | No | $7.50 | | [Beam](/Guides/Console/Managed-Nodes/beam) | Validator | Yes | No | $40.00 | | [XAI](/Guides/Console/Managed-Nodes/xai) | Sentry | Yes | Yes | $15.00 | ## Pricing comparison Compare monthly subscription costs across validator & staking protocols: | Protocol | 1 Month | 3 Months | 6 Months | 12 Months | |----------|---------|----------|----------|-----------| | Avail | $7.50 | $7.13 | $6.75 | $6.00 | | Beam | $40.00 | $38.00 | $36.00 | $32.00 | | XAI | $15.00 | $14.25 | $13.50 | $12.75 | > Longer subscriptions include discounts up to 30%. Prices shown are per license per month. ## Protocol details ### Avail Web3 infrastructure layer allowing modular execution layers to scale and interoperate in a trust-minimized way through data availability. - **Node Type:** Validator - **License Required:** No - **Delegation:** Not supported - **Starting Price:** $7.50/month [Deploy Avail Node](/Guides/Console/Managed-Nodes/avail) | [Get Started with Console](/Get-Started/Console/README.md) ### Beam Permissionless proof-of-stake Layer 1 blockchain for gaming. Beam Nodes validate transactions and add new blocks to the network. - **Node Type:** Validator - **License Required:** Yes β€” Beam:Node Token (ERC-721) + 20,000 BEAM minimum stake - **Delegation:** Not supported - **Starting Price:** $40.00/month [Deploy Beam Node](/Guides/Console/Managed-Nodes/beam) | [Get Started with Console](/Get-Started/Console/README.md) ### XAI Gaming blockchain with Sentry Nodes that validate network operations. Offers basic shared and premium dedicated operator plans. - **Node Type:** Sentry - **License Required:** Yes β€” Sentry Key - **Delegation:** Supported - **Starting Price:** $15.00/month [Deploy XAI Node](/Guides/Console/Managed-Nodes/xai) | [Get Started with Console](/Get-Started/Console/README.md) ## FAQ ### What are validator & staking Nodes? Proof-of-stake validator Nodes that secure blockchain networks and earn staking rewards ### How much does it cost to run validator & staking Nodes on NodeOps? Pricing starts from $7.50/month. Longer subscriptions receive discounts up to 30%. ### Do I need technical expertise to run these Nodes? No. NodeOps Console handles all hardware, installation, updates, and uptime management. You can deploy Nodes with just a few clicks using the NaaS (Node-as-a-Service) model. ## What next? - [Get Started with NodeOps Console](/Get-Started/Console/README.md) to deploy your first Node - View all [supported protocols](/Guides/Console) on NodeOps Console - Learn about [Node-as-a-Service](/Learn/Glossary/naas) and how NodeOps handles the technical complexity --- ### Web3 Infrastructure Nodes β€” Compare & Deploy > Compare web3 infrastructure Nodes available on NodeOps Console. Core Web3 infrastructure protocols including Compute, storage, and communication layers URL: https://docs.nodeops.network/Compare/web3-infrastructure-nodes Core Web3 infrastructure protocols including Compute, storage, and communication layers NodeOps Console lets you deploy and manage web3 infrastructure Nodes with no manual setup β€” choose a protocol, subscribe, and your Node is running in seconds. ## Available protocols | Protocol | Node Type | License Required | Delegation | From ($/mo) | |----------|-----------|-----------------|------------|-------------| | [Aethir](/Guides/Console/Managed-Nodes/aethir) | Checker | Yes | No | $6.00 | | [Avail](/Guides/Console/Managed-Nodes/avail) | Validator | No | No | $7.50 | | [Celestia](/Guides/Console/Managed-Nodes/celestia) | Light | No | No | $15.00 | | [Captain & Company](/Guides/Console/Managed-Nodes/capnco) | Node | Yes | No | Contact | | [DIN](/Guides/Console/Managed-Nodes/din) | Node | Yes | No | Contact | | [Fuse](/Guides/Console/Managed-Nodes/fuse) | Node | Yes | No | Contact | | [Huddle01](/Guides/Console/Managed-Nodes/huddle01) | Node | Yes | No | Contact | | [Hybrid](/Guides/Console/Managed-Nodes/hybrid) | Node | Yes | No | Contact | | [Hychain](/Guides/Console/Managed-Nodes/hychain) | Node | Yes | No | Contact | | [iAgent](/Guides/Console/Managed-Nodes/iagent/bootstrapping) | Node | Yes | Yes | Contact | | [KIP](/Guides/Console/Managed-Nodes/kip) | Node | Yes | No | Contact | | [Lumoz](/Guides/Console/Managed-Nodes/lumoz) | Node | Yes | No | Contact | | [0G](/Guides/Console/Managed-Nodes/og-alignment) | Alignment | Yes | Yes | Contact | | [OpenPad](/Guides/Console/Managed-Nodes/openpad) | Node | Yes | No | Contact | | [Sophon](/Guides/Console/Managed-Nodes/sophon) | Node | Yes | Yes | Contact | | [Vemp Horizon](/Guides/Console/Managed-Nodes/vemp-horizon) | Node | Yes | No | Contact | | [XProtocol](/Guides/Console/Managed-Nodes/xprotocol) | Node | Yes | No | Contact | ## Pricing comparison Compare monthly subscription costs across web3 infrastructure protocols: | Protocol | 1 Month | 3 Months | 6 Months | 12 Months | |----------|---------|----------|----------|-----------| | Aethir | $6.00 | $5.70 | $5.40 | $4.80 | | Avail | $7.50 | $7.13 | $6.75 | $6.00 | | Celestia | $15.00 | $14.25 | $13.50 | $12.00 | > Longer subscriptions include discounts up to 30%. Prices shown are per license per month. ## Protocol details ### Aethir Cloud computing infrastructure platform revolutionizing the ownership, distribution, and utilization of enterprise-grade GPUs through a decentralized framework. - **Node Type:** Checker - **License Required:** Yes β€” Checker Node Key License - **Delegation:** Not supported - **Starting Price:** $6.00/month [Deploy Aethir Node](/Guides/Console/Managed-Nodes/aethir) | [Get Started with Console](/Get-Started/Console/README.md) ### Avail Web3 infrastructure layer allowing modular execution layers to scale and interoperate in a trust-minimized way through data availability. - **Node Type:** Validator - **License Required:** No - **Delegation:** Not supported - **Starting Price:** $7.50/month [Deploy Avail Node](/Guides/Console/Managed-Nodes/avail) | [Get Started with Console](/Get-Started/Console/README.md) ### Celestia Modular blockchain powering applications with full-stack customizability through a dedicated data availability layer. - **Node Type:** Light - **License Required:** No - **Delegation:** Not supported - **Starting Price:** $15.00/month [Deploy Celestia Node](/Guides/Console/Managed-Nodes/celestia) | [Get Started with Console](/Get-Started/Console/README.md) ### Captain & Company Web3 protocol with managed Node services available through NodeOps Console. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Captain & Company Node](/Guides/Console/Managed-Nodes/capnco) | [Get Started with Console](/Get-Started/Console/README.md) ### DIN Data infrastructure network providing decentralized data services for Web3 applications. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy DIN Node](/Guides/Console/Managed-Nodes/din) | [Get Started with Console](/Get-Started/Console/README.md) ### Fuse Payments-focused blockchain network enabling fast and low-cost transactions for everyday commerce. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Fuse Node](/Guides/Console/Managed-Nodes/fuse) | [Get Started with Console](/Get-Started/Console/README.md) ### Huddle01 Decentralized video infrastructure protocol enabling real-time communication across Web3 applications. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Huddle01 Node](/Guides/Console/Managed-Nodes/huddle01) | [Get Started with Console](/Get-Started/Console/README.md) ### Hybrid Web3 protocol with managed Node services available through NodeOps Console. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Hybrid Node](/Guides/Console/Managed-Nodes/hybrid) | [Get Started with Console](/Get-Started/Console/README.md) ### Hychain Gaming-focused blockchain designed for high-performance game economies and infrastructure. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Hychain Node](/Guides/Console/Managed-Nodes/hychain) | [Get Started with Console](/Get-Started/Console/README.md) ### iAgent AI agent infrastructure protocol with bootstrapping and delegation capabilities for decentralized AI services. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Supported [Deploy iAgent Node](/Guides/Console/Managed-Nodes/iagent/bootstrapping) | [Get Started with Console](/Get-Started/Console/README.md) ### KIP Web3 protocol with managed Node services available through NodeOps Console. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy KIP Node](/Guides/Console/Managed-Nodes/kip) | [Get Started with Console](/Get-Started/Console/README.md) ### Lumoz ZK Compute layer providing zero-knowledge proof infrastructure for scalable blockchain applications. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Lumoz Node](/Guides/Console/Managed-Nodes/lumoz) | [Get Started with Console](/Get-Started/Console/README.md) ### 0G Decentralized AI operating system providing scalable infrastructure for AI applications and data availability. - **Node Type:** Alignment - **License Required:** Yes β€” 0G Alignment NFT - **Delegation:** Supported [Deploy 0G Node](/Guides/Console/Managed-Nodes/og-alignment) | [Get Started with Console](/Get-Started/Console/README.md) ### OpenPad Web3 launchpad protocol with managed Node infrastructure for decentralized project launches. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy OpenPad Node](/Guides/Console/Managed-Nodes/openpad) | [Get Started with Console](/Get-Started/Console/README.md) ### Sophon Web3 protocol offering managed Node services with commission-based delegation support through NodeOps Console. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Supported [Deploy Sophon Node](/Guides/Console/Managed-Nodes/sophon) | [Get Started with Console](/Get-Started/Console/README.md) ### Vemp Horizon Web3 gaming and metaverse infrastructure protocol with managed Node services. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy Vemp Horizon Node](/Guides/Console/Managed-Nodes/vemp-horizon) | [Get Started with Console](/Get-Started/Console/README.md) ### XProtocol Social infrastructure protocol enabling decentralized communication and social features across Web3. - **Node Type:** Node - **License Required:** Yes β€” NFT License - **Delegation:** Not supported [Deploy XProtocol Node](/Guides/Console/Managed-Nodes/xprotocol) | [Get Started with Console](/Get-Started/Console/README.md) ## FAQ ### What are web3 infrastructure Nodes? Core Web3 infrastructure protocols including Compute, storage, and communication layers ### How much does it cost to run web3 infrastructure Nodes on NodeOps? Pricing starts from $6.00/month. Longer subscriptions receive discounts up to 30%. ### Do I need technical expertise to run these Nodes? No. NodeOps Console handles all hardware, installation, updates, and uptime management. You can deploy Nodes with just a few clicks using the NaaS (Node-as-a-Service) model. ## What next? - [Get Started with NodeOps Console](/Get-Started/Console/README.md) to deploy your first Node - View all [supported protocols](/Guides/Console) on NodeOps Console - Learn about [Node-as-a-Service](/Learn/Glossary/naas) and how NodeOps handles the technical complexity --- --- ## Changelog ### Product updates > Stay up to date with NodeOps Network product updates. Changelog covering Cloud Marketplace, Console, Portal, DeFi services, and provider changes. URL: https://docs.nodeops.network/Changelog ## Apps #### 20250922: 0G Alignment Node supported [0G Alignment Node](/Guides/Console/Managed-Nodes/og-alignment) support added to NodeOps Console. #### 20250822: Telegram bot Push notifications added to [Telegram bot](/Guides/tg-bot). #### 20250820: Telegram bot We added new functions to the [Telegram bot](/Guides/tg-bot): - /mygNODE - /redeemnode - /myplans #### 20250721 UNO Node Orchestrators We made [UNO Node Orchestrators](/Get-Started/Cloud-Compute/node-orchestrator) available from the [Cloud](https://cloud.nodeops.network/) and [Console](https://console.nodeops.network/) apps. #### 20250818: Aethir staking We introduced [Aethir staking on NodeOps Portal](/Get-Started/DeFi-Services/stake#stake-supported-tokens-with-nodeops-portal): 100 K gNode pool ends 4th October, 2025. #### 20250815: Portal as DeFi app NodeOps Staking Hub was sunsetted and all its functions supported from the [Portal app](/Guides/Portal). #### 20250810: LNT Vault for liquidity release NodeOps Console began support for [LNT Vault](/Get-Started/DeFi-Services/liquidity). #### 20250723 Free Template A [free template](/Get-Started/Cloud-Infrastructure/deploy) has been made available to allow users to experience how easy a deployment is at no cost. #### 20250625 gNODE withdrawl Users are able to [redeem gNODE](/Guides/Portal#redeem-gnode-with-nodeops-portal) with a redemption period between 15 and 150 days. #### 20250623 Autorenewal Cloud deployments can now be set to autorenew. #### 20250623 Payment partner fee increase Copperx increased its fee to 2% on each transaction. Please consider [adding credits](/Get-Started/Pay-for-Services#step-1-optional-top-up-your-credits) to reduce the number of transactions needed. #### 20250524: Node delegation We introduced a **Node Delegation** feature accessible via the Console app, allowing users to delegate their Non-Fungible Tokens (NFTs) and allocate a portion of the commission to NodeOps. This eliminates the complexities of self-managing Nodes, offering a hassle-free experience. #### 20250414: Enhanced notification system To keep our users consistently informed, we implemented a comprehensive notification system. Users now receive in-app notifications directly on their console for various events, complementing our new Email Notification system that delivers timely updates straight to their inboxes. #### 20250303: Email notification system To keep our users consistently informed, we implemented an Email Notification system that delivers timely updates straight to their inboxes. #### 20250309: $NODE to credit conversion We've empowered users with greater financial flexibility through the \$NODE to Credit Conversion** feature. This allows users to convert their $NODE tokens into USD credits, usable across the entire NodeOps platform ecosystem. #### 20250216: Auto-renewal feature To ensure uninterrupted service, we've introduced an **Auto-renewal feature**. When enabled, user-selected subscriptions will automatically renew, provided sufficient credits are available in their account. ## Cloud ### Marketplace #### 20250929 Correction Issues with [example template definitions](/Reference/template-schema) identified and corrected. #### 20250929: Gensyn Testnet Node supported [Gensyn Testnet Node](/Guides/Marketplace/Marketplace-Templates/gensyn-gpu) compatible with RL Swarm supported in Marketplace. #### 20250902 Gaia GPU [Gaia GPU](/Guides/Marketplace/Marketplace-Templates/gaia-mainnet) supported in Marketplace. #### 20250920: Free preview Template creators have [free deployment tier](/Guides/Marketplace/Configure-Compute/upload-template#optional-test-your-template-deployment) for template testing. ### Mainnet #### 20250901 Machine status update - Active - Inactive: - Pending - Inactive - Awaiting-Stake - Deleted: - Suspended - Draining - Deleted - Deleting #### Linux Kernel minimum version update to 6.7+ ##### About We have updated the minimum required Linux kernel version to 6.7+ to address a USER_IDMAP related issue found in Debian’s 6.1 kernel version. ##### Why this change? In Debian releases with kernel version 6.1, a USER_IDMAP issue was discovered that could impact system functionality. Upgrading to kernel 6.7 or later resolves this issue. ##### Action required Users running older Linux kernel versions on Debian need to upgrade their kernel to maintain compatibility and avoid issues. ###### Upgrade steps for Debian To upgrade to kernel 6.7 or above on Debian (such as Debian bookworm), users can execute the following commands: ```bash echo "deb http://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware" >> /etc/apt/sources.list sudo apt update sudo apt install -t bookworm-backports linux-image-amd64 ``` This enables backports in the sources list, updates package lists, and installs the latest Linux kernel image from backports. #### Service log command update ##### About As part of the migration from testnet to mainnet, the service name used for real-time log monitoring has changed. The `journalctl` command should now target the nn-provider service rather than the atlas service. ##### Old command Testnet: ```bash journalctl -fu atlas* ``` ##### New command Mainnet ```bash journalctl -fu nn-provider* ``` ##### Action required When monitoring logs on mainnet, use the new command. Update any automation scripts, aliases, or documentation that still reference the old atlas* service name. The old service naming will no longer receive logs once all Nodes have transitioned to Mainnet. ##### Why this change? The service name was updated to reflect the new Mainnet infrastructure and provider naming standards, ensuring consistency across deployments and monitoring tools. ### Provider onboarding command update #### About We’ve updated the provider installation / upgrade command to point to our new Mainnet server. This change ensures you always fetch the latest verified installer script from the updated endpoint. ##### Old command ```bash curl -L https://get.atlasnetwork.dev | sh -s - ZxEsuA******************zAJ6 New command ``` ```bash curl -L https://serve-pre-mainnet.nodeops.network | sh -s - ZxEsuA******************zAJ6 ``` ##### Action required If you are installing a new provider or re-onboarding a machine, use the new command. ##### Why this change? We have migrated our distribution to a new infrastructure to improve delivery speed, reliability, and version traceability for pre-mainnet operations. ### 20250707: Testnet sunsetted **Show me archive** #### 0.0.1-13022025 Provider upgrade #### About This upgrade aims to enhance system stability and ability along with the latest runtime and dependency patches #### Action required Re-run the command that you ran while onboarding the machine, which looks something like `curl -L https://get.atlasnetwork.dev | sh -s - ` > You can search for the command in your history by running the following. ```shell history | grep -m1 'get.atlasnetwork' ``` #### Existing machines Open Terminal and run the following command, ensure you're root user by running `sudo su` ```shell systemctl restart atlasnetwork-provider.service ``` #### 0.0.1-03012025 Provider upgrade #### About This upgrade aims to enhance system stability and address previously identified connectivity issues affecting certain users. Providers anticipate temporary downtime during the upgrade process, which is anticipated. #### Action required ##### Existing machines Open Terminal and run the following command, make sure you're root user by running `sudo su` ```shell systemctl restart atlasnetwork-provider.service ``` ---